It fails because there is already a theme with that name on the server. So the obvious solution is to remove the theme before you upload the new version. If you’re wanting to use an update mechanism like the theme repo, but on a custom theme, there are udpater classes you can add, such as … Read more
The featured image itself– the actual .jpg, or .png, most likely– is saved to wp-content/uploads with primary image data saved to $wpdb->posts as an attachment post type. Additional relevant data for the image is saved in $wpdb->postmeta. What makes an image “featured” or not is an entry in $wpdb->postmeta under the key _thumbnail_id and a … Read more
I had to also change the owner of the root web directory. chown apache:apache . # or chown apache:apache /var/www/html Edit by Otto: Chloe, as you asked for more information than I could reasonably put into a comment, I’m appending this on to your answer. I hope that is okay. If not, feel free to … Read more
you are correct, that is for the admin bar. add this code to functions.php to disable the admin bar if you wish <?php /* Disable the Admin Bar. */ remove_action( ‘init’, ‘wp_admin_bar_init’ ); ?> if you want to use it then check your source for <div id=”wpadminbar”> <div class=”quicklinks”> If so, then the output is … Read more
sounds like you need to think about a new host… do I dare ask where you’re hosted now? But yes that’s a permission issue.
I know that when i disable the WordPress updates its mainly to allow me to first test the updates and then go and update in my clients sites instead of them just clicking links around and usually messing things up.
If you’re already using the SVN method, then keep using it. Trying to auto-upgrade an SVN site will probably fail due to all the extra .svn directories and such. Auto-upgrade doesn’t do anything special or different. It’s just replacing the WordPress files with the new ones. SVN will do the same thing.
Your .htaccess is not readable (like the error noticed). So make your .htaccess readable using permission 644. Source Now check again, perhaps now your stylesheet will be loaded? If not, check if the stylesheet file is readable. May this not be the cause, check the owner of the files.
In this situation, I’d recommend the following: Dump your production database into your test database Install WP 3 and point it at your test DB Run the database upgrade Turn users loose on the test instance We used a similar process on a much larger installation, and it worked fairly well. Having the second instance … Read more
Got it back, the $table_prefix line was wrong in my wp-config.php. Fiu.