Please could you give me some guidance on achieving this.
Thanks as always
Marcus
Is it possible that at some point, the WordPress core will require other indexes that could conflict with your optimizations? Or is it possible that some keys should actually be reverted but your plugin prevents it, which could be harmful to WordPress itself?
Thank you very much for such a great plugin; it seems to work exceptionally well.
]]>wppepvn_post_content
wppepvn_post_excerpt
wppepvn_post_name
wppepvn_post_title
and I do not know where they came from
all keys are FULLTEXT keys
is it related to this plugin ??
Is it possible to create 2 indexes?
I have created an index that uses filters to included only a custom post type, along with some additional attributes for facets derived from a custom taxonomy. I have then created a page (not the search page) for visitors to find particular information, all of which is working fine.
But obviously this impacts the site search which will now only return the results from my index that contains custom posts as I have had to leave either the “Use Algolia in the backend” or “Use Algolia with Instantsearch.js” active.
So is it possible to:
1. Create another index that contains all searchable posts that I can use on the site search results page?
2. Disable Algolia for site results page, without activating “Do not use Algolia”?
Thanks as always.
]]>I know you can use:
name_starts_with
But what about:
last_name_starts_with
or first_name_starts_with
]]>Notice: Undefined index: show in xxx/wp-content/plugins/advanced-cf7-db/admin/class-advanced-cf7-db-admin.php on line 693
Notice: Undefined index: label in xxx/wp-content/plugins/advanced-cf7-db/admin/class-advanced-cf7-db-admin.php on line 690
This shows when debugging is on and the labels are customized in the Dashboard.
Also, please add support for calls within a class of functions such as:
add_action('cfdb7_before_save_data', array($this, 'cfdb7_modify_data'));
I am using the most recent plugin and WordPress versions.
Thank you,
Noah
]]>isset( $GLOBALS["wpdb"] )
should be written as isset( $GLOBALS["wpdb"%5D )
.
We are looking into a fix for this that would allow the use of the ‘]’ character directly.
https://www.ads-software.com/plugins/content-visibility-for-divi-builder/
]]>https://www.ads-software.com/plugins/recipe-card/
]]>Is there anyway in MySQL for WordPress to find out “missing” indexes.
I constantly get (in Server Monitor) long waiting queries that say “copying to temp table” or “sorting result” in the state column (Navicat) when the query is something simple like
SELECT SQL_CALC_FOUND_ROWS wp_posts.ID FROM wp_posts WHERE 1=1 AND wp_posts.post_type = 'post' AND (wp_posts.post_status = 'publish') ORDER BY wp_posts.post_date DESC LIMIT 0, 10
Where this query in theory should be running very quickly it sometimes has a very long wait/execution time and I have no idea why.
Plus I don’t know who (which page) is calling it.
Is there any way in MySQL to find out “missing indexes” like MS SQL?
This is where the System has calculated that an index on X columns on X table would increase performance by a cost of X %.
I use a system to store this info from the SQL DMV’s so that I have it saved in case of a reboot of the server. This helps me over time find out when I need to add/delete indexes.
Is there ANYTHING similar in MySQL?
It seems pretty basic to me and I know EXPLAIN shows some useful data but you need to first know the query before running it and analysing.
The Slow Query Log is also useful BUT a lot of these queries when taken out and run on their own in Navicat for example run instantly so it seems like a problem in the back-end of MySQL or WordPress that is causing locks/deadlocks etc.
So far I cannot see anyway of finding out easily if one query is locking up another in MySQL.
And yes I use MySQL Tuner and all the other tuner systems all the time which always come back fine apart from don’t sort on disk and always optimize.
As I cannot really change the core queries within WordPress to run more efficiently all I can do is add indexes to help them.
So I need a way to find these “missing” indexes and problematic queries.
Thanks
Rob
]]>