Plugin breaks custom functionality after being disabled

  • Resolved Alex

    (@alextechgr)


    2 months, 3 weeks ago

    Hi, I have this extremely bizarre issue with the plugin. I was trying to disable it but when I did noticed people were unable to login via a custom scripted otp plugin I have created, more specifically it seems the part with the cookie is failing wp_set_auth_cookie($user_id, true); after disabling the plugin.

    I tried resetting the .htaccess after deleting the plugin and that didn’t help, any idea of what could cause this issue?

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @alextechgr the plugin does not interfere in any way with the way the users are logging-in. There are no actions and filters associated with the login process. It shouldn’t be since the plugin is a performance one and would not go beyond its purpose.

    Moreover, if you are saying “I tried resetting the .htaccess after deleting the plugin and that didn’t help“, this also suggests that the problem you’re having has nothing to do with the plugin because it doesn’t alter in any way the .htaccess file, and if it’s deactivated, it shouldn’t mess at all the website, since none of its code is triggered.

    Thread Starter Alex

    (@alextechgr)

    Hello Gabe, thanks for the info, issue was with the custom function indeed, however, the plugin did influence the buffer output (or something related) which ended up breaking the functionality when the plugin got disabled.

    Either way I recreated the function under a different logic and it is working fine now,
    Thanks for your time.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.