mhartste
Forum Replies Created
-
Thanks for your reply and suggestion. Yes, I turned off caching, same issue.
Thanks for all your help, @joneiseman. I think the issue is now solved.
I added an exception to the firewall to not cache that event page. It now seems to work on my testing and confirmed from one of my users who ran into the issue.
The downside of this is that every time we add a new event, which will generate a new URL, I will have to add a new firewall rule. But at least it works.
Thanks so much for your persistent help!
That didn’t work.
When I go to the homepage, there is no ?nocache option.
When I go to any other page I get an error:
==========
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
==========
But, the good news is that if I add &nocache to the event page URL it seems to work.
Thanks.
Ok, I added those additional lines, and now it adds the ?nocache to the homepage URL.
But it fails to load with this error:
This page isn’t working
<mytestsite> redirected you too many times.
ERR_TOO_MANY_REDIRECTS
I added those lines to my .htaccess file but it didn’t add the ?nocache to the URL. I tried both before and after the # END WordPress line.
And my .htaccess file just had some boiler plate text in it. Is that what it should be?
But I’m not sure this would fix the issue. I’m using Plain permalinks for most of my pages, and the ?nocache works there. But for the event pages, the plugin automatically uses Pretty permalinks and that seems to be unable to go to the right page with the ?nocache string in it.
Thanks!
Thanks, @joneiseman, for that pointer. That was useful.
I just had a lengthy call with GoDaddy Support. GoDaddy believes this is an issue caused by one or more of my plugins, or a plugin conflict. They insist their environment is not causing the issue.
They do have some caching, but I have almost no control over it. (I am running in their Managed WordPress product.) I did discover that if I add the ?nocache option to the URL then the page is correctly treated with me being logged in. So that confirms that it’s a caching issue. Now, if I could get the ?nocache option added to the URL on the page with the issue I might have some progress.
Mike
And I am using the Custom Login plugin to control the appearance of the login page, and PHP 8.1.
Do you have any plugins that add caching? — No, I have no caching on my site, unless some plugin is doing it without letting me know.
Is your hosting provider doing any caching server side? — No, I confirmed with my hosting provider, GoDaddy, that they don’t do any caching.
Thanks for your good questions.
Thanks for that suggestion, @joneiseman. I added that WordPress Persistent Login plugin and tried it, but still run into the problem.
It seems that on certain pages my website thinks the user is logged out. The Events registration page, the Homepage, and the Login page seem to be the only ones affected. If I go to a different page it thinks I am logged in. So the Persistent Login plugin doesn’t do anything because the user still is logged in, just not on certain pages.
It’s pretty weird.
Mike
Yes. That worked.
Thanks!
Thanks for that suggestion. It didn’t make any difference.
I added it to Pages -> Event Pages -> Body Classes. Is that the right place to add it?
Forum: Plugins
In reply to: [UpdraftPlus: WP Backup & Migration Plugin] Tables excluded on RestoreThanks, vupdraft, for your reply.
But can you clarify what ‘core tables’ are? Yes, I added mikeh_news_sender_emails, which was not created by or maintained by any plugin. But all the other tables were created by and are maintained by my various plugins. Are these ‘core tables’? The free UpdraftPlus used to backup and restore everything. Is this a recent change?
Thanks for your reply!
Mike
Forum: Plugins
In reply to: [WP Rollback - Rollback Plugins and Themes] rest_no_route errorThanks, Devin. I installed v 2.0.7 and I can confirm the issue is now resolved.
Thanks!
Mike
Forum: Plugins
In reply to: [WP Rollback - Rollback Plugins and Themes] rest_no_route errorThanks, @afizesan, for your brilliant suggestion.
It works, but it causes another problem. But can you explain why this change allows the WP Rollback plugin to work?
The problem this change introduces, however, is that it changes my URL structure. Instead of my pages being style /mysite/?page_id=nn, they are now style /mysite/page-title. I have a lot of external pointers to various pages in my site which will no longer work. And there is a security exposure with this style — for blog posts, the poster’s username is embedded in the URL name, exposing the usernames. This is why I originally switched to the page_id style.
Is there some way for the WP Rollback plugin to continue to work with my page_id URL style, like it used to in v1 of WP Rollback?
Thanks!
Mike
Forum: Plugins
In reply to: [WP Rollback - Rollback Plugins and Themes] rest_no_route errorThanks, Matt, for your detailed response. Are you the Matt of Give?
I contacted GoDaddy and I was told by Joe in Web Development of GoDaddy that the security server for WordPress.com in the USA has been down and has had intermittent problems sine 4-Feb-2024. Upgrades of WP Rollback since then have not been installed properly. The solution is just to wait for this security server issue to be resolved, which should happen on 7-Mar (tomorrow), then upgrade the WP Rollback plugin again.
I will test it again tomorrow and update the ticket.
Thanks,
Mike