Quote Originally Posted by Dave224 View Post
mc...Can you provide additional detail? Placing #[\AllowDynamicProperties] just before the class declaration doesn't seem to help me. Is there anything else that needs to be done to temporarily kill the error messages? My webhost went from PHP 8.0 to 8.2 and I'm getting tons of error logs associated with this problem in the query_factory class. I'm in zc 1.5.7c and not quite ready to deploy 1.5.8a.

Sample log:
[16-Feb-2024 17:18:38 America/New_York] Request URI: /index.php?main_page=index, IP address: xxx
#0 /domain/includes/classes/db/mysql/query_factory.php(586): zen_debug_error_handler()
#1 /domain/includes/classes/db/mysql/query_factory.php(202): queryFactoryResult->__construct()
#2 /domain/includes/init_includes/init_database.php(52): queryFactory->Execute()
#3 /domain/includes/application_top.php(189): require('/...')
#4 /domain/index.php(25): require('/...')
--> PHP Deprecated: Creation of dynamic property queryFactoryResult::$link is deprecated in /domain/includes/classes/db/mysql/query_factory.php on line 586.

Thank you.
You say or reference the query_class, but that file has two classes declared in it, the reported issue is with the class towards the bottom of the file which is the queryFactoryResult class.

It is my understanding though I haven't again gone to test this, that the alliance to add dynamic properties is a power class allowance not a first at top of file allowance. Otherwise, one could add it to the first of many files loaded to assemble the store and it would apply across all. That to would complicate troubleshooting and development if the single inclusion applied to all of the code.

Of course upgrading to the latest software, downgrading the php version, and then other code changes might be a reasonable sequence to how to approach resolution of a significant number of different deported issues. For one that is breweries reported, the fix should be simple (famous last words).