wordpress - all pages are blank except the home page - wordpress

My site works fine. I have a development copy that was working fine but now all pages apart from the home page are blank. The files are identical on both servers, apart from the wp-config.php and the .htaccess files. I tried removing the theme and the plugin folders to no avail. I'm lost now! What am I missing?

Well, after hours and hours, changing the permalinks to 'default' and then back to the right setting (in my case Post name) solved my problem.
I hope this helps someone in the future.
I still don't know why I get a strange ABSPATH error message though.

I had the exact same problem working on a website hosted at Bluehost. Everything beyond homepage was white.
The solution was to move the contents of my sub-directory into /public_html.
Despite this article to the contrary (https://my.bluehost.com/hosting/help/347), Bluehost support told me the primary domain cannot be run from a sub-directory.

Related

Wordpress Wp-login.php 500 internal server error

I have run into a bit of a weird problem on a site i created a couple of years ago. No new plugins have been added recently or anything else changed on the site for the last 6 months. Besides from the site admins adding content to the page.
But now, they cant acces the wp-login page. They just get a blank page and a 500 error.
I have looked around the web for some solutions, and have tried the most common ones i come accros:
Tried turning plugins off.
Tried changing the theme to default.
Tried deleting .htcacces file.
Checked if the wp-login.php was updated as to the wordpress codex
Some people have reported that they could acces the login page, by trying to access a specific wp-admin page and then get redirected. This does not work for me either.
None of the solutions above gave any results, so i am now at a bit of a loss.
The frontend of the site is working just fine btw.
Any ideas?
Have you tried increasing the PHP memory limit?
you did not mention it and maybe it could help
Create a file called php.ini
Paste memory=64MB in there.
Upload it into your /wp-admin/ folder using FTP
If this answer helps you. it's a memory issue and you need to figure out what takes your PHP memory limit.

XAMPP Wordpress install - WP-Admin formatting unusable

Putting our company website on localhost for testing, etc. All working OK, apart from WP-Admin: lets me login OK, but the format of the site is unusable - image attached.
Have checked permalinks, etc. which are working OK for rest of website. It is just WP-Admin that I'm having trouble with.
Anyone come across this before?
Thanks in advance.
Darren.
WP-Admin screenshot
Follow this steps
You have a problem in CSS style link, it may cause on your database or maybe on one file which has been hardcoded.
Copied over WP-Admin files from a fresh install and now works.
Thanks for the nudge in the right direction, Babak.

Wordpress goes blank randomly changing plugins folder fixes it

I have a constant issue with my site going blank. Nothing ever shows. To fix it all I have to do is go in with my FTP and rename the plugins folder, refresh the page, and rename the plugins folder back to normal.
How can I have my site up and running at all times? I keep deactivating plugins hoping that it will stop it but after a few hours it goes blank again.
I contacted my host and after having them dig around for an hour they finally found the correct log. The problem was the WP-Touch never stopped 'running' so the mobile sites were fine but it would try to take over the desktop and would conflict with our theme. I have since then disabled the plugin and everything seems normal.

wordpress wp-login.php?redirect_to wrong path

This is a weird one. I googled for hours but seems to me not a single person has this same issue.
I moved my website from http://www.domain1.com/wpfolder to http://www.domain2.com . Everything works fine except I cannot get the "wp-login.php?redirect_to" path to point to the correct url.
WordPress keeps setting it to:
"wp-login.php?redirect_to=http://www.domain2.com/wpfolder/wp-admin&reauth=1"
It should be setting it to:
"wp-login.php?redirect_to=http://www.domain2.com/wp-admin&reauth=1"
The "wpfolder" doesn't exist anymore..
I followed the instructions exactly on how to move a WordPress website, but the darn URL won't change...
Some forum mentioned changing the "site_url" and "home" from "http://www.domain2.com" to "http://domain2.com". Now I can finally get to the admin panel, but I don't get why it needs to be that way?
I cleaned my browser cookies and checked the wp-content folder for cache already. Nada..
Also the rest of the site is functional.
I would appreciate if anyone can help.
I moved the WordPress website from GoDaddy to Bluehost by copying the files and the database and the problem went away. I am not sure why this fixed it, but assuming it has something do with the cache.
If anybody has more information, I would love to read about it.
Thanks
I was facing the same issue, with same redirection to one of the sub-directory in which wordpress was installed.
Resolved this issue, by clearing the cache, if some cache plugin is active.
Or by deleting the cache plugin if any present and is currently not yet active.
As some entries made by cache plugin inside wp-config.php file creates the above mentioned problem.
After removing the cache plugin, it resolves the WP-admin URL issues.

Default Website Page error - While installing wordpress multisites on a subdomain

I have installed wordpress multisites in my directory, everything is working perfectly except the fact that the main page of the sister sites shows "Default Website Page" error and redirects me to "http://geek.thelazy.info/cgi-sys/defaultwebpage.cgi".
The error occurs only when I open geek.thelazy.info and at specific places (not on places far from here), and only when I open the main page. At all other pages say like geek.thelazy.info/devashish site works regardless of anything.
Any clues on how to solve this problem?
I think the solution is to wait for a day or two. This helped me. But, I am not sure what if there is any other workaround at the server side as well because it is not really trivial to put a live site down for 1-2 days.

Resources