Forums › Forums › Search & Filter Pro › Problem with Caching Tables
- This topic has 11 replies, 7 voices, and was last updated 7 years ago by
Anonymous.
-
Trevor(Private) November 8, 2016 at 10:43 pm #69325
It is something to do with the way the database is setup on your server.
These (amongst many others) threads discuss this:
https://support.searchandfilter.com/forums/topic/problem-when-trying-to-activate-plugin/
https://support.searchandfilter.com/forums/topic/no-results-found-13/
And also check out these comments on twitter from Justin Mazzi –
https://twitter.com/jmazzi/status/743116381185576960
https://twitter.com/jmazzi/status/743116653764960256I may need to ask the developer tomorrow. Give me a ‘bump’ tomorrow to do this unless it makes sense to you?
Ross Moderator(Private) November 30, 2016 at 4:01 pm #73235Hi Christian
We’re absolutely happy to help.
The problem with this particular issue is that there is only one “official” way to create table in WordPress from plugins –
https://codex.wordpress.org/Creating_Tables_with_Plugins
We do it this way, so when it fails its nearly impossible to tell why – the real issue in solving is recreating it in the first place.
If you can share some info on your setup, then perhaps I can recreate it and solve.
Would you be able to supply your server config, including DB & PHP versions etc?
Thanks
Anonymous(Private) November 30, 2016 at 4:25 pm #73252Thanks for your reply.
You can provide this -working- solution:
Execute the following SQL:
CREATE TABLE wp_search_filter_cache ( id bigint(20) NOT NULL AUTO_INCREMENT, post_id bigint(20) NOT NULL, post_parent_id bigint(20) NOT NULL, field_name varchar(255) NOT NULL, field_value varchar(255) NOT NULL, field_value_num bigint(20) NULL, field_parent_num bigint(20) NULL, term_parent_id bigint(20) NULL, PRIMARY KEY (id), KEY field_name_index (field_name), KEY field_value_index (field_value), KEY field_value_num_index (field_value_num) )
And:
CREATE TABLE wp_search_filter_term_results ( id bigint(20) NOT NULL AUTO_INCREMENT, field_name varchar(255) NOT NULL, field_value varchar(255) NOT NULL, field_value_num bigint(20) NULL, result_ids text NOT NULL, PRIMARY KEY (id), KEY field_name_index (field_name), KEY field_value_index (field_value), KEY field_value_num_index (field_value) )
Done!
Ross Moderator(Private) December 3, 2016 at 1:16 pm #73818Thanks for the update still looking into how to solve this permanently.
Best
Trevor(Private) January 4, 2018 at 7:42 pm #150622You will need to use something like phpmyadmin in your control panel, or maybe the ARI Adminer plugin from inside WP Admin.
If you are not confident of doing this, talk to your host and ask them for assistance. If you are using a prefix in your WordPress tables, the code would have to be modified.
Ross Moderator(Private) January 12, 2018 at 5:17 pm #152266Hi Nils
The code should be the same on multisite, however, you must use the correct multisite prefix for your table name.
So
CREATE TABLE wp_search_filter_cache (
would become
CREATE TABLE wp_1_search_filter_cache (
and
CREATE TABLE wp_search_filter_term_results
would become
CREATE TABLE wp_1_search_filter_term_results
You would need to repeat this for each site in your multisite and use the correct ID of the multisite in the table names.
I imagine this must be a pain getting setup especially with a new plugin.
And on personal level I would like to get this solved once and for all.
Would you be willing to let me do some testing (early next week) on your (dev) site to try to resolve this issue within our plugin?
Thanks
-
AuthorPosts