daninor
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminThanks for your reply. I’m still stuck with this and the site is effectively dead (nothing done over the past two months). Obviously, I’m sincerely hoping some kind soul will help me get this solved. So what is the “recommended way” you’re referring to? As you can see further up the thread, I did delete all active plugins straight from the database without getting closer to solving this. I saw the effect of the missing plugins, so I know they had been disabled.
How/where do I switch to default theme? Which files should I check for different versions? If you’re talking about wordpress internal stuff, then everything is the same version, I don’t mess around there.
Same goes for wp-config.php, I don’t touch that and it’s been the same for a few years and working fine.
Thanks again
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminMy other thread is about a plugin that prevented me and all other users from seeing the home page.
This problem is regarding /wp-admin area and me not being able to get into the admin part at all, even with all plugins disabled. So very much the opposite situation.
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminI just deleted wp-admin and wp-includes and upgraded to 2.8 and it still won’t let me in the admin part. Obviously, I’ve tested on multiple browsers, computers and networks, so it’s not the computer/browser issue.
Is there really no one with any clue out there?
Forum: Fixing WordPress
In reply to: No longer access to /wp-admin.
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminanyone?
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminbump, please help.
Forum: Fixing WordPress
In reply to: No longer access to /wp-adminDeleting .htaccess (I actually renamed it to htaccess.bak, but that should be the same) did not make any difference.
Here is the entire value of the wp_option field showing all the plugins in use. I deleted the whole thing in an attempt to get in, but no cigar.
a:13:{i:0;s:28:”RoleManager/role-manager.php”;i:1;s:32:”authenticate/wp-authenticate.php”;i:2;s:39:”bad-behavior/bad-behavior-wordpress.php”;i:3;s:17:”dashboardopts.php”;i:4;s:23:”flv-embed/flv-embed.php”;i:5;s:17:”postie/postie.php”;i:6;s:31:”register-plus/register-plus.php”;i:7;s:19:”wp-ExtremeVideo.php”;i:8;s:21:”wp-cache/wp-cache.php”;i:9;s:34:”wp-contact-form/wp-contactform.php”;i:10;s:27:”wp-homepage/wp-homepage.php”;i:11;s:31:”wp-lightboxJS/wp-lightboxJS.php”;i:12;s:13:”wpg2/wpg2.php”;}
I guess one way to fix it might be to create a new database, run install from scratch and move things manually table by table from the current database, but that sounds like something I’d like to avoid.
Forum: Fixing WordPress
In reply to: Login impossible after 2.7 upgradeThanks, dd32! Problem solved.
Forum: Fixing WordPress
In reply to: Login impossible after 2.7 upgrade@dd32: plugin is supposed to ensure that only registered and logged in users can view the content on the site. It has nothing to do with the admin console. If there are any other ways/plugins that can do this on 2.7 I would gladly try that, otherwise can you please tell me what any of the code snippets above should do differently to make this work with the new cookies?
Thanks
Forum: Fixing WordPress
In reply to: Login impossible after 2.7 upgradeFollow-up 2:
I just tested with another plugin called “Authenticate” and this one also has the same effect. Both plugins are not specified to support versions over 2.5, but since I can’t seem to find any 2.7 compatible plugin for this, I would really like to find out what the cause of this is.
“Authenticate” has a slightly different code than the previous one
//If the current page isn't 'wp-login.php' or 'wp-register.php' redirect if ((strpos($_SERVER['PHP_SELF'], 'wp-login.php') === false) && (strpos($_SERVER['PHP_SELF'], 'wp-register.php') === false)) { auth_redirect(); }Please, help!
Forum: Fixing WordPress
In reply to: Login impossible after 2.7 upgradeFollow-up:
I believe this to be related to a plugin called Angsuman’s Authenticated WordPress Plugin, which should ensure that only logged in users are allowed in. Even though the code looks simple, I have no way of knowing exactly what in it is causing this on the new version.
The whole code is basically this
function ac_auth_redirect() { // Checks if a user is logged in, if not redirects them to the login page if ( (!empty($_COOKIE[USER_COOKIE]) && !wp_login($_COOKIE[USER_COOKIE], $_COOKIE[PASS_COOKIE], true)) || (empty($_COOKIE[USER_COOKIE])) ) { nocache_headers(); header("HTTP/1.1 302 Moved Temporarily"); header('Location: ' . get_settings('siteurl') . '/wp-login.php?redirect_to=' . urlencode($_SERVER['REQUEST_URI'])); header("Status: 302 Moved Temporarily"); exit(); } }