So the only reason you want to re-architect WordPress to use multiple tables for different post types is because your posts table is getting bigger too fast? I assume the underlying issue for you is that performance is suffering? Instead, I suggest adding appropriate indexes to the post table for the queries you are finding … Read more
You can just use the function switch_to_blog before running the WP_Query on your post_type “projects”. Switch the current blog to a different blog. switch_to_blog(), is useful if you need to pull posts or other information from other blogs. Sounds like this is what you want. So lets say you have your content on the main_site. … Read more
I’ve logged a ticket against this with trac: http://core.trac.wordpress.org/ticket/20536 However, it turns out that for the time being it IS necessary, as WordPress currently (since 2.x) has a bug that DOES associate two terms with the same name to the same term_id! So it IS possible (though incorrect) for a single term to be associated … Read more
This answer is the way I would take to solve the issue if I had to face it, it means is not the answer but one of the possibilities. All the operations I will suggest should be run on a development/local server on a backup of database and not on production nor on original database. … Read more
This is precisely what custom post types are for. If it were my project, I’d scrap the custom table you have, set up a custom post type for your “widgets”, add all your existing widgets as regular WP content, and use standard WordPress functions and templates to query and display them. It’s a bit of … Read more
If your main requirement is to synchronise blog posts from a master site to a slave, then maybe look at the FeedWordPress plugin. It means that you would only add/edit posts on one website and they would be replicated to the other site. That will allow you to cleanly run different plugins on the two … Read more
This is because the site_url and homeurl of your original installation are set to HTTPS in the database, so you can’t access your website on localhost unless you: Change these values to non-ssl Install a SSL certificate on localhost I will only explain the first case since installing a certificate is out of this community’s … Read more
$wpdb->query(“INSERT INTO settings-table (option_name, option_value, option_created, option_edit, option_user) VALUES (‘name-1’, ‘val-1’, current_time(‘mysql’), current_time(‘mysql’), ‘user-1’), (‘name-2’, ‘val-2’, current_time(‘mysql’), current_time(‘mysql’), ‘user-2’), (‘name-3’, ‘val-3’, current_time(‘mysql’), current_time(‘mysql’), ‘user-3′)”) In the query which you had posted, the column names shouldn’t be in string.
This doesn’t sound like something coming from WordPress core. Quick search online got pretty slim results, but it seems to be asscociated with WP All Import plugin.
Hi @Justin Jenkins: It’s very hard for use to say if WordPress will or will not support it since they can make those decisions and we cannot. However we can look at some evidence. SQL Server? For SQL Server on one hand a trac ticket was debated and stalled a year ago; since then more … Read more