This is really a server question and not particularly WordPress. You’re running into a MySQL server speed bottleneck at 1and1. Sorry, but they’re well known as a slow shared host, and for that reason I doubt their VPSs are any better. Caching and a CDN will only do so much for you. You need more … Read more
I would not do this with SQL. A relatively simple PHP loop should work. function bulk_schedule_posts_wpse_105834() { $args = ( array( ‘cat’ => 1, ‘posts_per_page’ => -1, ‘post_status’ => ‘draft’, ‘post_type’ => ‘post’, ) ); $posts = new WP_Query($args); if (!$posts->have_posts()) return false; $date=”2013-08-01″; $times = array( ’10:00′, ’14:00′, ’17:00′, ’20:30′ ); while ($posts->have_posts()) { … Read more
You can prevent more than three revisions from being saved to the database in the future by adding this line to your wp-config.php file: define( ‘WP_POST_REVISIONS’, 3 ); That line should limit new posts to three revisions, but it won’t go through your database and clean it up. The SQL snippet that you found for … Read more
You can find the database information by looking at your wp-config.php (which will be in your WordPress root folder). Your wp-config.php will probably tell you then that your database host is “localhost” (DB_HOST) and since you are using XAMPP locally, the location of your DB would be wherever you are running MySQL basis your XAMPP … Read more
Persuming “article_datetime” to be a numeric value, I would suggest that instead of using ‘orderby’ => ‘meta_value’ use ‘orderby’ => ‘meta_value_num’ If still query is slow, than remove: ‘orderby’ => ‘meta_value’, ‘meta_key’ => ‘article_datetime’, ‘order’ => ‘DESC’ and instead sort the result in php.
No, you are not missing something. But you are using the wrong “framework” (which WordPress is not) for your use case, it seems. And you are mixing things up. What you are talking about, A.C.I.D. transactions, is by no means what you think it is for. ACID: save crash recovery (due to soft- or hardware … Read more
Your JavaScript code works for me. The metadata do get saved. But perhaps you’d like to try my code which is pretty much completed, i.e. on page load, the checkbox is auto-checked/unchecked (and the text box is also shown/hidden) depending on the current database value. Secondly, I did it just as the Gutenberg team did … Read more
It all depends on your workflow. If you have no use for the post revisions and autosaves then disable them in wp-config and WordPress will clean them up on its own. You may also prefer to limit how many you keep at once. Also the space they take up is unlikely to be of a … Read more
I had to do something similar. What you need to do first is in each of your config files define the table prefix … make sure that they are different. Example: WordPress installation 1: wp123_ WordPress installation 2: wp124_ Your first installation would be your main installation the one with the user table you want … Read more
Actually, the customary way to do this in WordPress would be to use <?php update_post_meta($post_id, $meta_key, $meta_value, $prev_value); ?> as per the codex: https://codex.wordpress.org/Function_Reference/update_post_meta. It yields shorter code, and the intent of the code is clearer.