Conflict between metadata-driven scheduling and the auto-enabled scheduling

publishpress / PublishPress-Future

This plugin was known as "Post Expirator", and now it is called "PublishPress Future".

https://wordpress.org/plugins/post-expirator/

7 stars 11 forks source link

Conflict between metadata-driven scheduling and the auto-enabled scheduling #678

Open andergmartins opened 8 months ago

andergmartins commented 8 months ago

This was mainly tested using the WordPress post-import feature. If auto-enabled is checked the metadata that is expected to be imported is ignored and only the default metadata/default configuration is used and the post is scheduled.

This is related to #69.

Check the setDefaultMetaForPost method in the Plugin class.

andergmartins commented 8 months ago

Note to self: after a post is imported I see it has duplicated metadata:

Breakpoint added to the methods

ExpirablePostModel::syncScheduleWithPostMeta
ExpirationScheduler::updateLegacyPostMetaUsedBy3rdPartySoftware
Plugin::setDefaultMetaForPost