<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>views</title><description/><link>https://kevinquillen.com</link><language>en</language><item><title>Using computed fields in Drupal 11 and Views</title><link>https://kevinquillen.com/using-computed-fields-drupal-11-and-views</link><guid isPermaLink="false">399 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Using computed fields in Drupal 11 and Views&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Every so often I run into something in Drupal that reminds me why I still enjoy working with it after all these years. Recently, while working with the Group module, I needed to display a few pieces of dynamic information: the number of members in each group and a handful of user thumbnails. I wanted these values both on the Group entity itself and inside a Views listing like a “Group Directory” page.&lt;/p&gt;&lt;p&gt;That led me to computed fields, how they behave on entities, how they behave in Views, and why you often need two different implementations even though the logic is the same.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2025-11-25T01:53:33+00:00&quot;&gt;&lt;time datetime=&quot;2025-11-24T20:53:33-05:00&quot; title=&quot;Monday, November 24, 2025 - 20:53&quot;&gt;November 24th, 2025&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Tue, 25 Nov 2025 01:53:33 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Manually Add Breadcrumb Links in Drupal 8</title><link>https://kevinquillen.com/manually-add-breadcrumb-links-drupal-8</link><guid isPermaLink="false">284 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Manually Add Breadcrumb Links in Drupal 8&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;In Drupal, most breadcrumb generation and navigation is sufficient by basing it off of the menu hierarchy with the Menu Breadcrumb module.&lt;/p&gt;

&lt;p&gt;This works great except in certain edge cases, such as nodes that do not have menu placement, and Views pages which may exist, but not have a set menu link. Neither Drupal core nor Menu Breadcrumb have a way to handle this scenario.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2017-02-16T12:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2017-02-16T07:00:00-05:00&quot; title=&quot;Thursday, February 16, 2017 - 07:00&quot;&gt;February 16th, 2017&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Thu, 16 Feb 2017 12:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Overriding Output for Search API Fields in Views</title><link>https://kevinquillen.com/overriding-output-search-api-fields-views</link><guid isPermaLink="false">285 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Overriding Output for Search API Fields in Views&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Just wanted to share a quick example of overriding a field output from Search API if the value isn’t exactly what you want.&lt;/p&gt;

&lt;p&gt;In my case, I am indexing the URI of a node and have a design requirement to output it as a link in the result, but it has to contain the host and scheme (http://www.example.com/path/to/node). Out of the box, Search API is only returning the “/path/to/node” portion, which QA quickly kicked back to me.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2017-02-02T12:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2017-02-02T07:00:00-05:00&quot; title=&quot;Thursday, February 2, 2017 - 07:00&quot;&gt;February 2nd, 2017&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Thu, 02 Feb 2017 12:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item></channel></rss>