- Issue created by @scott_euser
- Issue was unassigned.
- Status changed to Needs review
about 1 year ago 3:15pm 20 October 2023 - 🇬🇧United Kingdom scott_euser
Seems the 'Create merge request' button is broken at the moment. If you press 'Compare' on the MR, its ready to go.
- 🇮🇹Italy aronne
Hi @scott_euser,
yes what you're saying makes a lot of sense.
I'm uploading a patch that should do the work.Hope it helps,
aronne. - Status changed to Fixed
about 1 year ago 3:49pm 31 October 2023 Automatically closed - issue fixed for 2 weeks with no activity.
- Status changed to Fixed
9 months ago 12:54am 3 March 2024 - 🇬🇧United Kingdom andreastkdf
Hi aronne → ,
It looks like this was reverted by this commit on 8.x-1.6 )(and 8.x-1.x) fixing Issue #3395691 → ?
- 🇮🇹Italy aronne
Omg yes, thank you @andreastkdf
I'm gonna upload the new patch now.Thanks again.
aronne - Status changed to Needs review
9 months ago 10:16am 4 March 2024 Hello. I recently update this module to latest 1.7.0 version and I noticed this patch.
It is not implemented correctly and might lead to issues.
In my case I am using pluginformalter_form_alter_info_alter so I can dynamically add all taxonomy term form ids. This way if I create new taxonomy, the plugin for form alter will automatically work for it and I limit the risk to forget to include its specific form id.
Here it comes the issue: For you the change is working because you expect that $this->getDefinitions() doesn't return you a result and the validation below doesn't matter. You can not hit it.
In my case $this->getDefinitions() and the following $definitions = $this->findDefinitions() uses my form alter and return a results. This lead me to your change and !isset($definition['paragraph_type']) always return true and it tries to create new instance for something that is not correct.