gaiusjaugustus

@baicusandrei

I purged all cache, then tested the cache. I still get the same error.

I set “Enable Cloudflare CDN & Caching” to Disabled, and then click Update Settings. The page refreshes, but “Enable Cloudflare CDN & Caching” is still set to Enabled. I tried several times with the same result. (And, tried retesting the cache again just in case, with the same failed result).

I am having the same issue on my website (https://gaiusjaugustus.com).

Cloudflare cache has been active for a long time, but I tried testing it today and got the same error. I assume our errors are related, which is why I’m posting in this same topic.

Here is my output on the test cache page:

alt-svc: h3=":443"; ma=86400
cache-control: max-age=600
cf-cache-status: DYNAMIC
cf-ray: 8db09939ae10d7a8-LAX
content-encoding: br
content-type: text/html
date: Thu, 31 Oct 2024 03:36:02 GMT
expires: Thu, 31 Oct 2024 03:46:02 GMT
last-modified: Tue, 29 Oct 2024 20:28:14 GMT
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
priority: u=1,i
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v4?s=wY2rtAihHfWQvqU5MJ6gWRdexTwu2D2DtjkY5HSFlR7rtfISsQP7yLelncyzuiisWUpO8Tx0j06srKF5oZtGQu8TflcQVLwtWNj0t6c1ehdWgKT2I1RzJQUa%2FWXFWkSH3CHfd0gtt5wdjgWwiZRhPC8%3D"}],"group":"cf-nel","max_age":604800}
server: cloudflare
server-timing: cfL4;desc="?proto=QUIC&rtt=55359&sent=1720&recv=632&lost=23&retrans=27&sent_bytes=1619192&recv_bytes=209007&delivery_rate=11703&cwnd=56607&unsent_bytes=0&cid=1480395788c82d5f&ts=130568&x=1", cfExtPri, cfHdrFlush;dur=0
vary: Accept-Encoding,User-Agent

Please disregard this. After further investigation, I don’t believe this is causing my cronjob issues. If anything changes, I’ll update this topic or start a new one. My apologies for any inconvenience.

However, the warning message *is* appearing in my error log, and it would be great to see this resolved in a future update.

I have turned off the async notification option, and unpublished/republished a post.

The email appears to have sent! I’ll check on the next email (scheduled for Thursday) and will reopen if the issue returns.

I thought that might be the case. Thanks for your assistance.

Unfortunately, the plugin is out of budget for me at the moment, so I’ll find a less ideal workaround for now.

I’ve tried “replace visibilities”, “remove selected visibilities”, and “add selected visibilities”.

None of these worked.

As I mentioned in my initial post, when I set up a Future Action for the next few minutes (for example, I just set one up for 10 minutes in the future), the action runs successfully.

However, when I set it for farther in the future (for example, tomorrow or next Thursday), I see the following:

• Prior to the future action date, the future action appears correctly in the Quick Edit menu
• AFTER the future action date, the future action is no longer shown in the Quick Edit menu or on the Edit screen
• The future action was not completed successfully.

I’m baffled by this behavior. Any assistance would be appreciated.

Hi. I can confirm that my scheduled posts (scheduled more than 7 days ago) are publishing without issue. I have 2 scheduled posts a week, and they have been publishing successfully. All were scheduled during the time I was having the issue with PublishPress Future.

@rizaardiyanto

I’ve changed the “When to notify” settings to “When content is updated” only.

Then I set up a episode’s Future action to change the visibility to “Extra Magic Content”.

At the appropriate time, the visibility changed successfully (ie, the Future action worked, verified by Debug and seeing the changed visibility)

No notification was scheduled or sent (verified by the Notification Log).

—

I also tried setting “When to notify’ to both “When content is updated” AND “When status changes from Published to Published”. The result is the same as above.

My apologies, @rizaardiyanto .

Use this link instead: https://drive.google.com/file/d/1ZpXhQH50FeRM67K6W_H-1WAPFlU5_Loa/view?usp=sharing

Thanks in advance for any assistance!

To recap:

I want to notify users when PublishPress Future changes a custom taxonomy, “Visibility”, for a custom post type, “Episode”. PublishPress Future successfully changes the Visibility (verified through debug & testing), however, a notification email is not triggered by PublishPress Planner (verified through the notification log).

@rizaardiyanto Hopefully you can view this image:

https://gaiusjaugustus.com/wp-content/uploads/Planner_Setting.png

Thanks in advance for any assistance!

To recap:

I want to notify users when PublishPress Future changes a custom taxonomy, “Visibility”, for a custom post type, “Episode”. PublishPress Future successfully changes the Visibility (verified through debug & testing), however, a notification email is not triggered by PublishPress Planner (verified through the notification log).

Hi @rizaardiyanto.

The emails are NOT in the notification log. That’s how I know it’s not working.

To recap:

The future action runs successfully (which I can see from the Debug + the updated taxonomy of the post), however the email notification is not triggered (therefore it doesn’t show up in notification log) and not received.

When the post changes from Scheduled to Published, the notification is sent successfully (and shows up in the notification log). (Note for completeness that I had to install PublishPress Statuses for Scheduled to show up as an option in the Notification form)

Oh, I should note that this is for a custom post type.

Thanks for any help!

Updating for anyone who runs across this same error.

I upgraded to Pro. When I installed the Pro plugin, the error went away.

That shouldn’t be viewed as a solution, and should be reported to developers.

Did some looking through your forum after trying a bunch of things to get jQuery loaded properly on the login page.

I found a post identifying Cloudflare’s Rocket Launcher as a potential source of the problem, so I deactivated this feature.

Now the Cloudflare Turnstile functionality seems to be working as expected! Thanks for your help in troubleshooting this. I don’t think I ever would have figured this out on my own.

Thanks for the info. That explains why it’s working on one page and not the other. I’ll enable it for the custom login once it’s working.

I set pre-clearance to Yes in Cloudflare, but I run into the same issue keeping me from being able to login.

When I login with valid credentials, I get the error message “ERROR: Your answer was incorrect – please try again.”