Taxonomy vocabularies and PHP 8.2 - needs direction / decision.
Core support for PHP 8.2 is on its way. In a previous pull request, we decided to check for property existence in function taxonomy_form_vocabulary_submit() to prevent arbitrary form item values to bloat the object, but it turns out, that's not sufficient and possibly not even appropriate.
Looking at official documentation, it seems like class TaxonomyVocabulary is actually supposed to allow dynamic properties. We just didn't realize, as hook_taxonomy_vocabulary_load() isn't used anywhere in core. And there's no functional test for that hook, either.
When I corrected this, I got the following error message:
I would start the upgrade process again from scratch, this time making sure all correct modules are in the right...
Posted2 hours 26 min ago by Alejandro Cremaschi (argiepiano) on:
https://github.com/backdrop/backdrop-issues/issues/5919
This issue was first raised in Drupal 7 in May 2011 so it actually pre-dates Backdrop itself.
I raised it in the Backdrop...
Posted2 hours 35 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
I also placed the Drupal stub version of ubercart into the modules folder rather than the Backdrop one.
When I corrected this, I got the following error message:
An AJAX HTTP error...
What I have posted is the entirety of the error message.
I do get some other error messages that show up in the course of running the update script. I'll check on what version of Entity...
Comments
Taxonomy vocabularies and PHP 8.2 - needs direction / decision.
Core support for PHP 8.2 is on its way. In a previous pull request, we decided to check for property existence in function taxonomy_form_vocabulary_submit() to prevent arbitrary form item values to bloat the object, but it turns out, that's not sufficient and possibly not even appropriate.
Looking at official documentation, it seems like class TaxonomyVocabulary is actually supposed to allow dynamic properties. We just didn't realize, as hook_taxonomy_vocabulary_load() isn't used anywhere in core. And there's no functional test for that hook, either.
Issue #6197 provides more info.
The decision has notable impact on contrib modules.