Avoid deprecated message in ajax request #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avoid deprecated message in ajax request response.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since PHP 8.2, dynamic properties are deprecated.
In exacomp/lib/classes.php, line 689, the __set() method is using dynamic properties :
So when settings my portfolio view, ajax request to /blocks/exaport/views_mod.php response with deprecated message :
Even if configuring error_reporting in php ini configuration, the deprecated message appear in ajax response. It's because error_reporting is changed in inc.php file.
The merge request is for removing E_DEPRECATED from error_reporting change made in inc.php file, so that deprecated message disappear from ajax request.