Moving this to fixed, given the follow-up already fixed 🐛 Fata error with Drupal 11 Active
Hi, could we please get a new tagged release with this change?
Same here, but re-installing the module fixes the issue
This regressed with changes from #3153682: Move duplicate code in OpenIDConnect to auxiliary function → .
My bad. The error occurs at json_decode() (line 59), before any of our processing logic runs. This confirms the raw JSON response data is too large and not the parser at fault.
@orkut murat yılmaz yes, but we need one for Project Browser →
I've added relevant changes together in MR 19 from ✨ GUI of regex_redirect does not support targets without a pattern Active that allows for all languages applied on a redirect.
Looking at this again and I can understand why, but am reluctant to add this in a minor or patch release as I believe it could break existing installations in terms of styling. I think we need some more review, testing and thoughts on this.
Sorry for the delay and thanks for the details so far, but I would need a little bit more steps to reproduce.
I appreciate this is an old bug report but tested both on latest 2.x and 3.x with Ajax on Webform without issues. If this is still happening please feel free to re-open.
Sorry I didn’t get back on this but it would have to be an extended functionality on the form element and the field widget / Webform depending on where you want it.
However given the underlying library being archived, I suggest this to be looked at in 3.x of this module.
baikho → created an issue. See original summary → .
@rajveergang the module uses the current node as a parent for a new node that will be created, hence it doesn't make sense to add an operation link in admin/content. You can add a child page while editing or viewing a node, and the idea is that you don't need to go down the menu links, you can add a children to the current node.
Please see ✨ Add dropbutton in Content overview Active . This approach has been working well for our client, though I understand it may not align exactly with the direction you envision for the project moving forward.
After testing, I think we should still support target URLs using the internal schema when the named capture is omitted. This would make it easier to use and ensure the redirect continues to work if the target path changes.
Tried to backmerge 2.0.x for the MR patch to update but somehow it shows a whole different diff yet https://git.drupalcode.org/project/regex_redirect/-/merge_requests/12.patch
So instead manually adding patch from MR 12
Keeping it as a procedural hook_entity_operation implementation for BC with D10