Your first issue is the fact that you’re using query_posts. That function isn’t meant for creating new queries to the database; instead, it’s used to modify the existing global query. Read up here and here for more information on what you can use instead. Second, there is just some strange code in your template that, … Read more
From my view, I avoid using the wp editor at all. It doesn’t offer all the good things a IDE can provide. If you have a local server running, you probably can access it. For example, in linux its usally on /var/www/localhost/htdocs/ but it varies a lot from distro to distro. You can also use … Read more
Yes, while convenient, let’s rule out the variable of using the $_SERVER[‘HTTP_HOST’] trick and put in the absolute URLs. Here are some handy snippets I use when moving a site (you may want to use these to make sure everything is the same on your install): UPDATE wp_posts SET guid = replace(guid, ‘http://www.olddomain.com’,’http://www.newdomain.com’); UPDATE wp_posts … Read more
99.99% chance that you configure wordpress with wrong database details. make sure you are using correct database details in wp-config.php file /** The name of the database for WordPress */ define(‘DB_NAME’, ‘database_name_here’); /** MySQL database username */ define(‘DB_USER’, ‘username_here’); /** MySQL database password */ define(‘DB_PASSWORD’, ‘password_here’); /** MySQL hostname */ define(‘DB_HOST’, ‘localhost’); some possibilities are … Read more
The WordPress-Config-Bootstrap is setting DEBUG to true on a local installation. If you try to define DEBUG again later you should get another error. The solution is not to use the non-existent property $id. Notices should be fixed not suppressed.
Since you want to test out your existing(local) site on the server; you have done the right thing as far as I can see on pastebin except for 1 thing On step 10 – you replaced all occurances of “localhost” with your servername. Instead you should have replaced it with servername/directoryName. If you still have … Read more
some time it’s most likely the permalink structure is missing or something went wrong after migration from localhost to live server, the solution is reflush permalink rules to avoid 404 errors.
It sounds like you have not properly updated the “WordPress Address” and “Site Address” at wp-admin -> Settings -> General, or you have defined WP_SITEURL and WP_HOME in wp-config.php and did not adjust the value when the site was moved. I can’t comment on whether the .htaccess file is correct, though I can say that … Read more
This happens when WordPress cannot directly (via php) create files inside the wp-content directory. WordPress asks for FTP credentials to try and upload “manually” the files, you should provide the hostname of the ftp server (example: ftp.yourdomain.com), username and password. Of course you have to have an FTP server set up, which is usually straightforward … Read more
Probably your localhost siteurl option it’s not set up right. Try to add this on your wp-config.php file: define(‘WP_HOME’,’http://localhost/stepladder’); define(‘WP_SITEURL’,’http://localhost/stepladder’); If it works, then it proves that your siteurl option (on your options table) it’s not correct. hope that it helps, Cheers