• Resolved Harrychapp

    (@harrychapp)


    Whenever I click “Update” on a page or post, it activates the post expirator which marks the page or post as draft immediately. This expirator will be previously inactive for that page or post, and all I need to do is click “Update” regardless of if I’ve changed any settings with the post expirator.

    And yes I’ve checked in the settings, and the plugin is set to “Active” on that post type, but not set to auto-enable.

    This has become a big problem as when anyone with access changes a simple thing on a page (unrelated to the expiration status of the page), such as the body content, then the posts or page will unpublish immediately.

    This has been a problem for me for a month or so, and is happening on multiple websites I manage.

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    Hi @harrychapp

    Thanks for using PublishPress Future.

    This problems should be fixed with version 2.7.

    We still have kind of this issue with version 2.7.
    If I edit a post that was active during the plugin version with the auto-expire bug, the checkbox is still set to active by default even if it’s unset in settings.
    When I update the post and unchecked the box and edit it again, it is not checked again, so that works.

    Since we have nearly 500 posts, I am unable to edit all and uncheck the box. Will there be a fix for this?

    I can confirm the problem. and the problems and phenomena mentioned by the previous speakers 1:1 understand and observe on several of my websites.

    is there already a solution for this?

    Can confirm as well. It seems to be active for new posts by default. At least as of 2.7 it won’t reactivate when updating the post.

    This is very much not resolved.

    • This reply was modified 2 years, 11 months ago by motivmedia.
    Plugin Author andergmartins

    (@andergmartins)

    Hi guys.
    @harrychapp, @motivmedia @holzfelix @ehoff

    Thanks for the information you provided.
    We have been testing using v2.7.0 but we were not able to reproduce the bug.

    Please, could you try cleaning up the browser’s cache?
    Are you using the block or classic editor?

    If you change the field “How to expire” on the post type settings, do you see the same result? Do you see the bug? Does it expire the post using the selected option, or does it always change the post to draft?

    Are you able to reproduce the bug on a fresh site, with only PublishPress Future (Post Expirator) installed?

    Thanks.

    @andergmartins

    same issue with clean browser cache, I am using the block editor.

    I changed “how to expire” to delete -> deletes the post.

    Bug is not reproducable on a freshly installed WP instance with only Post Expirator installed.

    So it is probably a incompatibility between the current and an old version of the Plugin.

    Same issue since upgrading to Version 2.7. All previous pages and posts are set to auto expire at current time if updated.

    Expiration date needs to activated for all new pages and posts.

    Using block editor.

    NOTE: Post Expiration only shows it has been activated in the editor when the PublishPress Feature tab is opened.

    The lists of all previous pages and posts do not indicate a Expiration date has been set.
    When I click on the quick edit button for the previous posts and pages, it does not indicate Enable Post Expiration has been turned on.

    • This reply was modified 2 years, 11 months ago by Safety13.
    • This reply was modified 2 years, 11 months ago by Safety13.

    WordPress 5.8.2
    PublishPress Future Version 2.7.0

    We have updated to the latest version since we had the bugged version in the start of november, however the problem on old posts persists as there have been described in this post. Just filling in what we know about the issue

    When editing an old post with Block editor the “Enable Post Expiration” is active and set to expire the same time/date that the dit starts.

    When editing the same old page with Classic editor the “Enable Post Expiration” is not active.

    When editing the page in classic editor where the “Enable Post Expiration” is not active and just press update without changing anything. The same page has no longer “Enable Post Expiration” active in block edit.

    When editing an old page in Block editor and select to to disable the “Enable Post Expiration” and press update. When editing that same page again with block editor the Enable Post Expiration is no longer activeated.

    Regards techdep

    Uninstalling and re-installing the plugin does not help. The same problem still persists after the re-installation as it still remembers what pages was set to be expired. Anything specific we can remove after the uninstall to make it a “fresh” install.

    Or if you in the mean time could add in a feature to reset the plugins settings/history etc so it can become like a fresh install ?

    Nm, found it under advanced…

    “Preserve data after deactivating the plugin”
    “Toggle between preserving or deleting data after the plugin is deactivated.”

    However the function is broken, when set to “delete data after the plugin is disabled” and pressing save it reverts to “preserving data”. We can not get the plugin delete the data, Would like to have this feature fixed so we can check if that solves the problem.

    ————————————————————

    Found a workaround for this problem:

    In the settings for the plugin under the Advanced tab

    The function:
    Block Editor Support
    “Show Gutenberg style box” or “Show Classic Editor style box”
    Toggle between native support for the Block Editor or the backward compatible Classic Editor style metabox.

    In our install it was set to “Show Gutenberg style box”
    When altering this to “Show Classic Editor style box” we have no more problems that the plugin automatically wants to become active when editing an old post, no matter if we use Block edit or Classic edit.

    So the problem seemes to be located in the “Block editor support” and the “Show Gutenberg style box”

    Regards,
    TechDep

    • This reply was modified 2 years, 11 months ago by techdep.
    • This reply was modified 2 years, 11 months ago by techdep.
    • This reply was modified 2 years, 11 months ago by techdep.

    techdep’s workaround is not working for us, unless I’m missing something.

    I went to the plugin settings, Advanced tab, selected the Show Classic Editor style option, hit Save. I also purged/emptied WP Rocket caches, just to be safe.

    Now when I enter edit more for an existing page, the Enable Post Expirator box still is checked. Oddly, the date that it fills in is several months ago; I don’t know where that date is coming from, but it seems to be consistent across pages.

    One other thing that may be helpful: if I edit an existing page and uncheck the “Enable Post Expiration” box then save the item, then edit the same item again, the “Enable Post Expiration” box for that item is *not* automatically checked.

    For now, we will need to disable the plugin. That’s terrible because it’s a great help! But we can’t take the chance of overlooking the auto-expire on a page and having a “Page Not Found” on an important page, which caught us once already. I hope this one is fixed soon, or we have a workaround. Thanks in advance for any help.

    techdep’s workaround is not working for us either. We also disabled the plugin for now but would love to be able to activate it in the future again!

    I am encountering this with version 2.7.1 of the plugin, and have been forced to disable the plugin.

    Can confirm: bug is still present in version 2.7.1 of the plugin!

    Plugin Author andergmartins

    (@andergmartins)

    Thanks guys for the feedback.
    Please, could you try the following RC package?

    https://www.dropbox.com/s/su3osd9b1pv4gx4/post-expirator-2.7.2-rc.2.zip?dl=0

    If you still have the issue, please, could you send us the metadata of the post that are prefixed with “_expiration-“.

    Thanks,

    Anderson

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Plugin seemingly stuck on auto-enable’ is closed to new replies.