If this is a standard CMS (not something you came up with yourself), I would say that a WXR solution is the way to go. It might take some extra work, but it will be a good learning experience and a nice way to build up your WordPress skills. The WXR route will be an … Read more
If you’ve got 60,000 records, try cleaning post/page revisions; these really accumulate and cause excessively long queries. I’ve seen database sizes drop 90% with huge increases in performance. Run the query below in phpmyadmin or from the command line and then optimize: DELETE a,b,c FROM wp_posts a LEFT JOIN wp_term_relationships b ON (a.ID = b.object_id) … Read more
You can do this right in interface: Select posts in need of change in admin post list screen Select Edit in Bulk actions dropdown and press Apply next to it Choose Format > Image in interface panel that appeared Press Update to apply
It’s set in schema.php, the WordPress Administration Scheme API. You can also find it in the Codex. As you can see from a search through core, there’s (as far as my search went) exactly no use case for it, aside from defining it as 0 when adding that option to the DB. If you want … Read more
If you have databases reachable from the outside ie: mysql1.example.com you can work on a local development environment connected to that the whole time. I just found a nice thing to put in wp-config.php to be able to change the host depending on your environment $host = $_SERVER[‘HTTP_HOST’]; define( ‘WP_HOME’, ‘http://’ . $host ); define( … Read more
You most probably only added one of the following in your wp-config.php file thinking they were the same, as m73mitchell and I had done: define(‘WP_ALLOW_MULTISITE’, true); define(‘MULTISITE’, true); I couldn’t find any documentation why they have this counterintuitive setup, but just add the one you missed and it should work.
What you did wrong here was to prepare those items in the first place. You only run “data” variables through prepare(). You don’t run table names, or sort directions, or limits through it. These are part of the SQL command itself, they are not data that refers to information which is stored in a column … Read more
if you want to keep the row with the lowest id value: DELETE n1 FROM table n1, table n2 WHERE n1.id > n2.id AND n1.meta_key = n2.meta_key OR if you want to keep the row with the highest id value: DELETE n1 FROM table n1, table n2 WHERE n1.id < n2.id AND n1.meta_key= n2.meta_key
Firstly I would try to avoid the use of a custom table using custom post types, custom taxonomies and post/user/term meta. This will greatly increase compatibility and give you a large chunk of free functionality, such as UIs, import/export support, archives, REST APIs, etc But assuming you cannot use that, for whatever reason, you should: … Read more
You should’nt really be using wp query here, use get_user_meta(); Example: $first_name = get_user_meta(2, ‘first_name’, true);