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.
Posted1 day 50 min ago by Graham Leach (Graham Leach) in Other
Recent comments
Heya @adamg
First of all...no need to apologize. I was just trying to clarify what module(s) you were talking about so help would (hopefully) be more forthcoming.
I had to do a...
Posted9 min 49 sec ago by Graham Leach (Graham Leach) on:
Apologies for not being clear, and getting the name of the Backdrop module wrong!
On D7, I'm using a combination of Location and GMaps (and Views) to store and display locations on maps...
Leaflet on its does not provide fields, from what I understand. Which module do you have installed in Backdrop to provide fields? Is it geofield? And we're you using Location module in Drupal 7?
Hello @argiepiano,
I made a technical observation. Did you respond with a policy observation?
For a fruitful discussion to occur, we need to be in the same continuum.
NODE ID...
Posted2 hours 32 min ago by Graham Leach (Graham Leach) on:
Hi. Why do you need to validate node IDs? Node IDs are never entered through the UI. They are assigned to the node when saved, by the database server. There is no administrative UI that asks the...
Posted2 hours 50 min ago by Alejandro Cremaschi (argiepiano) on:
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.