🇺🇸United States @w01f

w01f → created an issue.

Sounds great to me! Thanks Jurgen

Ahh, I had missed the bold message on the EU Cookie Compliance page (that's the one we use). If that's the case and they all tackle the same problem, so that Klaro is the obvious, de facto best option - then I agree and we can close this.

w01f → created an issue.

Roger that. There is a new method for creating facets and view filters - https://project.pages.drupalcode.org/facets/exposed_filters - so I'll look into that and circle back around. Thanks!

w01f → created an issue.

w01f → created an issue.

I get this as well when clearing the cache with "drush cr".

Just following up on this - currently we have to use a few imperfect contrib/custom solutions to make a dropdown select for switching language. Some direction about if there's a plan for this and how/what to work on to contribute towards a best practices, accessible solution would be great.

Confirming patch in #32 resolves the WSOD error issue on D11.1.5.

I just ran into this, errors when attempting to run drush updb, when attempting to install commerce_invoice and bee_hotel together on a new D11 instance. These changes allowed me to run updb as normal, though I am still having issues getting everything to work as expected.

w01f → created an issue.

@mably I have this working correctly with the two changes on several D11 sites now - lgtm!

w01f → created an issue.

w01f → created an issue.

w01f → created an issue.

w01f → created an issue.

w01f → created an issue.

Interested in this as well - a couple questions spring to mind:

1. What are the differences (pros/cons) of each module - can we create a comparison table?
2. What are the benefits of using DropZoneJS over the native Drupal mechanism, or vice versa?
3. Are there any example best use case scenarios for one module over the other?

Also interested in any news on a D11 compatible release, cheers and thanks as well.

@grevil you piqued my curiosity - my team still finds this the easiest catch-all, integrated solution for responsive favicons. What are you using now?

Just updated to 3.0 RC1 and everything seems to be working fine so far - All songs are making use of tablefields for lyrics.
Ex: https://www.kobejet.com/en/song/let-it-go

+1 for adding mably as a co-maintainer - he is already a maintainer on a LOT of notable/popular modules and has over 200+ fixed issues.

Umm, please share that video and update the link here! That sounds absolutely fantastic.

w01f → created an issue.

@drunken-monkey, I could have been less sarcastic in my response as well. Thanks for adding your reasoning.

Also running into this issue - on D11 with latest commerce installed, and can't install BEE via composer.

+1 for mably as a new co-maintainer and a 3.x branch

@penyaskito absolutely. I went ahead and removed the ChatGPT response suggestions. I'm also eager to use the new dashboard and will await official details on how to correctly implement it.

Wow. I'm just going to chime in that @xen thoughtfully detailed an extremely valid reason to follow software platform/base convention and... @drunken monkey, you just...what, decided to completely ignore it?

Wait, let me actually break down what I'm seeing here further.

1. The question as to whether to adopt hooks over events originally came up in this Search API Autocomplete thread 📌 Convert all hooks to events Active .
2. Drunken Monkey, actually said "good point" and then took the initiative to open this thread, with the sole purpose to discuss...
3. @xen had the highest word count contributing to the discussion - and it's not fluff. As I said before it's well thought out and valid.
4. Drunken Monkey ignored valid points and marked as fixed with no reponse.

My issue here isn't with the decision or anything else. It's that time, consideration, and discussion was specifically solicited. And then it was almost categorically discounted and ignored. That's just rude. @drunken monkey, in the future when you take the initiative to open a ticket specifically asking for engagement, fulfill your absolutely basic, most minimum expected duties as the moderator and thoughtfully respond in kind. #welcometoopensource #opensource101

@drasgardian, my understanding is the new Dashboard you configured should be able to replace the standard user account page and be set as the default for users when they log in or click to view their account information.

That said, and without trying it myself yet, I plugged the question into ChatGPT and got the following:

In Drupal, how do you set a new path as the default page for users logging in, or when they click to see their account page? I want to install and use the Dashboard module, but am unsure how to actually have it replace the current user account page.
Reasoned for 1m 40s
You can achieve this in one of two ways:

1. Redirect Users After Login
If you want users to land on your dashboard immediately after they log in (rather than when they click on “My Account”), you can use a contributed module like Login Destination. With this module, you configure a rule so that when a user logs in, they’re redirected to your new dashboard path (for example, /dashboard).

Steps:

Install & Enable Login Destination:
Download and enable the module.

Configure the Redirect:
Go to Configuration > People > Login Destination and add a rule that targets the user login event. Specify /dashboard (or your chosen path) as the destination.

This method ensures users are sent to the dashboard right after logging in.

2. Override the Default User Account Page
If you want to permanently replace the default /user page (the account page) with your dashboard, you’ll need to override Drupal’s route for the user account page. In Drupal 8/9/10, this is best done by creating a custom module that implements a Route Subscriber.

Example Implementation:

Create a Custom Module:
Create a new module (e.g., my_dashboard_override).

Implement a Route Subscriber:
In your module, add a file (e.g., src/Routing/MyDashboardRouteSubscriber.php) with the following code:

<?php

namespace Drupal\my_dashboard_override\Routing;

use Drupal\Core\Routing\RouteSubscriberBase;
use Symfony\Component\Routing\RouteCollection;

class MyDashboardRouteSubscriber extends RouteSubscriberBase {
  /**
   * Alters existing routes.
   *
   * @param \Symfony\Component\Routing\RouteCollection $collection
   *   The route collection.
   */
  protected function alterRoutes(RouteCollection $collection) {
    // Override the default user account page.
    if ($route = $collection->get('entity.user.canonical')) {
      // Replace the controller with the Dashboard module’s controller.
      // (Make sure to adjust this to the actual namespace and method provided by your Dashboard module.)
      $route->setDefault('_controller', '\Drupal\dashboard\Controller\DashboardController::dashboard');
      // Optionally, change the title.
      $route->setDefault('_title', 'Dashboard');
    }
  }
}

Register the Route Subscriber:
Create a my_dashboard_override.services.yml file in your module’s root with this content:

services:
  my_dashboard_override.route_subscriber:
    class: Drupal\my_dashboard_override\Routing\MyDashboardRouteSubscriber
    tags:
      - { name: event_subscriber }

Clear Cache:
After enabling your custom module, clear all caches so that Drupal picks up your route override.

This method replaces the default /user route so that whenever a logged-in user visits their account page, they see the dashboard instead.

Summary
Redirect on Login: Use the Login Destination module to send users to /dashboard right after they log in.
Override the Route: Create a custom module with a Route Subscriber to change the default user account page (entity.user.canonical) to use the Dashboard module’s controller.
Choose the method that best fits your desired user experience. If you want the dashboard to always appear in place of the account page, the route override is the way to go. Otherwise, redirecting on login might be sufficient if you only want to change the post-login behavior.

w01f → created an issue.

w01f → created an issue.

This module looks amazing - we're also looking forward to using it once there's a readme and a full, stable release covered by the Drupal Security Team with the Drupal "shield".

Also confirming patch #3 → appears to solve issue on 10.4.2.

w01f → created an issue.

Chiming in that this module made my org's D11 wishlist holdout list - https://www.timbers.dev/article/our-drupal-11-waiting-wishlist-getting-s....

It has over 10k registered sites, so it's fairly well used. Do you need additional support/maintainers to get work on getting a D11-compatible version ready? After reading through the related open issues, it sounds like the plan is to release a completely new major version to slim the codebase down while supporting all the new realfavicon.net functionality/updates?

I definitely think there would be widespread interest and support for a module that allows full, automated site backups on different providers.

Also verified on a new D11.1.2 site and seems to work correctly with no further changes.

ChatGPT suggests that handling conversions by replacing, rather than appending, the new extension may be better for SEO and caching. It suggests 2 methods:

1. Adjust Your Conversion Process
If you’re using a tool (like ImageMagick, GD, or a dedicated Drupal module) to convert images to WebP, check its configuration. Some tools allow you to specify a naming pattern so that the original extension is replaced rather than appended. For example, instead of appending .webp to DSC_3347.jpeg, you’d configure it to replace .jpeg with .webp.

2. Use a Drupal Hook to Alter the Output URL
In Drupal, you can implement a hook (such as hook_image_style_url_alter()) to modify the generated image URL. For example:

php
Copy
/**
 * Implements hook_image_style_url_alter().
 */
function mymodule_image_style_url_alter(&$url, $style_name, $uri) {
  // Adjust only for styles that convert to WebP.
  if ($style_name == 'your_webp_style') {
    // Replace a filename ending in .anything.webp with just .webp.
    $url = preg_replace('/\.[^.]+\.webp$/', '.webp', $url);
  }
}

Replace 'your_webp_style' with the actual machine name of your image style.
After implementing this hook, clear your caches so the changes take effect.

w01f → created an issue.

Update: Disregard - the new default module filter is too smart for my own good and just wasn't showing the submodules. I believe it's working correctly now - thanks again!

w01f → created an issue.

Just chiming in, this is what we added to make the checklist look correct on our site:

/* CKEditor Plugin Pack overrides */
.todo-list {
	list-style: none;
  margin: 2rem 0;
}

.todo-list .todo-list__label {
	vertical-align: middle;
}

.todo-list .todo-list__label input[type="checkbox"] {
	margin-right: .5rem;
}

Hi @salmonek,

Okay so I just:

1. Removed the checklist icon from active
2. Saved text format configuration
3. Cleared cache
4. Re-added checklist to active
5. Re-saved text format configuration

And I still don't see any checkboxes (checked or not) on the node display page using Olivero as the theme. I also didn't notice anything being added to the alllowed html tag list (screenshot attached). For reference, what should be present there to show correctly? In my case, I think I can just manually add the tags to allow.

@ressa if the goal is just to help users successfully set up an valid RSS feed for Planet Drupal, I think providing a working view template with instructions to help understand and further customize fields, rewrites, etc. that can be modified as needed would be better?

Hi @salmonek, this does indeed seem to be that issue so I'm fine with closing as a duplicate. But I did try to:

1. Rebuild the cache

Resave the text editor configuration

And I'm still not seeing the checkboxes on the Olivero frontend. I might wait until the next release or the next next release with the Olivero style changes...

w01f → created an issue.

Okay, I think I have it... please check (for the last time?) when you have a chance.

A couple notes:

1. I was confused at first by Comment 13 📌 Add Timbers.Dev to Planet Drupal Active at first, because I didn't find it intuitive customize the default 'RSS view' to that extent. At least my assumption was that the majority should work by default without customzing field output. Once I got over that assumption, the format was fairly easy to replicate."
2. The Missing atom:link with rel="self" suggestion seems to be a simple quick template override of web/core/modules/views/templates/views-view-rss.html.twig. Should this be included by default in core?
3. Is the GUID supposed to show path aliases? I'm assuming not as it's supposed to be a permanent ID location, in case the alias changes. But despite tinkering with all the settings I could find in the view I couldn't get it to not output the alias...
4. Any other best practice or future-proofing suggestions?

Thanks again for all your help with this! I would not have been able to muddle through without both of your assistance!!

@ressa okay I now have:

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://www.timbers.dev/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Drupal</title>
    <link>https://www.timbers.dev/</link>
    <description></description>
    <language>en</language>
    
    <item>
  <title>So what IS Drupal CMS... exactly?</title>
  <link>https://www.timbers.dev/article/so-what-drupal-cms-exactly</link>
  <description>  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/2025-01/A%20comparison%20between%20two%20systems%2C%20Drupal%20and%20Drupal%20CMS.webp&quot; width=&quot;1792&quot; height=&quot;1024&quot; alt=&quot;A comparison between two systems, Drupal and Drupal CMS&quot; /&gt;


Drupal CMS offers an intuitive, user-friendly approach for creating specialized websites without deep technical expertise. Built on curated &quot;recipes&quot;—collections of community-vetted modules—it streamlines site building, ensuring compatibility and reducing guesswork. Fully compatible with Drupal Core, it enhances flexibility while maintaining transparency. By combining powerful functionality with guided simplicity, Drupal CMS empowers users to build faster, more reliable sites, making it a game-changer for content managers and site builders.</description>
  <pubDate>Tue, 01/21/2025 - 09:56</pubDate>
    <dc:creator><a href="/user/129" hreflang="en">David Dowell</a></dc:creator>
    <guid isPermaLink="true">https://www.timbers.dev/682</guid>
    </item>
<item>
  <title>Drupal Community &amp; Learning Resources</title>
  <link>https://www.timbers.dev/article/drupal-community-learning-resources</link>
  <description>  &lt;img loading=&quot;lazy&quot; src=&quot;/sites/default/files/2025-01/Futuristic%20image%20of%20the%20collaborative%20Drupal%20Community%20and%20learning%20resources.webp&quot; width=&quot;1792&quot; height=&quot;1024&quot; alt=&quot;Futuristic image of the collaborative Drupal Community and learning resources&quot; /&gt;


The Drupal CMS community offers valuable tools for beginners and experienced users. Key resources include Drupal.org for modules, themes, and updates, a customizable dashboard to track issues and posts, and Slack channels for support. Notable tools like Planet Drupal, The Weekly Drop newsletter, and beginner guides enhance learning. Engage in Slack communities or explore recommended channels like Accessibility, CKEditor5, and Jobs. Build your Drupal knowledge through events, tutorials, and contributions while growing within the supportive community.</description>
  <pubDate>Mon, 12/30/2024 - 09:35</pubDate>
    <dc:creator><a href="/user/129" hreflang="en">David Dowell</a></dc:creator>
    <guid isPermaLink="true">https://www.timbers.dev/455</guid>
    </item>

  </channel>
</rss>

I don't see the following and unsure how to add:

• Tue, 28 Jan 2025 20:01:29 +0100

Okay, how about now - I think I figured out the RSS setting I needed to change at /admin/config/services/rss-publishing

I still can't figure out how to change the channel description and link if those are necessary - any suggestions?

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="https://www.timbers.dev/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Drupal</title>
    <link>https://www.timbers.dev/</link>
    <description></description>
    <language>en</language>
    
    <item>
  <title>So what IS Drupal CMS... exactly?</title>
  <link>https://www.timbers.dev/article/so-what-drupal-cms-exactly</link>
  <description>&lt;span class=&quot;field field--name-title field--type-string field--label-hidden&quot;&gt;So what IS Drupal CMS... exactly?&lt;/span&gt;
&lt;span class=&quot;field field--name-uid field--type-entity-reference field--label-hidden&quot;&gt;&lt;a title=&quot;View user profile.&quot; href=&quot;/user/129&quot; class=&quot;username&quot;&gt;David Dowell&lt;/a&gt;&lt;/span&gt;
&lt;span class=&quot;field field--name-created field--type-created field--label-hidden&quot;&gt;&lt;time datetime=&quot;2025-01-21T09:56:54-08:00&quot; title=&quot;Tuesday, January 21, 2025 - 09:56&quot; class=&quot;datetime&quot;&gt;Tue, 01/21/2025 - 09:56&lt;/time&gt;
&lt;/span&gt;
  &lt;div class=&quot;layout layout--twocol-section layout--twocol-section--75-25&quot;&gt;

          &lt;div  class=&quot;layout__region layout__region--first&quot;&gt;
        &lt;div class=&quot;block block-layout-builder block-field-blocknodearticlebody&quot;&gt;
  
    
      
  &lt;div class=&quot;clearfix text-formatted field field--name-body field--type-text-with-summary field--label-hidden field__items&quot;&gt;
        &lt;div class=&quot;field__item&quot;&gt;Drupal CMS offers an intuitive, user-friendly approach for creating specialized websites without deep technical expertise. Built on curated &quot;recipes&quot;—collections of community-vetted modules—it streamlines site building, ensuring compatibility and reducing guesswork. Fully compatible with Drupal Core, it enhances flexibility while maintaining transparency. By combining powerful functionality with guided simplicity, Drupal CMS empowers users to build faster, more reliable sites, making it a game-changer for content managers and site builders.&lt;/div&gt;
  &lt;/div&gt;
  &lt;/div&gt;
&lt;div class=&quot;block block-layout-builder block-field-blocknodearticlefield-tags&quot;&gt;
  
    
      
  &lt;div class=&quot;field field--name-field-tags field--type-entity-reference field--label-above field__items&quot;&gt;
    &lt;div class=&quot;field__label&quot;&gt;Tags&lt;/div&gt;
        &lt;div class=&quot;field__item&quot;&gt;&lt;a href=&quot;/taxonomy/term/216&quot; hreflang=&quot;en&quot;&gt;Drupal&lt;/a&gt;&lt;/div&gt;
        &lt;div class=&quot;field__item&quot;&gt;&lt;a href=&quot;/taxonomy/term/212&quot; hreflang=&quot;en&quot;&gt;Drupal CMS&lt;/a&gt;&lt;/div&gt;
        &lt;div class=&quot;field__item&quot;&gt;&lt;a href=&quot;/taxonomy/term/213&quot; hreflang=&quot;en&quot;&gt;Comparison&lt;/a&gt;&lt;/div&gt;
  &lt;/div&gt;
  &lt;/div&gt;
&lt;div class=&quot;block block-layout-builder block-extra-field-blocknodearticlelinks&quot;&gt;
  
    
        &lt;div class=&quot;node__links&quot;&gt;
    &lt;ul class=&quot;links inline&quot;&gt;&lt;li class=&quot;node-readmore&quot;&gt;&lt;a href=&quot;/article/so-what-drupal-cms-exactly&quot; rel=&quot;tag&quot; title=&quot;So what IS Drupal CMS... exactly?&quot; hreflang=&quot;en&quot;&gt;Read more&lt;span class=&quot;visually-hidden&quot;&gt; about So what IS Drupal CMS... exactly?&lt;/span&gt;&lt;/a&gt;&lt;/li&gt;&lt;li class=&quot;comment-add&quot;&gt;&lt;a href=&quot;/article/so-what-drupal-cms-exactly#comment-form&quot; title=&quot;Share your thoughts and opinions.&quot; hreflang=&quot;en&quot;&gt;Add new comment&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;  &lt;/div&gt;

  &lt;/div&gt;

      &lt;/div&gt;
    
          &lt;div  class=&quot;layout__region layout__region--second&quot;&gt;
        &lt;div class=&quot;block block-layout-builder block-field-blocknodearticlefield-media-image&quot;&gt;
  
    
      
  &lt;div class=&quot;photoswipe-gallery field field--name-field-media-image field--type-entity-reference field--label-hidden field__items&quot;&gt;
        &lt;div class=&quot;field__item&quot;&gt;  &lt;a href=&quot;https://www.timbers.dev/sites/default/files/2025-01/A%20comparison%20between%20two%20systems%2C%20Drupal%20and%20Drupal%20CMS.webp&quot;  class=&quot;photoswipe&quot; data-pswp-width=&quot;1792&quot; data-pswp-height=&quot;1024&quot; data-overlay-title=&quot;&quot;&gt;&lt;img src=&quot;/sites/default/files/styles/max_325x325/public/2025-01/A%20comparison%20between%20two%20systems%2C%20Drupal%20and%20Drupal%20CMS.webp?itok=lRdhU_hh&quot; width=&quot;325&quot; height=&quot;186&quot; alt=&quot;A comparison between two systems, Drupal and Drupal CMS&quot; loading=&quot;lazy&quot; class=&quot;image-style-max-325x325&quot; /&gt;

&lt;/a&gt;
&lt;/div&gt;
  &lt;/div&gt;
  &lt;/div&gt;

      &lt;/div&gt;
    
  &lt;/div&gt;
</description>
  <pubDate>Tue, 21 Jan 2025 17:56:54 +0000</pubDate>
    <dc:creator>David Dowell</dc:creator>
    <guid isPermaLink="false">682 at https://www.timbers.dev</guid>
    </item>

@ressa okay I think I'm getting there - I believe I've removed the tags, though I was under the impression they were needed as "Drupal Planet" is specified as necessary.

Also changed the display of the image to a thumbnail, but obviously this doesn't show anything on the feed page... is that how it's supposed to work and somehow the posts will automagically show the image correctly?

Thanks for both of your help!

@avpaderno, okay I think the changes just hadn't made their way through the CDN caching probably. Can you check now - I am seeing body text and an image included now.

@avpaderno okay I think I have it fixed now - please check.

After more testing, I think I misunderstood Better Social Sharing Buttons → . I now think it is also of the "Sharing" type, which would leave the Social Media Links Block and Field → module as the only "Information" type. Can you verify this is your impression as well before I update the ticket and other places this is posted?

So then do Better Social Sharing Buttons → and your module, Better Social Share → , essentially do the same thing? Is there room for discussion on merging and reducing duplication of effort, or do they provide incompatibly different features?

In part I'm asking because I noticed one of my friends Martin is a maintainer of the former, and would love to have two great minds working together if possible on the "same" product.

w01f → created an issue.

Hi @sujan-shrestha, I'm putting together a blog that you are more than welcome to share anywhere that makes sense - module description pages, etc.

If we could get a table going to help users quickly assess the different options that would be the next step. Would you be willing to get the jump on that?

Modules to include would be:

1. Informative - links to individual's or company's social media accounts
   • Better Social Sharing Buttons →
   • Social Media Links Block and Field →
2. Sharing - options to directly share the links for entities or repost on one's own social media
   • Better Social Share →
   • AddToAny Share Buttons →

And some starter comparisons would be:

• Security / shares user information with third-parties
• Type - Informative vs Sharing (if we want to break that down there instead of making completely separate tables?
• Optimizes native sharing per platform
• Placement options - block/page/node
• Drupal core version compatibility (D7/10/11)
• Most recent update/release

Let me know your thoughts and I'm happy to add you as a blog contributor too if you'd like - this'll only be my third one.

Fantastic response and information, thanks @sujan-shrestha! I am continuously testing and may even make a blog post breaking down some of the same information =)

Also confirmed working on a test D11.1 site.

Thank you for the additional information @cmlara - it sounds like we wait to see if any of the maintainers chime in, while also possibly pursuing some changes to the maintainer review and authentication process?

I would also recommend instituting a mandatory periodic review of maintainers for modules (with current versions of supported Drupal - shield "covered by security team") reportedly used on over 10k (or some threshold) sites.

Setting this back to "Needs work" as it's obviously not "Fixed", but I'm unsure if another Status is more appropriate.

@deekayen, @shrop, @ms2011 and @bdone - please be aware of and provide any guidance/assistance in this matter.

@cmlara - as you flagged this as questionable, it would make sense for you to provide more guidance as well, including:

1. "reaching out to the official maintainer" - unless I'm missing something, it appears both @dieterholvoet and @a.dmitriiev attempted to reach out to the maintainers
2. are there guidelines for recommended/required:
   1. channels for this, e.g. Slack, user profile contact form, email, etc.
   2. number of outreach attempts (or number of channels attempted)
   3. elapsed time to allow for response
3. is there also a process whereby to audit maintainers and remove inactive members - 13 seems a bit excessive, especially with no engagement on this issue from a maintainer for two months
4. should @dieterholvoet be made a co-maintainer instead to proceed?
5. what should happen now? next step?

Flagging as questionable sounds appropriate if the proper process wasn't followed, but it's not actually helpful in rectifying the issue without some additional context/direction.

I think we're getting the same error:

"drush updb" gives:
[error] Search API Autocomplete requires this module and version. Currently using
Search API version
(Currently using Unresolved dependency Search API (Version >= 8.x-1.20 required)
)

w01f → created an issue.

@freelock Hey John, I haven't changed any of the Rules on older sites in a while, haven't used Rules since they had that semi-recent overhaul to be D10/11 compatible, and am just getting started with ECA myself.

I was considering myself as more one of the eager target audience for this comparison information than a knowledgeable found of existing knowledge for... though I can contribute to a table when I find time to learn ECA better myself.

penyaskito → credited w01f → .

Also tested successfully on core 11.1

LGTM, tested on Drupal 11.1

You can't upload an SVG, but you can define the path to an existing SVG. Ideally users should be able to do either, and the basic CSS would work for most use cases - perhaps similar to how the SVG image module handles basic width and height?

Just checking in if anyone else has tested and we can possibly get this in - we're starting to ready and launch more D11 sites and so far these commits seem to allow quicklink to work for us.

w01f → created an issue.

w01f → created an issue.

w01f → created an issue.

w01f → created an issue.

Per the rules → , if the maintainer doesn't answer in two weeks the issue may be escalated to the Drupal.org project ownership issue queue.

However, someone would need to be interested in stepping up for this.

Chiming in with the same information as in my other post:

Per the rules → , if the maintainer doesn't answer in two weeks the issue may be escalated to the Drupal.org project ownership issue queue.

Just wondering how dark mode as a core feature for Claro (and Olivero) are coming along - are they still in development. I just saw this new module in contrib I'm likely to going to give a try - https://www.drupal.org/project/xclaro → .

@jurgenhaas, hey Jurgen - would you or another ECA maintainer be able to help build out the above comparison table to help describe the differences between the Rules and ECA modules for new (and existing) implementers/decision makers?

w01f → created an issue.

+1 for at least adding ECA as an alternative on the Rules description page. Also agree an easy to understand breakdown of pros/cons and key differences would be great for new Drupal users (or even old ones).

w01f → created an issue.

w01f → created an issue.

Hmm, any chance of getting a short write-up/tutorial on how to implement and example, suggested config to use for interested adopters of the new dashboard features in non Drupal-CMS projects? I think that would definitely help with exposing the feature to an initial wider audience and getting engagement (including myself =) ).

