bghooke

Thanks @abzlevelup . Yes, we gave up and found another plugin to use as we were not able to solve this problem and it seemed like we could not get the support we needed to resolve this problem without paying for a pro license. So, I guess we can consider this “resolved.”

Thank you for your assistance.
Bruce

PS. I’m realizing I probably should have posted this question under the support forum for the event tickets add-on plugin. My apologies.

Thank you Jaime,

Yes, we are using your “Event Tickets” plugin Version 5.3.1 with The Events Calendar plugin. We have enabled “Tickets Commerce” in the Events settings.

I have gone through all the relevant steps in the first link you posted. We are not using Stripe so I did not use that part. On the Events > Payments tab PayPal shows as being connected.

I looked through the troubleshooting article you linked to and nothing in it seems to address our problem.

Thanks,
Bruce

It’s looking good to me too. I tested on a website where I had been seeing the problem and it’s gone now. Thanks!!!

@adamvanbuskirk My experience with this problem was that while the box would automatically be checked when we opened a post or page to edit it, if I manually unchecked the box and then saved the post no expiration date would be set, so while the problem was annoying it did not prevent us from making updates.

Oddly, this update at first appeared to have fixed the problem and then did not. I checked about 6 pages and on all the “enable” box correctly remained unchecked. Then the next 6 or so that I opened all had the box checked. And when I went back and checked the first 6 those now opened with the enable box checked when it should not be checked. I’m not sure how to account for this but I thought I’d mention it in case it provided any clues to the cause.

For what it’s worth, I checked five sites that I manage that use PublishPress Future and found the issue on 3 of the 5 sites. I could not find any pattern as to which sites and which pages within those sites exhibit the problem.

The site I observed this on does have “endurance cache” enabled. It’s set to “normal (level 2)”. The host is Bluehost. I tried turning it off and it did not have an immediate impact on the issue. When this problem occurs the expiration date and time set in PublishPress Future is the date and time I opened the page to edit it, so this is not just a question of the check box selection being cached.

Thank you for the speedy response, Steve. Sadly, this does not appear to have resolved the problem. Curiously the issue does not arise on all pages. I tried the pre-release version first on a new site I’m working on now and I was not able to reproduce the problem there with either 2.7.0 or 2.7.1-rc.3. Then I switched to the site that first reported the problem to me, that has pages published over the course of the past few years. There I was able to reproduce the problem with no apparent difference between the 2.7.0 and 2.7.1-rc.3. Oddly, not all pages exhibited the issue but I’d say that 90% did. I could not find a pattern as to which pages did and which pages did not.

We are having the same problem with version 2.7.0. This is EXTREMELY undesirable behavior as it’s easy to forget to turn off the unwanted expiration date when all we did was log in to update a page, and if we forget then key pages on the website can suddenly disappear. We also have “Auto-Enable” disabled.

@stevejburge I was able to confirm the issue on:

1. Windows 7 on a reasonably current versions of Firefox and Chrome
2. Apple iPhone using native Safari browser. I don’t get a pop-up message warning me that if I leave the post my changes won’t be saved but that’s because this browser does not appear to allow such messages. Even if I manually make a change to the post I can leave it without a warning being generated. The tip off that the problem is still occurring is that the “update” button is enabled as soon as I open the post, which only happens if WordPress thinks the post has been changed.

This is all using the test site I created that is just a clean, new installation of WordPress with the post expirator plugin added.

Hi @stevejburge Thank you. I checked on two other sites I manage and was able to reproduce the problem on those sites and so as a final check I installed a clean copy of WordPress and left the theme at the default: twenty Twenty-One. The WordPress version shows as 5.8.1, which I believe is the current version. I added only the Post Expirator plugin to this WordPress installation and I deactivated Akismet and deleted Hello Dolly. I was still able to reproduce the problem. To make sure we’re on the same page, here are the steps to reproduce the problem:
1. Activate the Post Expirator plugin.
2. Open a post as if to edit it.
3. Do nothing else and try to leave the post edit screen by clicking somewhere else on the WordPress menu.
4. With Post Expirator activated I always get a prompt to save the post.
IF I deactivate Post Expirator I do not get such a prompt.
I checked the console and did not see any errors. I also checked the website error log and did not see any errors.
Thanks,
Bruce

@stevejburge Thanks. I updated to version 2.6.2 and unfortunately that did not solve the problem.

Thank you MM.

On #1 the directions did not seem to fully apply since there isn’t a new language file for me to download so I jumped down to the “manually editing…” section. Here’s what I did, that did not seem to work:

1. Found the file wp-user-frontend.pot in the folder wp-user-frontend/languages and opened it Poedit.
2. Clicked on the button to “Create new translation” and selected “English (United States)”
3. Searched for the line in question and edited it.
4. Saved the file as wp-user-frontend-en_EN.po in the folder wp-user-frontend/languages (I also tried putting it in “/wp-content/languages/plugins/”)
5. Uploaded the new .po and .mo files
6. Checked to see if the message had changed. It had not.

What did I do wrong?

On #2, it looks like that issue has been fixed. If we can figure out #1 I will probably edit this message but the basic issue has been addressed.

Hello, I have confirmed that we are still experiencing this problem and want to know what the next step is to try to get a resolution? Thanks!
Bruce