I have several installations of wordpress on my vps… You need to look in your error logs and find out if it is a permissions problem or something else. Everything will be in the logs on a VPS, unlike cheaper shared hosting. Google “error logs” for the OS of your VPS.
Your SQL command is invalid. The error says: WordPress database error: [Incorrect table definition; there can be only one auto column and it must be defined as a key] CREATE TABLE to_issues ( id int(11) NOT NULL AUTO_INCREMENT, name varchar(125) NOT NULL ) Try: $sql =”CREATE TABLE {$wpdb->prefix}to_issues ( id int(11) unsigned NOT NULL auto_increment, … Read more
Make sure there is an index.php in the directory, and make that file the index file. Example for .htaccess: DirectoryIndex index.php
Your plugin is causing some errors, but not fatal ones, so plugin works, but as the error messages says, it can cause some problems, i.e. the feed that can output the plugin error so not valid xml content, or when somewhere in the code there is a redirect once “headers already sent” it fail. If … Read more
I run a multisite setup for developing, it saves time and you can just delete the sub-site when you’re done developing. I also have a few different .xml files of common content types that I tend to use a lot (Portfolio items, Standard pages / posts, Testimonials, etc.) and I just import each one as … Read more
Yes you can have more than one database, this type of set-up is for large traffic heavy sites and you would want to use something like http://wordpress.org/plugins/hyperdb/ . This is outside the scope of the vast majority of WordPress sites. You can manage a multitude of blogs from 1 db if you want using http://codex.wordpress.org/Create_A_Network. … Read more
make a backup of your SQL database for the site and try running these queries manually on the database through php myadmin. change the URLs to match your site http://example.com/blog As always, be careful when running queries on the database UPDATE wp_options SET option_value = replace(option_value, ‘http://www.oldurl’, ‘http://www.newurl’) WHERE option_name=”home” OR option_name=”siteurl”; UPDATE wp_posts SET … Read more
If I understand you correctly, this is because you have a index.html (from your static site) and a index.php (from WordPress). So if you rename your index.html to something like: oldindex.html, the correct index.php will be shown (the WordPress index.php). Alternatively, you could remove the index.html.
Hopefully I can be of a little help. Taking a look at the InstandWP website, it appears to be an install version of WordPress that installs into a directory, and then contains all settings etc for the site to run in a local environment. I am not sure on the file structure of InstantWP, so … Read more
Generally when moving a WordPress site I copy the files to the new path then update the URL in the Dashboad. After logging into the ‘new’ install and making sure everything looks good I remove the old directory.