Is there a significant benefit to UI, UX, etc. from how AddToAny posts to social media? Or all things being equal, Better Social Sharing Buttons would be considered the better way to go, you think?

This.

Current navigation is:

Nav menu > Extend

• > Update (tab) shows /admin/modules/update
• > Available updates (link) shows /admin/reports/updates

Nav menu > Reports > Available updates also shows /admin/reports/updates

w01f → created an issue.

Also requesting some additional options for the filter if they don't already exist (I can't find them).

We'd like to be able to create and use custom entity reference views for the tagify autocomplete dropdown. We need to be able to change the sort (new to old, instead of old to new), and being able to add other filters would be useful as well.

w01f → created an issue.

w01f → created an issue.

This also looks good - I would add both of these to the module description page. Also, if the module can allow 3 or more individuals to chat together at once, I would have a picture depicting that as well.

Lastly, if the chat can be configured as a pop-up on the screen, as traditional chats typically are, and not as an entirely different page, I would include a picture of that.

This is a good start. Can we get screenshots of an example conversation with one or multiple users?

w01f → created an issue.

w01f → created an issue.

Confirming removing "final" line 15 in /src/Controller/CountryAutocompleteController.php file allows the site to correctly run drush updb/cr or run update.php from the site again.

Wondering if this improvement will also work for images stored in cloud storage options such as S3, Azure, etc. via modules such as the S3 File System → and Flysytem → ?
Once the images are stored in the external cloud storage, will this still work in capturing exif data on demand for already loaded/saved images and media?

I am seeing this on a site recently updated to 10.3.7 and using both country and flags modules. The php_errorlog file shows the following error:

[09-Nov-2024 10:44:22 Asia/Tokyo] PHP Fatal error: Class Drupal\flags_country\Controller\CountryFlagAutocompleteController cannot extend final class Drupal\country\Controller\CountryAutocompleteController in /home/customer/www/kobejet.com/web/modules/contrib/flags/flags_country/src/Controller/CountryFlagAutocompleteController.php on line 0

Flags (Flags Country) version 2.0.0-alpha1
Country version 2.1.0

Very interested in getting this module caught up with all recent code updates and D11 compatibility for a specific education site I maintain - any chance on getting final review and a release out? =)

Just checking in on this - have a few projects looking to upgrade to D11 that currently use Responsive Favicons. I think this is still the best solution for muliti-platform/display favicons - or is there going to be a replacement for D11?

w01f → created an issue.