Is there a clean separation between the WP tables involved with presentation vs content? I would say “no”. There is no clean separation. There is mostly-separation. Most of your content is in the post and taxonomy tables, and most of your presentation is the options table. But you also have things like sticky post IDs … Read more
I think this issue is handled by WooCommerce in their plugin. It also creates its own tables and this is how they take care of Collation part. (I am referring to file class-wc-install.php of WooCommerce). They have written following code in the create_tables function global $wpdb; $collate=””; if ( $wpdb->has_cap( ‘collation’ ) ) { if … Read more
This is a pretty vague and broad question, but I’ll give it a shot. You can add the following code into a functionality plugin or if you’re running a theme, you could place it in your theme’s functions.php file. (Obviously you’ll have to change the SQL, attributes, etc – just a proof of concept) add_shortcode( … Read more
A single term can, theoretically, be present in multiple taxonomies (and have a different description in each). That’s where term_taxonomy_id comes into play, referencing a single term within a single taxonomy. In practice, WP tries to avoid that, and will create a term with the same name and a -2 (iirc) suffix on the slug … Read more
This is what you’re looking for: http://codex.wordpress.org/Plugin_API/Action_Reference/init Example from Codex: add_action(‘init’, ‘process_post’); function process_post(){ if(isset($_POST[‘unique_hidden_field’])) { // process $_POST data here } }
As far as I know the custom key-value pairs are kept in the wp_postmeta table. You can simply examine (and delete) them in the database directly. SELECT * FROM wp_postmeta WHERE meta_key LIKE ‘%you_old_key_name%’ The ACF configuration of the fields is another story, but you say that you don’t even have the field in the … Read more
Store the object temporarily in the database, but implement __sleep() and __wakeup() to avoid side effects. Alternatively, implement the Serializable interface and prepare the data in its methods. There is no need to store NULL values.
I can confirm that the imported post will get a new unique ID if (and only if) there already is an existing/conflicting ID in the target database. Given a post to be imported with an ID of 7579 (represented in the WXR export file as <wp:post_id>7579</wp:post_id>) and an existing post with that exact same ID … Read more
To recap the comment chain above: I think that’s a perfectly valid way of storing some options in the database, however, it’s good practice to prepend your option name with some unique characters pertaining to your site or something, like ‘my_simple_links’ to avoid possible collisions with other plugins and themes that add_options. Also, if you’re … Read more
My educated guess you will drown in edge cases, exploding in your face, if you try to shard specific post type in separate table. Since you seem to be actually concerned with meta rather than posts themselves, you could: implement custom table for it use Metadata API to store it in separate table, while retaining … Read more