In AjaxSearch 1.7.1 I can’t find where it reads the config from. I had to hack ajaxSearch.php for database_connection_charset to work.
-
☆ A M B ☆
- 1,031 Posts
Same thing with Safari 3.1 on Mac OS X 10.5.
Any idea why this result comes back after install of 1.7.1 :
AjaxSearch: database_connection_charset is null. Check your config file
TIA
-
☆ A M B ☆
- 24,524 Posts
Because if your /manager/includes/config.inc.php file doesn’t have its database_connection_charset set to match your database’s charset, the search query can return garbage.
Thanks Susan,
The /manager/includes/config.inc.php had a blank entry for the charset.
Adding utf8 fixed it - maybe the author should put this in the notes of the snippet. As this install was a base 0.6.2b out the box - it will maybe therefore occur on every install of the new snippet version??
-
☆ A M B ☆
- 24,524 Posts
There’s work being done to automate this as part of the installation process.
-
MODX Staff
- 2,502 Posts
Is there any way to block inclusion of specific TVs in search results or at lease restricting search to specific documentObject elements like intortext or content only?
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
