I migrated the company's website on a new hosting server. Since then, I cannot access my Wordpress dashboard when I'm logged in.
When connected, I see my website and the classic Wordpress top bar. But when I click on the button with the name of my website (usually that sends me to the dashboard) it just sends me back to the home page.
I add that the top bar isn't really like the classic top bar since it doesn't contain any option.
Here's a screenshot.
The top of my website when logged with the top bar of the admin wordpress
Clicking "Bonjour Signature_Beta" doesn't do anything. I can only log out.
Going to the /wp-admin page gives me an error saying "Sorry, you do not have authorization to reach this page". Except, I'm supposed to have authorization since my profile has a wp_content value of a:1:{s:13:"administrator";b:1;} and wp_user_level of 10.
I have tried multiple things I found online that didn't come to fruition sadly :
Renaming plugin's folder (nothing changes except page breaking because they're made with Elementor)
Renaming theme's and child theme's folder (page goes blank, top bar still there though)
Replaced .htaccess file (nothing)
Checking my account didn't lose admin privilege through phpmyadmin (it didn't, it's at level 10 + it has the weird administrator code
Added a new admin account through function.php (can log in with it, still can't access dashboard)
Increased memory limit
Repair database tables
Kind of desperate and frustrated about it.
Thank you in advance for the help :)
Ok with a fresh pair of eyes, I found out what was the problem. Tables prefix! I followed what was described here : After moving Wordpress, login works, but no admin access anymore
For the record, I never found it when googling or searching my answer here before posting. When posting my question I review the post stackoverflow suggested and it wasn't there either. But now it's suggested next to my post, so... great!
Related
I have a site that I made updates to, however none of the changes show up when I log out. I can see all the changes on the pages when I am logged in, but I even went as far as to remove a link from the top menu and I still see the link when I log out.
It's almost like I'm seeing a different instance of WordPress when logged in, but I have no idea how that would happen. There's only one database so that can't be the case right?
The URL is https://CXForward.com
I tried removing the "Our Services" link from the top menu, and everything looks fine while I'm logged in, but as soon as I hit log out or view it from a different browser, the link is still there. I'm hosted on SiteGround. Has anybody experienced anything like this?
EDIT: I've found that I can upload a file that is visible in both the browser I'm logged in with as well as another browser that is not logged into the site: https://cxforward.com/wp-content/uploads/testing.txt
So it would appear that I am pointed to the same code base at the very least.
I figured it out. There's a SiteGround Optimizer plugin that apparently does caching for the site. It's bizarre. I deactivated the plugin, then reactivated it and all my changes appeared on the site when logged out. So weird.
I have somewhat recently become the admin for a friend's website. When I came on he had about 80 different plugins and I have recently gotten rid of a lot of the useless one. The website was working perfectly fine afterwards. Then I found out (a bit before the WordPress 5.5 update) that the register page wasn't working properly. I went ahead and cleared a lot more things and have been troubleshooting it nearly everyday. The website is now at the point where you can go to the login page, but attempting to go to the register page will redirect the user back to the login page. If I visit as an admin I can access the page, but the form displays the text that I am already registered (correctly, but not useful).
The plugins that are currently enabled related to logins are: Ultimate Member, Gamipress, Jetpack, Loginizer, and various Gamipress and Ultimate member integration plugins. If you want to see the site for yourself you can find it here:
https://www.plagueleague.com/
I cannot comment for more information, so I use the answers... In admin, then "Settings", then "General", does the box "Membership: Anyone can register" is checked? If the answer is no, I think that redirects to the login page.
Drupal 7.19
Acquia hosting
using Yottaa for optimization and monitoring
Problem: when trying to log in from home, we're experiencing something odd: we keep getting "logged out" ONLY on the front page. When you click anywhere inside the site, we get the admin toolbar and contextual links back. But we can't update the front page at all because it acts like it's logged out only for the front page.
This only happens when we're at home working on the site. This does not happen when we're in the work office.
Anyone experienced this? Don't know at what level is this occurring in...drupal, yottaa?
Found out the issue. It was a specific caching for the homepage on Yottaa's CDN. Once I turned this off, I was able to edit the home page again.
Note: They said that turning it off is not recommended. Instead, they recommend to flush the cache. Either way, found out what was causing the issue.
I am trying to set up a new custom post type and create a page (based off the custom post type archive template) and keep it private until it's ready to be published. I created a page and made it private, but it was visible to everyone (although not in the dropdown like it normally would be, just from entering the permalink URL). So I deleted that from the database (in phpMyAdmin) and tried again just leaving the page a draft. The permalink URL still shows the page template for the custom post type archive. I deleted the draft in phpMyAdmin and still the URL shows the page template (should be giving a 404). I tried this in a different browser where it had never been opened and it also gives the page template.
Does anyone have any idea why this is happening? Why isn't it working to privately publish and why aren't the deleted pages going away?
You propably only deleted the content of your page, but there are more relations to the page. See the database diagram on wordpress how posts are connected to other tables in the database as well. You'll have to delete every record pointing to that post!
I really recommend you not to play around in the database of wordpress, there's a reason why WP gives you the opportunity to administer everything in their admin panel!
To leave a page/post invisible to others, just don't publish it! As a draft, no one can access it unless he/she has access to your admin panel and the required rights to see drafts!
As soon as you publish it - it's published. You can also just use the preview view to see how it would look like! Why your private page was visible to everyone is another question, maybe you made some mistakes with your DB...hard to reckon without any further information. Try to set it up as a normal post/page and publish it privately, log out and see what happens!
I recently upgraded to WPMU 2.8.6 and ever since, my users can't log in on their individual blogs, but they can log in from the main page.
My site is at blogs.mtwp.net (we're a school district).
So if a user goes to blogs.mtwp.net/BLOGNAME/wp-login.php, their password is rejected. If they go to blogs.mtwp.net/wp-login.php, they can log in and get to the dashboard from there.
But it's not all users. Site admins can get in just fine.
We're using wpDirAuth 1.4 if that makes a difference.
Honestly, I'm stumped. Any help would be very much appreciated. Thanks!
you would seem to have enabled the WPdirauth plugin at the top level blog but not on others. Only your top level blog will have the necessary information to connect to your directory.
Site admins are not typically part of your internal directory - they're a Wordpress user which means they can still log-in ok without needing to connect to Active Directory or whatever you're using.
Enable WPdirauth on all blogs that you need users to login to.
Try reviewing your wp-config file. You should see something like this:
define('SUBDOMAIN_INSTALL', true);
Depending on how you've configured Wordpress, this must be enabled to log in to the dashboard of secondary sites.