WordPress already has this available under Tools > Export. You can export all of your posts, comments, authors, etc. into an XML file which you can them Import into a new (or not new) installation. I believe this has been part of the core since WordPress 2.1.
This is actually stored in the {prefix}sitemeta table. The meta key is site_admins, and it’s a serialized PHP array of usernames.
I believe the issue is that your function that sets up the settings initially isn’t getting run upon activation. Add a call to your mouldings_register_settings_initial() in the activation hook, like this: function mouldings_activate() { global $wpdb, $mouldings_options; mouldings_register_settings_initial(); if ($mouldings_options === false){ $mouldings_options = array( ‘idea_item_columns’ => ‘4’ ); update_option( ‘mouldings_settings’, $mouldings_options ); } } … Read more
You could use a WordPress action hook. For example, you could add the following code to your themes functions.php file: add_action( ‘init’, ‘your_script_function’ ); function your_script_function() { // your script here } The first line makes WordPress execute the ‘your_script_function’ function on initialization. You can add your script in that function. Alternatively, you could add … Read more
No, to be honest 35 is nothing. You should not see any problems scaling this into the hundreds/thousands if optimized right, it does depend on many factors. Where is the post meta being used, are you sure it’s all being used? Are you using a lot of unique keys? You can check this by doing … Read more
The same WordPress Codex has a page for backing up your database with phpmyadmin; see http://codex.wordpress.org/Backing_Up_Your_Database You must export and import the database itself – and not do a posts export from the dashboard – to retain all settings, image URLs, etc. Either use phpmyadmin in your host control panel, or you can use it … Read more
WordPress has a pretty flexible way of handling custom data, and it stores it in a table called wp_postmeta (assuming default wp_ prefix). The only catch is that it assumes that it will somehow be related to a certain post, which I’m not sure you actually want to do. It’s very simple to use (see … Read more
Concept As I’ve currently done this, I found the easiest part would be to save the original UID (unique ID) from your “origin”-database as post meta value. Every time you update a post, you just have to search for a post that has this meta entry. Just make sure that you set the last value … Read more
$wpdb->get_results(); has a second parameter for the return format: /** * Retrieve an entire SQL result set from the database (i.e., many rows) * * Executes a SQL query and returns the entire SQL result. * * @since 0.71 * * @param string $query SQL query. * @param string $output Optional. * Any of ARRAY_A … Read more
Avoid serialized whenever you can. It is slow to read and you cannot really search for it. Use custom tables – more than one: One for the relationship between users, tags and images: user_id, tag_id and image_id. One for tag meta data, your attributes, if I understand that right: tag_id, meta_1, meta_2 … Now you … Read more