Since (from what I understand) the issue only occurs to imported posts I suggest you try the plugin Search and Replace. It’s a quick and easy way to solve this problem. WP stores the uploaded images in your database. Imported images probably direct to the old root, so you should change that to the new … Read more
I am working on redesigning a fairly high profile blog. I suggested the best way to do that, rather than mockups, is to just upload their wordpress export to a new WP install on domain. I periodically (twice a year or so) pull the database from our primary site and import into a dev site. … Read more
Generally speaking, you want to load your general stylesheet (style.css) first and follow it with your more specific stylesheet(s) (style-premium.css). However, the actual details of how CSS cascades are more complex than that and your specific stylesheet can still be overridden by the general stylesheet: if the !important declaration is used based on the specificity … Read more
I’ve created a patch that will work around this issue. This patch is for WordPress 3.6.1. It is a hack, not something that should be taken very seriously except that it points out where the problem may be. I don’t know PHP, but was able to trace it back to this point before giving up. … Read more
Export the posts via the exporter at wp_admin->Tools->Export and bundle the resulting file. Provide the end user with instructions for importing them– basically, install the WordPress importer and then visit wp_admin->Tools->Import. Please do not try to force installation of your posts automatically as it will insert data into the user’s database. That just isn’t friendly.
It’s not difficult. You need to transfer files to the new server. Create a blank database and keep it’s name, user_name (this user must have all privileges of this newly created database) and password. Edit config.php file on new server with the these new details. Read: WordPress Codex for transferring site
If you can guarantee the “uniqueness” of each page’s title, I would first run the entire import, and then loop over the newly inserted pages & set their parents by cross referencing the CSV.
Its not that $wpdb->query does not need $wpdb->prepare(), it’s because of not using $wpdb->prepare() in a correct manner. In your case $wpdb->prepare() never received any values which it must. Please refer to the Codex for details about using $wpdb->prepare().
From what I can see, you are inserting data in table wp_commentmeta. However the column meta_id has a Primary Key restriction. You can see the table definition at http://codex.wordpress.org/Database_Description#Table:_wp_commentmeta As meta_id has a Primary Key restriction, this column may only hold unique values. The insert statements you have posted show only unique values for meta_id, … Read more
Sounds like a sound approach to me! Not enough rep to comment so I’m posting an answer… Only advice I’d have is to 1. Make sure character encodings are correct so you don’t end up with a bunch of “æÔ ‘s 2. Make database backups 🙂 As to ACF, I think it’s pretty much the … Read more