fix: Fixed post type initialisation before ACF hooks #370
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.
…e is setting values in the constructor means ACF hooks have not fired.
Description
Issue is that ACF post types are not being picked up HWP Previews for the settings page (or any other related post type functionality).
After some investigating it was the Post Preview Service is being called before ACF hook initialisation to register those custom post types.
Fix: A small refactor that the post preview service would not set post_type, post_status on initialisation but rather when a getter method is called, to check if the property is not empty and then set the data.
Related Issue
Fixes #368
Dependant PRs
Type of Change
How Has This Been Tested?
Screenshots
Checklist