>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2550199. --> Reported by: [dsnopek](https://www.drupal.org/user/266527) Related to !10 >>> <p>This is a spin off of <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2377757" title="Status: Closed (fixed)">#2377757: Expose Block Context mapping in the UI</a></span> (and depends on that issue in order to work, so "Postponed")</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Context is frequently used to pass an entity to a block, as this allows you to do cool things like (a) place a block that shows the feed for the entity currently being displayed, or (b) show the feed for a referenced entity, as well as just (c) showing the feed for a specifically selected entity.</p> <p>Using configuration only allows you to do (c) but not (a) or (b).</p> <p>0) Apply the patch from <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/drupal/issues/2377757" title="Status: Closed (fixed)">#2377757: Expose Block Context mapping in the UI</a></span><br> 1) Apply the latest patch<br> 2) drush si<br> 3) drush en aggregator<br> 4) admin/config/services/aggregator<br> 5) Add a feed to <a href="http://rss.cbc.ca/lineup/topstories.xml">http://rss.cbc.ca/lineup/topstories.xml</a> (Canada FTW)<br> 6) admin/structure/block<br> 7) Add the "Aggregator feed" block</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Modify the aggregator block to use context rather than configuration.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>RTBC</li> <li>Get someone to commit it!</li> </ol> <h3 id="summary-ui-changes">User interface changes</h3> <p>After installing Aggregator, we visit the block layout admin w/o creating a feed yet and we are treated to this:</p> <p><img src="https://www.drupal.org/files/issues/01%20Block%20List%20-%20pre%20feed.png" alt=""></p> <p>If we attempt to configure this block without having created a Feed yet, we get this:</p> <p><img src="https://www.drupal.org/files/issues/02%20Block%20Config%20-%20pre%20feed.png" alt=""></p> <p>This is kind of ridiculous because there are no feeds, and we're placing a block that cannot even function yet. Once we create feeds we get:</p> <p><img src="https://www.drupal.org/files/issues/03%20Block%20Config%20-%201%20feed.png" alt=""><br> for 1 feed and:</p> <p><img src="https://www.drupal.org/files/issues/04%20Block%20Config%20-%20n%20feed.png" alt=""><br> for N feeds respectively.</p> <h4>Summary of HEAD:</h4> <p>We have the ability to place aggregator feed blocks before they're useful. This can lead to misconfigured blocks that don't function.</p> <h3>After Patch:</h3> <p>Leveraging the context system brings some uniform benefits to the UI, first on the list is that before you've created any feed entities, the block layout system won't even give you the erroneous option of placing feed blocks:</p> <p><img src="https://www.drupal.org/files/issues/05.1%20Block%20List%20-%20post%20patch%3Apre%20feed.png" alt=""></p> <p>After we've created feeds, the block system shows us that we can actually use the block:<br> <img src="https://www.drupal.org/files/issues/05.2%20Block%20List%20-%20post%20patch%3Apost%20feed.png" alt=""></p> <p>If we've only created a single feed, the block doesn't prompt the user for unnecessary configuration, it knows there's only one possible feed to use, and it just auto-configures that single value:<br> <img src="https://www.drupal.org/files/issues/06%20Block%20Config%20-%20post%20patch%3A1%20feed.png" alt=""></p> <p>Once multiple Feeds have been created, the user interface expands accordingly:<br> <img src="https://www.drupal.org/files/issues/07.1%20Block%20Config%20-%20post%20patch%3An%20feed.png" alt=""></p> <p>and<br> <img src="https://www.drupal.org/files/issues/07.2%20Block%20Config%20-%20post%20patch%3An%20feed.png" alt=""></p> <h3 id="summary-api-changes">API changes</h3> <p>None.</p>