[Resolved] Updating to 3.4 breaks site with WordPress in its own directory
I have half a dozen sites that I run, all small scale. Moving to the new v3.4 release has gone smoothly so far with all but one site. It has the WordPress main directory not in the web root but in
~/wordpress/. Trying to access that site at all gives me the error
Fatal error: Call to undefined function wp() in /home/emlweb/public_html/wordpress/wp-blog-header.php on line 14
(The other sites all have WordPress installed in
The problematic site is running PHP 5.2.9, MySQL 5.0.95-community, Apache 2.0.63. Before I start from scratch and restore from backups, any ideas on what is wrong and what to do?
- The topic ‘[Resolved] Updating to 3.4 breaks site with WordPress in its own directory’ is closed to new replies.