WPIntell

Source evidence

Deprecated warnings in PHP 8.2

Gallery PhotoBlocks · support · 2024-12-09T08:28:00+00:00

mixedsentiment
mediumseverity
0.78relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

9 / 37 rows with source links

24.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
leemon resolved
Your plugin is throwing some deprecated warnings in PHP 8.2 with WP_DEBUG constant set to true : Deprecated: Creation of dynamic property Photoblocks_Admin::$dashboard_page is deprecated in /xxxx/wp-content/plugins/photoblocks-grid-gallery/admin/class-photoblocks-admin.php on line 437 Deprecated: Creation of dynamic property Photoblocks_Admin::$add_page is deprecated in /xxxx/wp-content/plugins/photoblocks-grid-gallery/admin/class-photoblocks-admin.php on line 445 Deprecated: Creation of dynamic property Photoblocks_Admin::$troubleshooting_page is deprecated in /xxxx/wp-content/plugins/photoblocks-grid-gallery/admin/class-photoblocks-admin.php on line 453 The warning occurs because PHP 8.2 deprecated dynamic properties—properties that are not declared in the class but are created dynamically at runtime. To fix this, you should explicitly declare the properties in the class. Hello @leemon , Thank you for bringing this to our attention! I’ve opened a ticket with our development team to address this issue. You can track the progress and updates here . We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we work on a fix. If you have any other questions or concerns, please don’t hesitate to let us know! Best regards, Beatrice. This topic will be marked as resolved as we have an open ticket on GitHub regarding this. Please keep in mind that the ‘resolved’ status is only for this support thread, not the issue on GitHub.

Comments

2 shown
beatrice12 2024-12-17T12:03:00+00:00

Hello @leemon , Thank you for bringing this to our attention! I’ve opened a ticket with our development team to address this issue. You can track the progress and updates here . We sincerely apologize for any inconvenience this may have caused and appreciate your patience while we work on a fix. If you have any other questions or concerns, please don’t hesitate to let us know! Best regards, Beatrice.

beatrice12 2024-12-30T12:48:00+00:00

This topic will be marked as resolved as we have an open ticket on GitHub regarding this. Please keep in mind that the ‘resolved’ status is only for this support thread, not the issue on GitHub.