Problems with my backend after update

Resolved John Gerritse
(@sorpresashop)

1 month, 2 weeks ago

After upgrading to version 5.4.03 on one of my 2 webshops, I have serious issues getting into my backend. Weird thing is that my other webshop, which has a few different plugins installed, doesn’t have this issue.

I can’t login through my regular login, I end up back on my login page without being logged in. When I use my safe login page, I get into my backend, but whenever I go to any page there, I get thrown back to my homepage. I can’t edit anything on my homepage either. Weird thing is that, once in my backend, I can go to my plugins page and disable the HMWG plugin. I disabled it for 5 minutes as a test. But if I do, my login session is expired and when I try to log back in, I get the error that my password is incorrect.

When the 5 minutes are up, I am able to login through my safe login page again. I suspect some weird interaction with another plugin, because one webshop has this issue and the other doesn’t, while they both have the HMWG plugin version 5.4.03, although I disabled the plugin on the webshop that was still working properly as quickly as I could.

Viewing 3 replies - 1 through 3 (of 3 total)

Thread Starter John Gerritse
(@sorpresashop)

1 month, 2 weeks ago

I did a little more testing, but when reverting my website to a version just before the upgrade, when still using version 5.4.02, I have the same issue. I’ll run a copy of my webshop in a dev environment to try and figure out what is causing the issue. If I learn anything useful, I’ll post it here.
Plugin Author John Darrel
(@johndarrel)

1 month, 2 weeks ago
Hi John,

Thank you for the details. In the last update we worked on the custom path handle when the rewrite rules are not ser correctly in the config file. I don’t know if it’s your case.

Some solutions:
1. If you are using a cache plugin and custom admin path, include the custom admin in the URL exception of the cache plugin.
2. Switch on the WP Ghost > Advanced > Compatibility > Clean Login option to avoid any redirect before applying the cookies on the custom admin path.
3. If the above solutions are not try with the default wp-admin path as it seems to be a cookie issue on the custom admin path (probably a plugin conflict).
4. If you are using a Nginx server, restart the Nginx after saving the settings in WP Ghost to apply the rewrite rules.
These are the main reasons the custom login is not working. It you find anything that can help us identify the issue please let us know.

Best regards,
John
Thread Starter John Gerritse
(@sorpresashop)

1 month, 2 weeks ago

I’ve been tinkering a bit with it, but haven’t resolved it yet. Clean login is enabled. I don’t use a cache plugin.

The only place where logging in doesn’t work, but used to, is the page I created for customer logins using the [woocommerce_my_account] shortcode. Logging in through the default wordpress login page does work.

That at least narrows it down.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Tags