• Resolved spiwee

    (@spiwee)


    Hi,

    I’m reposting this topic, which already exists in several places on the forum but was marked as resolved even though the issue still persists.
    I’ve been using the plugin WPS Hide Login without any problem for a long time, but this month, on two sites, after setting the new login URL I get a 404 error and I had to deactivate the plugin
    My permalinks are set to “Post title” and I don’t want to change them.
    On sites I configured some time ago, it still works and they have the same other plugins and theme installed.
    Your plugin used to work perfectly; it’s a shame if I can’t use it anymore.

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Lea WPServeur

    (@leacomm)

    Hi,
    Thanks for using WPS Hide Login !
    The issues were closed because people found that it was a conflict with other plugins and not caused by ours.
    Have you tried disabling the plugins one by one? Changing the theme?
    Could you please provide me with the exact slug where you get the 404?

    Thread Starter spiwee

    (@spiwee)

    Hi,

    If there are conflicts with other plugins, could you tell me which ones?
    I’m certainly not going to deactivate all the plugins and the theme. I work with Elementor, and disabling this plugin or others would break a site.
    I can share some information with you — I have a test site — if you give me an email address or a way to send it anonymously.

    Thanks

    Hi @spiwee and All

    I had the exact same issues a few days ago but persisted with the investigation by un-installing WPS-Hide-Login and re-installing. The problem of login going to 404 page was only at one of my testing sites.

    I was finally able to get logged in by prepending my LoginWord with a questionmark.

    Thus for site mysiteabc.xyz and a login word of “partytime”, I was able to login using
    https://mysiteabc.xyz/?partytime

    Note the ? mark before login name

    Interestingly, on the site where this problem occurs, where I go to set the new login target in Settings, it shows the Login URL with the entry field as:-
    https://mysiteabc.xyz/? [then the input field where I enter partytime]

    On other sites where WPS Hide Login has never given a problem, that Settings Entryfield area shows as…
    https://mysiteabc.xyz/ [then input field where I enter partytime] then it shows a forwardslash /

    Both site are WP 6.8.3, both sites use WPS HideLogin v19.17.2

    The problem site has one extra Plugin, that is “Add from server”

    I hope this gets you, and anyone else working again. WPS HideLogin has been solid for me.

    Plugin Support Lea WPServeur

    (@leacomm)

    Hi,
    If you don’t want to deactivate plugins and themes one by one on your live site, you should do this on a test site instead, as this is the first step when troubleshooting issues like this.
    Also, check if you have any caching system in place (whether a caching plugin or server-side cache) and temporarily disable it.
    Best regards.

    geoffdaw

    (@geoffdaw)

    Hi,

    I came across this thread when one of my users reporting that the link I had sent him to sign on was returning a 404 error. The link worked fine for me with a variety of browsers. When I looked in the access log I found:

    his.ip.address GET https://website.co.uk/logonstring/ 302
    his.ip.address GET https://website.co.uk/wp-admin/ 404

    my.ip.address GET https://website.co.uk/logonstring/ 200

    So same url but different outcome. Could it be cookies?

    I told him to try what @midlander suggested and he said it worked. From the access log:

    his.ip.address GET https://website.co.uk/?logonstring 200

    I tried the same thing and just got the Home page.

    So nothing to do with plugins or caching (I don’t use it). Possibly browser difference, he was using the Samsung browser and I used a variety of Android and Windows browsers, but unlikely. Cookies?

    Hope this helps.

    Plugin Support Lea WPServeur

    (@leacomm)

    Hi,
    The issue you’re experiencing is likely caused by your browser cache or server/CDN caching. This is not a plugin bug. Please make sure to fully clear both your browser cache and any server/CDN cache.

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

You must be logged in to reply to this topic.