Dismissed pointers are stored as user meta, you can inspect this for yourself with: $meta = get_user_meta( wp_get_current_user() ); print_r( $meta[‘dismissed_wp_pointers’] ); In your case, the meta might be empty or damaged, to update dismissed pointers for ALL users on your blog, you could run this function (only once): function wpse80084_dismiss_wp_pointers() { $dismissed = array( … Read more
SELinux was contributing to the problem. The main issue was that an HTML page was attempting to talk to another port on the localhost. I would not have seen the problem if the HAProxy was running on a separate host. The log was revealed in /var/log/messages, where I should have checked but did not considering … Read more
Got it solved. Probably not the most efficient way but it works! SELECT product_id, meta_value FROM ( SELECT order_meta.order_item_id, order_meta.meta_value AS ‘product_id’ FROM wp_woocommerce_order_itemmeta AS order_meta LEFT JOIN wp_woocommerce_order_items AS order_items ON order_meta.order_item_id = order_items.order_item_id LEFT JOIN wp_term_relationships AS term_rels ON term_rels.object_id = order_items.order_id WHERE term_taxonomy_id = 24 AND order_meta.meta_key = ‘_product_id’ ) AS product_ID … Read more
Rather than mess around trying to find the serialised data that got messed up, just use a tool to migrate environments and avoid messing up serialised data. WP Migrate DB is a good one that handles serialised data properly. The free version does a great job, as long as you don’t have a huge database. … Read more
Backup your db Remeber to backup your db Import the backup in another database, change wp-config.php to use this new database and see if everithing is ok. (Importing is successfull? Site appear without any change?) WordPress uses a prefix for table names. The default is ‘wp_’ but clever guys change it with something else. (The … Read more
This sounds like you have a hierarchical post type. You will have trouble with hierarchical post types with large numbers of posts because query results have to be sorted/resorted. Register you post type with hierarchical set to false, if you can.
why is $wpdb->update() causing a DB error from within wp_set_password()
I simplified your query, but wouldn’t something like this accomplish it? SELECT * FROM $wpdb->posts AS p LEFT JOIN $wpdb->postmeta AS pm ON p.ID = pm.post_id LEFT JOIN users AS u ON pm.meta_value = u.user_id WHERE pm.meta_key = ‘user_id’ AND post_status=”publish” ORDER BY p.ID DESC LIMIT 50;
You can update just joining both table on comparing same userid. like: update t1 join t2 on t1.user_id = t2.user_id set t1.meta_value = t2.desc;
Alright. I think I cracked it. <dateTime.iso8601>20140111T20:39:15</dateTime.iso8601> Should be: <dateTime.iso8601>20140111T20:39:15Z</dateTime.iso8601> Looks like the toolkit I was using didn’t quite implement iso8601 perfectly (or wordpress isn’t – not sure). I’m using Node WordPress and tracked down that it uses the module Node XML RPC to actually send the XML RPC. This seems to be where the … Read more