🇺🇸United States @inversed

I found this which provides a possible explanation for how UID 0 is lost, what it does, and how to restore it:

https://www.drupal.org/docs/administering-a-drupal-site/troubleshooting-... →

I'm also experiencing this on a new build and I'm wondering how this issue happened. This post's comment provides a patch but I'd like to understand the underlying cause.

https://www.drupal.org/forum/support/post-installation/2019-12-23/unexpe... →

I think the main issue is that this would need the same type of warning message shown when the Service ID or API key are overridden.

Warning message
Site id is overridden in settings.php or with environment variable so it's not shown in the config form.

I converted the patch to a merge request. Hope this helps!

I can confirm that this patch works as expected and we've been using it in production for since the beginning of 2024.

inversed → made their first commit to this issue’s fork.

The new 1.1.0-beta3 release should solve this issue.

It looks like this issue is coming from php 8.2+. The affected nestedSetFactory property needs to be declared in the class.

See: https://git.drupalcode.org/project/entitree/-/blob/1.1.0-beta2/src/Entit...

I wanted to add that I'm seeing this problem with version 2.0.6 as well. The patch does not apply on that version but that's not unexpected.

#26 works for me using existing config sync yaml on a fresh install.

Confirmed here as well. Either disabling Devel Generate or the patch, both solutions work with Webform 6.2.2 and Devel 5.1.2.

Fixed and closing this issue.

If it helps, I think the documentation on the anchor_link → project page is well written. It explains how to do this with wikimedia/composer-merge-plugin in composer or in other ways. This is an old ticket and, at some point, that plugin was not usable (maybe during one of the Drupal major release transitions) but it is working very well now. However, right now, with Drupal 10, I am using the composer.libraries.json approach for both Anchor Link 3.0.0-alpha1 and Webform 6.2.2.

Something else that may have be causing confusion is the issue mentioned in #41. The Colorbox documentation shown on the Status Report and the Project page is subtly incorrect. On case-sensitive operating systems like Linux, "libraries/DOMPurify/dist/purify.min.js" is going to fail because the module is actually looking for "libraries/dompurify/dist/purify.min.js". So, yes, that is an unrelated problem

For anyone having trouble getting to 6.0.3, this is the command I used. Essentially, I needed to update the out of date supporting jquery_ui dependencies at the same time as BEF.

composer require drupal/better_exposed_filters:^6.0.3 drupal/jquery_ui_datepicker:^2.0 drupal/jquery_ui_slider:^2.0 -W

Otherwise, I kept ending up on BEF 6.0.2 which does not include the fix from this issue. I had those packages required specifically so they were locked and composer was not able to update BEF, even when specifying the with-all-dependencies argument.

@tkim49, the typical way to deal with this can be found here: https://www.drupal.org/docs/develop/git/using-gitlab-to-contribute-to-dr... →

Essentially, adding a composer plugin and white-listing the project should let you require it and apply the patch. I've confirmed on my local that this is working (I've used this for other projects).

In your composer.json file, in the extra property, you would need to add the following:

        "drupal-lenient": {
            "allowed-list": ["drupal/adobe_launch"]
        }

And in the config.allow-plugins property, you would need to add the following:

    "mglaman/composer-drupal-lenient": true

First, thanks for the hard work in getting this out to the community! The alpha 7 version with this patch seems to be working for me on Drupal 10. The one question I have is about the indexing. It looks like all applicable fields get indexed when enabling the module or saving the settings. The instructions mention enabling indexing on a per-field basis on an entity's field storage screen. Is that intentionally no longer the right way? My field storage page does not have those controls. My View does give me the option to "Sort ascending naturally" and it's working, which is great.

However, my views_natural_sort table now has almost 37,000 records when I was expecting more like 50 (for the single field I need this for). The indexing process went Indexed 158,736 entries.

Is that the expected behavior?

That composer plugin solved it for me as well.

If you only need a default paragraph created, there is a module to add this functionality: https://www.drupal.org/project/migration_tools →

This is by far the quickest way to generate a paragraph entity during the migration process.

Here is their example YAML:

  field_some_paragraph_entity_ref_revison:
    plugin: create_default_paragraph_revision
    paragraph_default:
      create_paragraph_bundle: paint_recommendation
      field_color: blue
      field_paint_type: latex
      field_coats: 2
      field_exterior_use: true

