Avoid Sync Types Fatal Errors #1085
Merged
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.
This ensures that even if the sync types aren't loaded, there's no fatal errors due to sync_types being null.
Approach
Main reason: Current fatal errors occurs because the
sync_typesproperty is set to null (instead of an array). By default, properties in PHP are initialized as null unless told otherwise. By initializing it to an empty array, we can guarantee these fatal errors won't occur.More detailed investigation of the reported issue:
sync_typesproperty is assigned only in one place, which is thesetup_sync_typesmethod, which comes originally from thisinitfilter with a priority of 200 https://github.com/cloudinary/cloudinary_wordpress/blob/master/php/class-plugin.php#L278initfilter of priority 125. This means this executes beforesync_typeswp_get_attachment_image_srcwithin its settings page, which in turns calls our own cloudinary filter, resulting in the sync_types variable being called before it is initialized.Here's a stack trace of the issue (using XDebug)

QA notes
Two approaches:
Rank Math SEOplugin%post_thumbnail%variable