Using the wpdb::prepare() method is recommended for creating queries properly and avoiding SQL injection. For a basic solution, use the addslashes() function, but this is not sufficient for preventing SQL injection. See Mysql + php with special characters like ‘(Apostrophe) and ” (Quotation mark).
Given your detailed description, it seems you’ve taken several steps to address the issue of sorting your archive pages in WordPress. The fact that changing the “order”:”desc” to “asc” in the archives.html file of your theme didn’t yield the desired result suggests a deeper issue. Try this in your functions.php file: function wpb_modify_category_query( $query ) … Read more
Can I filter existing search query using pre_get_posts for post_mime_type?
I think the problem is here {$wpdb->prefix}prflxtrflds_user_field_data It seems your {$wpdb->prefix} value is prflxtrflds So you can directly use : global $wpdb; $results = $wpdb->get_results( “SELECT user_id FROM {$wpdb->prefix}user_field_data WHERE id = 37” );`
How to make query loop block dynamic
You could certainly write a wrapper function that implements caching of the WooCommerce core functionality, but WooCommerce isn’t going to use your wrapper function, so pretty pointless. Your best option is to create and use your own data store for WooCommerce that extends the WC_Data_Store_WP class, and add caching to those functions.
import/view table from external site
Add a category to posts, that DO NOT contain two specific keywords?
Getting the correct post ID in WordPress query loop
Optimizing AJAX Query with Large Database