With some help, it looks like the fix is to scope the 100% width more specifically to gin.

.gin-entity-browser .media-library-item--grid {
  width: 100%;
}

The main takeaway is:

• Prevents making thumbnails on main Media Library page giant: /admin/content/media-grid
• Fixes thumbnails in Media Library browser in CKEditor4 media entity embed
• Fixes thumbnails in Media Library browser in Media Entity Reference fields

Note that I happened to have an old field still using the Media Entity Browser widget (not Media Library). That one was still showing the tiny thumbnails. So the solution was to set this to use the same widget as all the other Media Entity Reference fields.

This was super helpful! I modified the patch to work without a dependency on the menu items extra module as well as set the language selection to use the content.

This is working for me on 8.x-1.7.

I modified the patch a bit to get this working:

• Fetch the entity before checking the translation
• Check against the content language (should match the menu items in general) and not the current language

Is this patch still working in Drupal 9.5.x? When I apply it, I get the following error:

Error: Call to undefined method Drupal\menu_link_content\Plugin\Menu\MenuLinkContent::hasTranslation() in template_preprocess_tb_megamenu_item() (line 687 of modules/contrib/tb_megamenu/tb_megamenu.module).

It seems as if this was an accident. Perhaps the intent was to move Durpal 10 development to the 4.x branch?

I'm bumping this up to critical as it's essentially a blocker preventing any new installations of this module on Drupal 9. If I'm incorrect and the intent is for end users to either remove the module from their sites or force a switch to the 4.x dev release, that needs to be addressed specifically.

Additionally, the change log mentions "minor fixes" but it seems like maybe kind of a lot of things updated? Here's a comparison of 3.14 to 3.15: https://git.drupalcode.org/project/fastly/-/compare/8.x-3.14...8.x-3.15

I am getting the errors after installing 2.0 and have never had 1.0 installed. I cannot successfully apply the patch from the MR, though.

This is on Drupal 9.5.3, PHP 8.1.x, and MariaDB 10.4.

I ran into this in Docksal (local development) with Apache 2.4. I went around and around before realizing it was the Surrogate-Key in the header. I am also using Paragraphs and with all the nesting, there are many entries in there.

In my case, only pages with lots of Paragraphs were failing.

