- Messaggi: 1
- Ringraziamenti ricevuti 0
Getting error on search. No error code or clues
- mcasner
- Autore della discussione
- Offline
- Nuovo Utente
Less
Di più
8 Anni 9 Mesi fa #2371
da mcasner
Getting error on search. No error code or clues è stato creato da 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.
Si prega Accesso o Crea un account a partecipare alla conversazione.
- andrea_4g
- Offline
- Amministratore
Less
Di più
- Messaggi: 1122
- Ringraziamenti ricevuti 163
8 Anni 9 Mesi fa #2372
da andrea_4g
Risposta da andrea_4g al 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.
Si prega Accesso o Crea un account a partecipare alla conversazione.
Tempo creazione pagina: 0.299 secondi