I recommend to anyone seeing this issue, please switch to linkchecker 2.1.0-beta1 or newer
2.1.0-beta1 does not have DER and will not have this problem. The very complex DER module (dynamic_entity_reference) module is no longer a requirement in version 2.1.0 versions of linkchecker.
I recommend to everyone to upgrade to 2.1.x
While the faked out null author does cover the use case and is a good test, if someone really wants to go for a ride into wonderland there's possibly an explanation.
Our node bundle has a translated author field and we have two languages.
We also use the ETUF module (entity_translation_unified_form) so both author values are loaded into the same edit page. In our case since the same user edits both languages we probably should have disabled translatability on author. With that said, might explain why it was tricky to write a test.
With that said, our particular case, we should turn off translatability on the author since the same submit button saves two versions of a node (ETUF is amazing)
have a look at the pipeline https://git.drupalcode.org/issue/feeds_para_mapper-3548675/-/jobs/6660687
Please investigate.
There was 1 failure:
1) Drupal\Tests\feeds_para_mapper\Functional\ImportingTest::testThings
Behat\Mink\Exception\ElementNotFoundException: Button with id|name|label|value "Save and continue" not found.
/builds/issue/feeds_para_mapper-3548675/web/core/tests/Drupal/Tests/WebAssert.php:159
/builds/issue/feeds_para_mapper-3548675/web/core/tests/Drupal/Tests/UiHelperTrait.php:75
/builds/issue/feeds_para_mapper-3548675/tests/src/Functional/FeedsParaMapperTestBase.php:247
/builds/issue/feeds_para_mapper-3548675/tests/src/Functional/FeedsParaMapperTestBase.php:221
/builds/issue/feeds_para_mapper-3548675/tests/src/Functional/FeedsParaMapperTestBase.php:151
/builds/issue/feeds_para_mapper-3548675/tests/src/Functional/FeedsParaMapperTestBase.php:77
/builds/issue/feeds_para_mapper-3548675/tests/src/Functional/ImportingTest.php:19The ^3.0.0@beta releases have support for custom workflows.
For those using the editorial workflow, stick to version ^2.0
@avpaderno, is there another two weeks that have to pass before we can move this over to the ownership queue?
Ok thanks for this, I will review any merge requests/patches submitted forward for filehash_report since I do know the the current report could be a lot more useful and flexible using the view approach.
joseph.olstad → created an issue. See original summary → .
This should be tesolved in 1.6 , please re-test and provide feedback if there's still an issue.
In any case, the patch here no longer applies to version 1.6
https://www.drupal.org/project/menu_export/releases/8.x-1.6 →
joseph.olstad → made their first commit to this issue’s fork.
joseph.olstad → made their first commit to this issue’s fork.
Unable to create a new branch from 2.2.x due to the upstream fork pre-dating 2.2.x
2.1.x cannot be merged into 2.2.x since it has D10 only stuff commits made after 2.2.x
Therefore, I recommend either creating a new issue, new branch from 2.2.x and merge request going from that to 2.2.x in the new issue and linking it to this one OR rely solely on patches provided by @seanb comment #93 for latest patch.
joseph.olstad → changed the visibility of the branch 2820400-ajax-request to hidden.
@rajeshreeputra, I see you tagged 8.x-1.8 (Thank you), however you may have forgotten to create the release build , I still see 1.7 on the project page.
Try this release:
composer require address_suggestion:'1.0.15'
eventually when you upgrade to Drupal 11 you'll have to do this:
composer require address_suggestion:'^1.0.15'
However when using Drupal 9, try locking to 1.0.15 , I am guessing it will likely work.
composer require address_suggestion:'1.0.15'
We probably should have dropped 9 starting at 1.0.16
Very nice touch with the video, and ya bonus, conditional fields, this is how it was meant to be!
Also worth mentioning, it's a global search replace. This is needed since one page could have multiple charts. When I was testing the early solutions only fixed the first chart. Now unlimited charts are displayable on the same page without error.
@smulvih2 , yes it's a configurable filter and the default is exactly what data tables (the js that propulses these wet-boew charts) needs fixes for. the is caused by ckeditor4 / ckeditor5 , both versions have the same issue, they insist on adding to a
and this empty td is required for the charts to work.
Perhaps we cook in the same filtering into one of the existing WxT text filters?
with that said, I see where you're comming from. I wanted a simple solution that both fixes the issue and makes it obvious as to what it's doing.
Merged the README.md changes. I'll mark this as fixed since the documentation (README.md) is improved.
two years later wxt_chart_stability is still functional and also works well in D11 with ck5
Today, september 23rd 2025 I reached out to ALL of the maintainers of this project with the following message:
Subject: Fontyourface needs a Drupal 11 fix
Hello {maintainer first name},
I am writing to you since you are a maintainer of the fontyourface project.
There is a Drupal 11 compatibility fix that needs to be merged/tagged and released.
https://www.drupal.org/project/fontyourface/issues/3465748 ✨ Drupal 11 compatibility fixes for fontyourface Active
Please action this item.
I am also writing to your co-maintainers the same message.
Thanks,
{My name}
{My company name}
{My phone number}
{My email address}
If no action in two weeks I suggest invoking the project ownership process.
I gave everyone here credit since it all helps however it was really bzaher that actually delivered the solution. Would be nice if there was a superstar credit or a star icon to put on.
The closest thing I can see that relates to this is:
🐛
Undefined array key "column_relations"
Fixed
Unfortunately this is all the help I can give for the moment. If you have a patch that helps this scenario please push it into a merge request or upload the patch. It'll get reviewed.
Hi @mfb,
I added you as a maintainer to filehash_report
Feel free to start a new branch for this views filter support, once the filehash module gets your patch we can publish a tag of the new branch.
smalot/pdfparser is still actively supported.
There's a new release: https://github.com/smalot/pdfparser/releases/tag/v2.12.1
Probably could re-test the patch → now.
Please review also:
#3547589-3: Unable to add table - Undefined array key "created_by" →
Perhaps our README.md is insufficient.
Check the " Notes for developers 🐛 Unable to add table - Undefined array key "created_by" Needs review "
About
- View custom table module provide you functionality to integrate your custom table data to views, and access all it's column in views. This module use hook_view_data to add custom tables in views. this module provides you following functionalities.
- Auto integrate custom table data to views
- Auto map mysql data types with drual data types
- Extend relationship of custom table data to drupal entities
How to use:
- Download and extract files in module folder.
- Enable module from module list
- Go to Home » Administration » Structure » Views » View Custom Table
- Add your custom table in system using "Add Custom Table" link
- Add Relationship with drupal entities if any, otherwise leave none.
- Clear drupal cache
- Add a new view and you will see your custom table name in "Show" drop-down field.
Notes for developers
- Each custom table must have a primary key.
- Column related to drupal entity must be numeric.
CONFIGURATION
Configure user permissions in Administration » People » Permissions:
- Add custom table in views
- Give user access to add his custom table to the system.
- Administer all custom table in views
- Give user access to administer all the custom tables, added by all the users
- Administer own custom table in views
- Give user access to administer own custom tables
Manage custom tables in
- Administration » Structure » Views » View Custom Table menu.
There's a patch here:
🐛 Relations doesn't work for entities without data_table Needs review
if you confirm that patch 3384069 works, I'll merge it.
yes hitting this on the latest tagged release, would be great to get a newly tagged release.
Still testing/reviewing the patch. So far so good.
The media field shows up in both languages, very cool.
Will have to test with a non-translatable media file just to make sure it doesn't spontaneously make it translatable.
@anybody, we upgraded to D11 in february and we're using layout_builder_st and recently updated layout_builder_st
Patch we're using (page manager compatibility bug fix)
"drupal/layout_builder_st": {
"3069964 - Null fix for moderation dashboard, otherwise WSOD on login": "https://www.drupal.org/files/issues/2025-08-27/layout_builder_st-3069964-41.patch"
},
Version of layout_builder_st:
{
"name": "drupal/layout_builder_st",
"version": "dev-2.0.x",
"source": {
"type": "git",
"url": "https://git.drupalcode.org/project/layout_builder_st.git",
"reference": "ea9ed7ee77369f2be64b3e925ac4a7a454920b74"
},
"require": {
"drupal/core": "^10.2 || ^11"
},
}We've been using this with Drupal 11.1.8
@rajeshreeputra, please tag a new release for jquery_ui , it has been approximately 18 months since a tagged release!
tests came out bad, cancelling this ticket as works as designed.
joseph.olstad → changed the visibility of the branch 3546871-prevent-form-anomalies to hidden.
if you're on 2.0.x like me, I recommend 2.0.38 or newer 2.0.x
you'll likely want 2.0.38
🐛 Prevent form anomalies from resulting in multiple confirm dialogs Active
@ldenna , this is an eslint patch from the gitlab-ci automated pipeline that I've pushed into a merge request. Expecting no change to functionality. With that said, it is a patch that needs to be tested against moderated_content_bulk_publish 2.0.38
Hoping that you can help me test and review it.
Thanks ldenna for your assistance with this. It was a tough one to figure out.
Fix likely be ported to 3.0.x however too many merge conflicts to cherry-pick so I'm not going to do it until I start using 3.0.x more often or unless someone else pushes up a merge request then I will review it.
With that said, I have another gin improvement to make.
hmm, Tabbed mode no longer seems to work with Claro, probably should set the default to Inline mode.
Here's the patch for testing purposes. https://git.drupalcode.org/project/entity_translation_unified_form/-/mer...
very interesting @bzaher, I'll test it myself right now.