problem getting results

Ross Moderator

#31980

This reply has been marked as private.

Anonymous

#73575

Just wanted to come by and say I had the same issue. Creating the tables like you said fixed the issue.

But here where the error messages I got:

Search & Filter Error: The caching tables are missing - click here to create them

Clinking on this gave the following error

WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
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) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

WordPress database error: [Index column size too large. The maximum column size is 767 bytes.]
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) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

and there was another error when activating the plugin in the admin area stating:

The plugin generated 1383 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

Hope it helps,

Ross Moderator

#73816

Thanks for the update, its strange because the manual SQL code I’ve pasted here is the exact same code used internally (in regards to index column sizes etc) so its odd one works and the other doesn’t.

When activating the plugin it tries to create the tables if they do not exist, so its likely those errors you’ve pasted causing the error message when activating too.

Thanks for the info, it is helpful and hopefully after some digging I can get rid of this error once and for all!

BTW, can you share a little about your environment, ie DB type, version, PHP version, server (nginx etc)

Thanks

Anonymous

#73820

@Ross not really familiar with server stuff, but PHP Version 5.6.28, DB type PhpMyAdmin? and I think nginx 1.8

hope it helps,

Ross Moderator

#74539

Hey Mitchel thanks for the info…

RE the DB, it could be MySQL, MariaDB etc (PhpMyAdmin is just a nice web based UI to access the DB), could you confirm this for me? I think this detail may be the key (and if you can find version number that would also be great).

I think phpinfo could uncover these details if your host does not already provide this information.

Thanks for digging for me.

Best

Anonymous

#74858

Hey @Ross,

A my bad. Could it be mysqlnd 5.0.11-dev for a better impression here is a Gist of the whole phpinfo(); https://gist.github.com/mvaneijgen/94fdca71802c792393cf690a00b11568

Hope it helps,

Ross Moderator

#74861

Got it thanks.

Posting your whole phpinfo can be a security risk, I would advise to delete that gist 🙂 i have the info now.

Best

Anonymous

#98654

If anybody is still having a problem with this and get the error saying column is too large, just modify the varchar(255) to varchar(190). If using the utf8mb4 method in your db then the max characters will exceed 765bytes. 255×4 = 1020 so 190×4 = 760

Ross Moderator

#98852

Thanks for the info Daniel, so its to do with the encoding of the DB – when I guess not the default WP one is used… I’ll have a dig around the WP code to see how they implement this when creating the posts table.

Thanks

[Author]

Posts