HELP! I am locked out of my dashboard!

My site: http://www.rmsatemp.com/

Last night, I was moving back and forth between admin and test user accounts because I was testing 2 new plugins that I had installed. One was user role editor pro and the other was a javascript editor plugin referred to in this link: https://premium.wpmudev.org/forums/topic/changing-name-of-events-filter-on-buddypress-site-wide-activity-widget#post-1188110

Everything was working well. Then this morning, first thing, I logged on as a test user to test user submitted info from the front end. It worked well. So I logged out and now I can not log in as wp-admin.

I get this message: The http://www.rmsatemp.com page isn’t working
http://www.rmsatemp.com is currently unable to handle this request.
HTTP ERROR 500

So, then I went to the hosting account, file manager and deleted the 2 plugins and also ultimate branding, as this was a plugin I had added a couple days ago. Then I cleared my browser and tried again.

I was able to get the wp-admin page 1 time but when I filled out form and hit send it went right back to the error page.

So then I tried to sign on as the same test user that had worked this morning and I get this message:

Warning! Simple Membership plugin cannot process this login request to prevent you from getting logged out of WP Admin accidentally. You are logged into the site as an ADMIN user in this browser. First, logout from WP Admin then you will be able to log in as a member. Alternatively, you can use a different browser (where you are not logged-in as ADMIN) to test the membership login. Your normal visitors or members will never see this message. This message is ONLY for ADMIN user.

Please help! Thanks in advance. Linda

  • iempoweru

    Ok, I restored the backup from last night and was able to get into the dashboard. Could you still take a look to see if you can identify why this might have happened? The 2 plugins I deleted and all of the settings are restored. Because one of those plugins: https://wordpress.org/plugins/tc-custom-javascript/ is experimental, could this be causing any problems? Access has been granted. Thanks in advance. Linda

  • Dimitris

    Hey there iempoweru,

    hope you're doing good and I'm glad that you sorted out his lockout event. :slight_smile:

    Warning! Simple Membership plugin cannot process this login request to prevent you from getting logged out of WP Admin accidentally. You are logged into the site as an ADMIN user in this browser. First, logout from WP Admin then you will be able to log in as a member. Alternatively, you can use a different browser (where you are not logged-in as ADMIN) to test the membership login. Your normal visitors or members will never see this message. This message is ONLY for ADMIN user.

    It seems that Simple Membership had some kind of issue with you changing users. In cases like these, you may have to clear all of your browser's cache/sessions/cookies. For that you can advise this handy website: http://www.refreshyourcache.com/en/home/

    Because one of those plugins: https://wordpress.org/plugins/tc-custom-javascript/ is experimental, could this be causing any problems?

    I also inspected your JS snippet which seems pretty simple and valid. If you want to test another alternative for "TC Custom Javascript" (I haven't used that but I doubt that it may cause any issues), this is my favourite plugin https://wordpress.org/plugins/custom-css-js/

    As for the "HTTP ERROR 500". If this is still reproducible in your website, you can enable WP_DEBUG in order to get any related information. Simply access your server through FTP, edit the wp-config.php file, find a line like
    define('WP_DEBUG', false);
    and replace it with the following (if the above line doesn’t exist, simply insert next snippet just above the /* That's all, stop editing! Happy blogging. */ comment)

    // Enable WP_DEBUG mode
    define('WP_DEBUG', true);
    // Enable Debug logging to the /wp-content/debug.log file
    define('WP_DEBUG_LOG', true);
    // Disable display of errors and warnings
    define('WP_DEBUG_DISPLAY', false);
    @ini_set('display_errors', 0);

    Then go ahead and try to replicate the error. By doing so, a /wp-content/debug.log file should be created. Simply download it, rename it to debug.txt and attach it here in your next reply.

    Warm regards,
    Dimitris

Thank NAME, for their help.

Let NAME know exactly why they deserved these points.

Gift a custom amount of points.