config:block_list config:block.block.areasofresearch config:block.block.b5primary_content config:block.block.b5primary_help config:block.block.b5primary_local_actions config:block.block.b5primary_local_tasks config:block.block.b5primary_messages config:block.block.b5primary_page_title config:block.block.impactgoals config:block.block.sharetools config:block.block.b5primary_account_menu config:block.block.b5primary_branding config:block.block.sitebranding_fr config:block.block.b5primary_breadcrumbs node:14 config:block.block.charitableregistration config:block.block.mscanada config:block.block.termsprivacy config:block.block.connectingcanadians config:block.block.footerlinks config:block.block.sociallinks config:block.block.connectlearn config:block.block.donationassistance config:block.block.inquiries config:block.block.takeaction config:block.block.exposedformsearchpage_search config:block.block.languageswitcher config:configurable_language_list config:block.block.readingprogressbar config:block.block.utilitynavtop config:block.block.exposedformsearchpage_search_mobile config:block.block.languageswitcher_mobile config:block.block.mainnavigation_mobile config:block.block.menu_about_us_mobile block_content:1 config:block.block.megamenu_about_us config:block.block.menu_find_support_mobile block_content:2 config:block.block.megamenu_find_support config:block.block.menu_get_involved_mobile block_content:3 config:block.block.megamenu_get_involved config:block.block.menu_intro_to_ms_mobile block_content:4 config:block.block.megamenu_intro_to_ms config:block.block.menu_managing_ms_mobile block_content:5 config:block.block.megamenu_managing_ms config:block.block.menu_ms_research_mobile block_content:6 config:block.block.megamenu_ms_research config:block.block.readingprogressbarmobile config:block.block.utilitynavtop_mobile config:block.block.mainnavigation_2 config:block.block.msdonateblock config:block.block.newslettersignupfooter config:block.block.views_block__related_articles_related_article_cards_block config:block.block.views_block__related_blog_posts_related_blog_posts_cards_block block_view config:simple_block.simple_block.charitable_registration config:filter.format.full_html config:system.menu.terms-privacy config:simple_block.simple_block.ms_canada config:simple_block.simple_block.social_links config:simple_block.simple_block.footer_links config:simple_block.simple_block.connecting_canadians config:system.menu.donation-assistance config:system.menu.inquiries config:system.menu.take-action config:system.menu.connect-learn config:simple_block.simple_block.newsletter_sign_up_footer node_view config:core.entity_view_display.node.flexpage.full config:views.view.related_content_default node_list config:layout_builder_styles.style.dsk_4_col_grid_lb_section config:layout_builder_styles.style.post_content_section paragraph_view paragraph:171 config:paragraphs.settings paragraph:170 config:core.entity_view_display.paragraph.carousel_embed_dynamic.default config:views.view.latest_research_carousel node:61 node:72 node:60 node:71 node:383 node:22 node:70 node:59 node:15 config:field.storage.node.field_highlighted paragraph:286 config:core.entity_view_display.paragraph.herospace_default.hero_title config:filter.format.title_html user:9 paragraph:344 taxonomy_term:35 taxonomy_term:36 paragraph:285 paragraph:343 paragraph:676 user:0 paragraph:48 paragraph:342 paragraph:284 paragraph:291 user:3 config:core.entity_view_display.paragraph.carousel_promo.default paragraph:141 paragraph:140 config:views.view.bf_red_list_template node:1212 node:1205 node:1207 node:1209 node:1204 node:1200 node:5 node:76 node:78 node:77 paragraph:1893 user:20 paragraph:1886 paragraph:1888 paragraph:1890 paragraph:1885 paragraph:1881 paragraph:160 taxonomy_term:2 taxonomy_term:3 paragraph:348 paragraph:350 paragraph:349 paragraph:139 config:core.entity_view_display.paragraph.spacer.default paragraph:134 paragraph:131 node:20 node:4 node:19 config:core.entity_view_display.paragraph.related_links_embed_curated.default config:core.entity_view_display.paragraph.promo_links_advanced.default paragraph:133 config:core.entity_view_display.paragraph.info_block.default config:layout_library.layout.info_block_right_image media_view media:17 config:core.entity_view_display.media.image.default config:image.style.original file:21 config:filter.format.rich_text paragraph:132 paragraph:130 paragraph:129 config:core.entity_view_display.paragraph.related_links_embed_auto.default config:views.view.related_content_links config:core.entity_view_display.paragraph.related_links_alt_wrapper.default paragraph:128 config:core.entity_view_display.paragraph.content.default paragraph:127 paragraph:126 paragraph:125 node:23 node:31 node:27 config:core.entity_view_display.paragraph.related_links_alt_embed_curated.default paragraph:124 paragraph:68 config:core.entity_view_display.paragraph.testimonials.default paragraph:67 config:core.entity_view_display.paragraph.testimonial.default config:layout_library.layout.testimonial_slide_left_image media:5 paragraph:66 config:layout_library.layout.testimonial_slide_right_image paragraph:65 paragraph:30 media:7 file:11 paragraph:29 config:core.entity_view_display.paragraph.promo.default media:8 config:core.entity_view_display.media.image.card config:image.style.card_default file:12 paragraph:28 config:core.entity_view_display.paragraph.media.default paragraph:27 config:core.entity_view_display.paragraph.dynamic_lists.default config:views.view.blog_list node:81 node:79 node:80 paragraph:224 taxonomy_term:70 paragraph:353 taxonomy_term:67 paragraph:351 taxonomy_term:69 paragraph:352 taxonomy_term:68 paragraph:70 paragraph:36 paragraph:19 config:core.entity_view_display.paragraph.block_reference.default paragraph:26 paragraph:25 config:core.entity_view_display.paragraph.content_grid_item_existing.default paragraph:24 paragraph:23 config:core.entity_view_display.paragraph.content_grid.default paragraph:95 paragraph:94 config:core.entity_view_display.paragraph.related_links_wrapper.default paragraph:93 paragraph:92 paragraph:91 paragraph:90 paragraph:22 node:1 config:layout_builder_styles.style.adv_content_section paragraph:31 config:layout_builder_styles.style.herospace_section config:system.site block_content_view config:core.entity_view_display.block_content.basic.default node:57 node:48 config:system.menu.main config:system.menu.utility-nav-top config:system.menu.account config:tb_megamenu.menu_config.main__b5primary config:system.theme config:admin_toolbar_tools.settings config:system.menu.admin config:node.type.page config:node.type.blogpost config:node.type.event config:node.type.flexpage config:node.type.research config:node.type.publication config:node.type.person config:node.type.pressrelease config:node.type.article config:node.type.supportgroup config:node.type.symptom config:comment.type.default_comments config:contact.form.personal config:contact.form.simple_contact_form config:contact.form.feedback config:entityqueue.entity_queue.staff_listing views_data entity_field_info config:media.type.audio config:media.type.file config:media.type.image config:media.type.remote_video config:media.type.video config:system.menu.devel config:system.menu.footer config:system.menu.tools config:system.menu.utility-nav config:system.menu.second-utility-nav config:system.menu.workbench config:paragraphs.paragraphs_type.layout_paragraph config:paragraphs.paragraphs_type.block_reference config:paragraphs.paragraphs_type.carousel_embed_curated config:paragraphs.paragraphs_type.carousel_embed_dynamic config:paragraphs.paragraphs_type.carousel_promo config:paragraphs.paragraphs_type.contact_form_ref config:paragraphs.paragraphs_type.content_grid config:paragraphs.paragraphs_type.content_grid_item_custom config:paragraphs.paragraphs_type.dynamic_lists config:paragraphs.paragraphs_type.content_grid_item_existing config:paragraphs.paragraphs_type.featured_content_section config:paragraphs.paragraphs_type.from_library config:paragraphs.paragraphs_type.carousel_embed_hp_hero config:paragraphs.paragraphs_type.carousel_slide_hp_hero config:paragraphs.paragraphs_type.carousel_slide_content_hp_hero config:paragraphs.paragraphs_type.html_pattern_reference config:paragraphs.paragraphs_type.herospace_default config:paragraphs.paragraphs_type.herospace_hp config:paragraphs.paragraphs_type.info_block config:paragraphs.paragraphs_type.content config:taxonomy.vocabulary.research_affiliation config:taxonomy.vocabulary.areas config:taxonomy.vocabulary.research_areas config:taxonomy.vocabulary.locations config:taxonomy.vocabulary.blog_type config:taxonomy.vocabulary.category config:taxonomy.vocabulary.country config:taxonomy.vocabulary.event_type config:taxonomy.vocabulary.flex_type config:taxonomy.vocabulary.geo_region config:taxonomy.vocabulary.impact_goal config:taxonomy.vocabulary.location_type config:taxonomy.vocabulary.people_type config:taxonomy.vocabulary.attendees_support config:taxonomy.vocabulary.research_priority config:taxonomy.vocabulary.research_topics config:taxonomy.vocabulary.research_study config:taxonomy.vocabulary.languages config:taxonomy.vocabulary.symptom config:taxonomy.vocabulary.tags config:user.role.anonymous config:user.role.authenticated config:user.role.designer config:user.role.content_editor config:user.role.content_manager config:user.role.site_manager config:user.role.site_developer config:user.role.administrator config:user.role.user_manager rendered http_response local_task config:workflows.workflow.editorial scheduled_transition_settings scheduled_transitions_for:node:14 config:devel.toolbar.settings config:shortcut.set.default user:1

And a follow up to my last post - unfortunately, this problem is still around for some situations. So I still need to explore a more refined approach.

Also, in case anyone did not realize, now that the roave/security-advisories package is aware of this, it blocks a composer update if the installed firebase/php-jwt package is 5.x.

I didn't have any problems manually requiring firebase/php-jwt:6.0 and it looks like the salesforce:5.0.x-dev version has an updated composer.json to support 5.0 or 6.0 so I figure this issue will get resolved eventually.

I was having this problem as well and had a similar solution in place (based on this issue). However, after recent Drupal and module updates, my fix introduced a regression error. I started seeing a problem where the Media Library thumbnails were full width in the modal (giant images). In particular, the Media Library can be accessed in the Form Display widget for media entity reference fields or in the CKEditor media embed browser. The responsive CSS code would fix the reference fields but break the CKEditor embed browser.

Ultimately, I now only need the following and removed the various media query workarounds:

.media-library-item--grid {
  width: 100%;
}

The fix for this was to call the event instantiation with once and update the JS and libraries.yml to support this.

inversed → created an issue.