|
Can I get a few suggestions for the white screen of death?code:
All I see in my Apache access log is: code:
My php install seems to be okay, I can run phpMyAdmin just fine, as well a base Wordpress install, and the wp-admin/install.php page on this site gives me the "You appear to have already installed WordPress. To reinstall please clear your old database tables first." message. I also made a little dbtest.php with the same user/pass/dbname as in wp-config and it connects successfully. I've moved a handful of Wordpress/Joomla sites in the past, I'm working from a zip file that a advertising company sent over that went out of business. I imported the MySQL database fine, moved the files over, re-set the permissions. php version 5.5.9 (it was running on 5.2.17 on the old server) Wordpress 4.1.7 Apache 2.4.7 mysqld 5.5.44 ubuntu 14.04 server It was running on GoDaddy before, I'm not sure if there's anything that needs to be changed between a shared environment and running on a Linux VM. I just can't get this fucker to spit out any useful information.
|
# ¿ Oct 15, 2015 14:16 |
|
|
# ¿ Apr 27, 2024 08:39 |
|
fuf posted:So a fresh WP install works fine? Fresh install works fine but if change the wp-config.php to use the imported database, I get the white screen. Should I leave the wp-config.php as is and import the old database into the one I set WP up with when I do the new install? As far as the URL changing, I did HOSTS file entries on my workstation and the VM to point the IP address of the VPS to xyz.com and https://www.xyz.com should that be enough? The database entries in the options table for siteurl and home both say 'xyz.com' Blinkz0rz posted:Try going to $url/index.php. If that works then you have a problem with your .htaccess file. The archived site uses this for a .htaccess file: code:
code:
Edit: just puke me out a drat error message! Bob Morales fucked around with this message at 16:48 on Oct 15, 2015 |
# ¿ Oct 15, 2015 16:21 |
|
fuf posted:Hmmm you could try but I guess whatever problem in the DB which is causing the white screen will just be copied over too? Blinkz0rz posted:Your rewrites are hosed. There's no reason whatsoever your site should be giving a permanent redirect. Double check your Apache/Nginx settings. I had the old .htaccess in there still which was causing that (drat hidden files), I just removed it.
|
# ¿ Oct 15, 2015 18:33 |
|
Update on where I'm currently at: I deleted what I had done so far and started over. This time I downloaded Wordpress 4.1.7 which is what the site was running on. Base install works. Changed the database info around to the database that I imported. As soon as I do that, the white screen comes back. However, this time I was able to login through /wp-admin. I had to change the password of the admin user with MySQL and I am able to get into the dashboard. I can see all the old articles (I mean posts, I'm warped from dealing with Joomla!11) and such. There are 2 plugins but they are both inactive. Now what? Still no loving errors. Edit: Oh boy I activated a theme (since the one it was showing as active was blank) and it works! Now I think I just need to copy over the theme from the old site. Theme is busted somehow. Activating it breaks the site instantly. Live preview doesn't work either. I should be good from here. "PHP Fatal error: Call-time pass-by-reference has been removed in ... on line 30" So either hack the theme up or install PHP 5.3... Fixed that one error and the theme mostly works. Thanks for the help, Goons. Bob Morales fucked around with this message at 19:35 on Oct 15, 2015 |
# ¿ Oct 15, 2015 18:35 |
|
thegasman2000 posted:I have a html template i need to hack up and make into a wordpress theme... Its pretty simple, and as it's for ebay self contained. http://prestoparts.co.uk/ebay/pp/BestTemplate/index.html someone in India or Muldova on rentacoder/freelancer would probably do it for $15
|
# ¿ Nov 19, 2015 18:54 |
|
IAmKale posted:I'm trying to find a simple way to send e-mails from our Wordpress server if the MySQL database goes down.
|
# ¿ Apr 22, 2016 19:32 |
|
edit: poo poo! wrong thread
Bob Morales fucked around with this message at 19:02 on Apr 25, 2016 |
# ¿ Apr 25, 2016 18:36 |
|
fuf posted:Using the "Duplicator" plugin (https://en-gb.wordpress.org/plugins/duplicator/): It's pretty easy to do this and your webhost might even help you out with it if you're a new customer. The best part is you can use a HOSTS file entry to test your new site before you ever change your DNS settings on your domain to point to your new hosting company https://secure.revion.com/knowledgebase/29/How-to-use-your-HOSTS-file-to-test-your-webserver-before-DNS-propagation-is-finished.html
|
# ¿ Oct 22, 2016 18:06 |
|
|
# ¿ Apr 27, 2024 08:39 |
|
Has anyone had luck accessing internal WordPress sites using an SSL proxy that runs on a firewall? In this case it's a Fortinet, you log in, and you can click on links to internal resources. Instead of the url being something like http://intranet01 it becomes http://1.2.3.4:9560/proxy/asfd/intranet01 I think what's happening is WordPress is trying to re-write the URL (since it's expecting it to be http://intranet01), but of course it keeps getting changed by the proxy so this happens 20 times or whatever and then the browser gives an error about too many redirects. If I use http://intranet01/index.php for my link, the site will mostly work. Some stuff doesn't load, though. Other internal resources seem to work fine, but they aren't re-writing the URL like WordPress does, and the challenge is trying to fix it without breaking it for regular internal users. I have the standard .htaccess file, I'm about to fall asleep or I'd try hacking away on it. Not sure what the 'goal' would be though to get WP to leave it alone or if I'm barking up the wrong tree.
|
# ¿ Apr 20, 2020 21:53 |