Disable smartsearch

[yggdrasil]

Is there a way to disable the new SmartSearch feature and have it working like it was previously?

[brian!]

52 minutes ago, yggdrasil said:

Is there a way to disable the new SmartSearch feature and have it working like it was previously?

still not managed to get it working properly on your updated WHMCS yet ?

theoretically, I suppose if you could take the appropriate js code from your pre-updated version, and replace the equivalent code in the current version, that might work... but that's possibly dependent on the old intelligent search method working with the updated js file.

even though there is an IntelligentSearch hook, I think it only adds access to additional custom search results, not replacing the existing search (e.g the hook results come after the main results) - though if you find the time to play with the hook, I might be wrong.

[yggdrasil]

5 hours ago, brian! said:

still not managed to get it working properly on your updated WHMCS yet ?

theoretically, I suppose if you could take the appropriate js code from your pre-updated version, and replace the equivalent code in the current version, that might work... but that's possibly dependent on the old intelligent search method working with the updated js file.

even though there is an IntelligentSearch hook, I think it only adds access to additional custom search results, not replacing the existing search (e.g the hook results come after the main results) - though if you find the time to play with the hook, I might be wrong.

How would I? The errors come from encoded files in the vendors folder. I cannot check or debug that. I just want the old search that worked for me in the past back. Nothing related to the new route paths on Laravel works on my installation. The more WHMCS moves stuff into that framework the more things break on my server.

[brian!]

18 hours ago, yggdrasil said:

How would I? The errors come from encoded files in the vendors folder.

not necessarily - as an example, I can invalidate the code within an action hook (on purpose or by accident lol) and it will throw up all sorts of errors in /vendor/illuminate/database/ - but that's not where the problem is, the cause of the errors are the hook not something within vendor itself.

i'm surprised that after an update, and if you are using an updated version of Blend, that you're seeing Intelligent Search errors... for that to occur, there must be legacy files present, and/or hooks etc... I know sentq posted a intelligentsearch hook years ago - you're not still using that are you?

18 hours ago, yggdrasil said:

I just want the old search that worked for me in the past back.

then i'm tempted to say that you really should have tested before updating... if you know you've got a highly modified installation, surely it would have been sensible to dip your toe in the water first?

[yggdrasil]

2 hours ago, brian! said:

not necessarily - as an example, I can invalidate the code within an action hook (on purpose or by accident lol) and it will throw up all sorts of errors in /vendor/illuminate/database/ - but that's not where the problem is, the cause of the errors are the hook not something within vendor itself.

i'm surprised that after an update, and if you are using an updated version of Blend, that you're seeing Intelligent Search errors... for that to occur, there must be legacy files present, and/or hooks etc... I know sentq posted a intelligentsearch hook years ago - you're not still using that are you?

then i'm tempted to say that you really should have tested before updating... if you know you've got a highly modified installation, surely it would have been sensible to dip your toe in the water first?

I did. The error was spotted in my dev/test installation but I did not care because its not a hard breaking feature. The client area and other things like billing are working fine, so I gave a green check to move the upgrade to production. For me, not being able to search or something else broken in the admin is not as critical as opposed to issues on customers that need to be fixed intermediately.

Now that you say, I think I did spot some errors related to hooks while triggering a search query. It seems the search wants to use some hooks. I will double check that.