- Posts: 1
- Thank you received: 0
Getting error on search. No error code or clues
- mcasner
- Topic Author
- Offline
- New Member
Less
More
8 years 9 months ago #2371
by mcasner
Getting error on search. No error code or clues was created by mcasner
Hi,
We are running the most recent version of Custom Properties on our website, www.resources4adoption.com .
We've discovered an error when a user tries to perform a search. There are no results, just the word error on the page.
I've attached a screenshot that shows the error message.
What should we do? Is there a way to troubleshoot.
We are running the most recent version of Custom Properties on our website, www.resources4adoption.com .
We've discovered an error when a user tries to perform a search. There are no results, just the word error on the page.
I've attached a screenshot that shows the error message.
What should we do? Is there a way to troubleshoot.
Please Log in or Create an account to join the conversation.
- andrea_4g
- Offline
- Administrator
Less
More
- Posts: 1122
- Thank you received: 163
8 years 9 months ago #2372
by andrea_4g
Replied by andrea_4g on topic Getting error on search. No error code or clues
That very uninformative error message is triggered when an error - that was not caught and/or prevented otherwise - occurs during the execution of the main selection query of CP.
In order to troubleshoot the error and get to the root cause you need to debug the query.
At line 1000 of file components/com_customproperties/models/search.php you'll find a commented line that, when un-commented - will print the query on the screen.
(Uncomment the 'print "<pre>....' part of the line.)
You can then proceed to copy the query and run it against the DB using your preferred tool (i.e. phpmyadmin) and eventually understand what's causing the error.
In order to troubleshoot the error and get to the root cause you need to debug the query.
At line 1000 of file components/com_customproperties/models/search.php you'll find a commented line that, when un-commented - will print the query on the screen.
(Uncomment the 'print "<pre>....' part of the line.)
You can then proceed to copy the query and run it against the DB using your preferred tool (i.e. phpmyadmin) and eventually understand what's causing the error.
Please Log in or Create an account to join the conversation.
Time to create page: 0.165 seconds