Here is a patch that adding such parameter.
Hm, according to issues descriptions - not.
Reroll of #2 for latest dev version.
Reroll of #2 for latest dev version.
Batch should be used for such update hooks. Because update took large amount of time for sites which have a lot of redirects (for example we have more then 46k).
Or instead of saving the whole entity, just simple sql query is preferable. Because during execution of the update hook site is unavailable (maintenance mode is enabled automatically when updates are executing).
Fresh patch based on 11MR (but it can be applied to latest 2.3 release). And also safe to use with composer.
Here is simple patch. We just don't need to recheck link if it wasn't changed in redirect.
Faced the same issue, but only for one redirect. We have the same two modules enabled.
Was able to reproduce it locally so going to debug it in nearest days.
kala4ek → changed the visibility of the branch project-update-bot-only to hidden.
kala4ek → changed the visibility of the branch 3431537-d11-compatibility to hidden.
kala4ek → changed the visibility of the branch 3431537-d11_ready to hidden.
Fixed in 🐛 Uncaught PHP Exception Active
Fixed in 📌 Automated Drupal 11 compatibility fixes for lang_dropdown Needs review
That issue is fixing in 📌 Automated Drupal 11 compatibility fixes for lang_dropdown Needs review
Looks like locale_form_redirect_edit_form_alter() was already removed during some other ticket and patch from #8 not applied anymore. So here is updated patch.
Will try to reproduce it with clean installation.
It's issue form Entity Reference Revisions module. Try patch from 🐛 Content translation source is not taken into account for paragraphs in case of translation of host entity. Active .
Updated patch that works with nested paragraphs too.
Most probably it was solved during
🐛
Invalid argument exception when changing language of node with menu link to und or zxx
Fixed
in 10.2.x.
Please recheck and provide a feedback.
benjifisher → credited kala4ek → .
The same as patch from #17, but now with bulk delete support.
Why it's not enough to check by $translation->access('view')?
If user has access to view unpublished page (admin user for example) it make sense also to show a language link.
- Hiding all the patches except images for further confusion since we are following MR approach now.
It's a wrong approach, patches still needed, at least to be able to use it in ongoing projects with composer.
Btw, works perfectly more than half of the year.
Adapted #12 so it can be applied to 1.17 version.
Updated patch to be applicable for 1.11 version.
Hm, but how it will works with entity edit forms? Looks like now trashed entites wouldn't displayed in referency fields anymore and after submitting the form, reference would gone. That means if the admin will restore the trashed node, it wouldn't appears at the place where it was before...
amateescu → credited kala4ek → .
We may let drupal automatically remove such "non-existent permissions" during role save.
Unforchanately it doesn't fully related to simple sitemap, because it was breaked at the core level, during 🐛 Missing url prefix on language neutral content Fixed tiket.
That issue is breaks the link that must be always neutral, like links insite sitemap.xml (if there are a lot of links the additional sitemaps are generated) and most probalby some more such cases.
Because the code was relied on "not applicable" language, but now the language applied anyway...
That issue should be solved much early than module fully get rid from jquery. Because on D10 instances it already cause errors.
To get a "purge" operation ,you can try to use patch from ✨ Add "Purge" operation link Fixed .
You may create your own view. Just set a "deleted" filter and display all other columns/filter that you want.
Ypu even may palce it into /admin/content/trash path.
Simple and working patch for 9.5.x.
Added new separate filters by system path and language.
No test were changed or added, feel free to add, like during last 8 years :)
Attaching changes from MR as a patch, so it can be safely applied via composer.
Increasing the priority of that ticket, because a lot of code do compare entities in the wrong way now.
Also attached the actual changes from MR as patch, so it can be safely used with composer.
Attaching changes from MR as a patch file, so it can be safely used with composer.
Btw, just checked and it's was fixed in 10.1.x-dev during 📌 Replace most strpos() !== FALSE or === FALSE with str_contains() Fixed
Updated patch to be compatible to latest dev version.
Attaching changes from MR as a patch, just to have possibility to safety apply it via composer.
Here is a patch with support for pathauto and translations.
Here is a patch that implemented it.
Small patch that add and call "trash_restore_entity" hook.
Also need to override default ValidReference constraint.
Attaching changes as a patch file, to have possibility use it with composer.
Attaching changes as a patch file, to have possibility use it with composer.
Checked on latest 3.x-dev - it's already fixed.
kala4ek → made their first commit to this issue’s fork.
A little bit adjusted patch from #16.
Now it also tries to display the actual field name from nested paragraph.