You have to search the wp_options database table for option_name‘s that contains widget. That search results in: Using the values of your backups, you’ll then proceed to restore the option_value of the missing widgets. And also the value of the option of sidebars_widgets. Goes without saying that backing up before doing this modifications is essential.
Since you guys haven’t mentioned it yet then i’ll have to BackWPup a free site and database backup plugin packed with features and easy to configure Database Backup WordPress XML Export Optimize Database Check\Repair Database File Backup Backups in zip,tar,tar.gz,tar.bz2 format Store backup to Folder Store backup to FTP Server Store backup to Amazon S3 … Read more
If it is an older version of WP, you need to find out what version of WP generated the database, as WP upgrades the DB most times the files are upgraded and you should incrementally upgrade to also upgrade the database. Look in the wp_options table for option 711 and see what the version is; … Read more
BackWPup has a lot of flexibility in timing, what to backup (down to the DB table level), and it can store to DropBox which would put it on your computer.
I’ve seen a bunch of ways of doing this, but here are a couple: Use a plugin, like BackupBuddy (paid): http://pluginbuddy.com/purchase/backupbuddy/ Export your whole DB using phpMyAdmin and run a search-and-replace tool that properly deals with the serialized data, e.g. https://interconnectit.com/products/search-and-replace-for-wordpress-databases/ (I use this, and it works just fine). Then on the live server, create … Read more
“the boring work of backup”… Backups may be boring, but they are essential and gives you a fallback position in case things go wrong. Without backups, you’re essentially playing Russian roulette with your site. It doesn’t even take very long, and reverting isn’t horrible or awful, it’s pretty easy. WP veterans take backups, test upgrades … Read more
Your problem is that ob_file ain’t global. You only define it in c3m_export_xml(). Setting global $ob_file in ob_file_callback() gives you an empty file handle. Try this instead: function c3m_export_xml() { $args=array( ‘content’ => ‘posts’, ‘start_date’ => ‘october 2008’, ‘status’ => ‘published’); ob_start(); export_wp($args); $xml = ob_get_clean(); file_put_contents(‘server_path_to_my_file.xml’, $xml); }
I’ve been doing this successfully with csync and an NDB cluster for years… Re other solutions: rsync works too, albeit slower. (Much, much slower; slow enough to rule out any file-based caching.) InnoDB/MyIsam master/slave works too, with HyperDB. But, you’ll end up with a need to manage other stuff, namely auto-increments on write servers, if … Read more
There is a significant amount of memory usage if you use the $wpdb for queries that return very large result sets. $wpdb loads the entire results from any given query into memory. So if you’re, say, selecting all the posts, then it’ll try to load the whole thing into memory immediately. So for something like … Read more
I’ve personally had limited success with the backup/restore plug-ins that are commonly available. Many times, the best backup plug-ins don’t allow for a direct restoration from a backup file. So I do things manually. It’s a bit more difficult, but far more reliable, too. Backing up with phpMyAdmin Log in to your host’s control panel … Read more