Notifications
Clear all

wpForo 1.x.x [Solved] Search Error When Using Searching Entire Posts Option

10 Posts
2 Users
1 Reactions
1,307 Views
Posts: 6
Topic starter
(@peterd)
Active Member
Joined: 4 years ago

I can successfully use Search on all of the Search Types expect 'Search Entire Posts'. I get the following error when trying to do this:

Warning: mysqli_query(): (22003/1690): DOUBLE value is out of range in '((match `db9dd6w7ev6y6f`.`p`.`title` against ('+pictures*' in boolean mode)) + (match `db9dd6w7ev6y6f`.`p`.`body` against ('+pictures*' in boolean mode)))' in /home/customer/www/bookoncapecod.com/public_html/wp-includes/wp-db.php on line 2033

This is a very similar message that I found in this forum post:
https://wpforo.com/community/general-forums-bug-reports/search-showing-error/#post-47322

I tried using the recommendation in this post, but Search still fails when trying to use Search Entire Posts.  I've seen some other posts that suggest updating the database Collation value.  Similar to this post:
https://wpforo.com/community/how-to-and-troubleshooting-2/search-not-working-in-wpforo-double-value-is-out-of-range/paged/2/

Any advice on how to resolve this error?

Attached is my current server configuration, which is quite current.

 

 

9 Replies
Alvina
Posts: 1863
Moderator
(@alvina)
Member
Joined: 5 years ago

Hi @peterd,

Please let us know the version you use? If it, not the latest please update to the latest wpForo version(v.1.8.4) and check again.

Posts: 6
Topic starter
(@peterd)
Active Member
Joined: 4 years ago

It's a new installation of wpForo, so we're currently running version 1.8.4.

1 Reply
Alvina
Moderator
(@alvina)
Joined: 5 years ago

Member
Posts: 1863

@peterd,

Then we've suggested you to contact your hosting server support and let them know about the issue.

Posts: 6
Topic starter
(@peterd)
Active Member
Joined: 4 years ago

We're currently running on SiteGround, which is a very popular hosting service for Wordpress.  I could use a bit more direction on what I should be asking them.  Could you provide some advice on what I should be asking them to look at, which could potentially be causing the error?  Also, is there a way to temporarily disable this search option.  I'm Ok in the short term if we can use all the other search options except for the 'Searching Entire Posts' Option.  Thanks again for your help.

1 Reply
Alvina
Moderator
(@alvina)
Joined: 5 years ago

Member
Posts: 1863

@peterd,

 I could use a bit more direction on what I should be asking them.  Could you provide some advice on what I should be asking them to look at, which could potentially be causing the error? 

Just provide a Warning message that you provided in your first post.

 Also, is there a way to temporarily disable this search option?  I'm Ok in the short term if we can use all the other search options except for the 'Searching Entire Posts' Option.

Try the following JS code:

jQuery("option[value='entire-posts']").remove();

The code should be added in the current active theme JS files.

Posts: 6
Topic starter
(@peterd)
Active Member
Joined: 4 years ago

I used the plugin 'Insert Headers and Footers' and was successful to deactivate the option of Search Entire Posts.  Here's the code that I placed in the Footer:

<script type="text/javascript">

   jQuery("option[value='entire-posts']").remove();

</script>

Unfortunately, I still have the problem that both the sidebar search widget, and the search in the header defaults to 'Search Entire Posts' initially.  This causes the warning to show.  Is there a way to have the initial search defaults use 'Search Titles Only'?

I did follow-up with your suggestion to contact SiteGround support.  They indicated that the error message related to different PHP versions used for my website and the website plugin.  They suggested I downgrade from PHP 7.3.24 to 7.1.33.  When I did this the error went away!!!  Running a lower release of PHP is not ideal.  Any thoughts on whether there's an issue with PHP 7.3.XX running with wpForo?

 

1 Reply
Alvina
Moderator
(@alvina)
Joined: 5 years ago

Member
Posts: 1863

@peterd,

They suggested I downgrade from PHP 7.3.24 to 7.1.33.  When I did this the error went away!!!  Running a lower release of PHP is not ideal.  Any thoughts on whether there's an issue with PHP 7.3.XX running with wpForo?

We don't think that the issue is caused by the higher version of PHP.

Please contact your hosting server support and ask them to check this issue with this version PHP. Probably there should change some settings in the PHP version that have this issue.

Page 1 / 2