Support/Comments for AjaxSearch 1.8.5-Finale

This is an auto-generated topic for <a href="http://modxcms.com/extras/package/8">AjaxSearch 1.8.5-Finale</a> by coroico.

Brief Description:

<h3>Ajax and non-Ajax search that supports results highlighting</h3>

<h3>Updates</h3>

<strong>AjaxSearch - version 1.8.5</strong>


See ajaxSearch_version_185.txt and ajaxSearch_readme.txt in the zip file


Wiki documentation : <a href="http://wiki.modxcms.com/index.php/AjaxSearch">http://wiki.modxcms.com/index.php/AjaxSearch</a>

Bugs & features tracker : <a href="http://svn.modxcms.com/jira/browse/AJAXSEARCH">http://svn.modxcms.com/jira/browse/AJAXSEARCH</a>

Demo site : <a href="http://www.modx.wangba.fr/index.php?id=51">http://www.modx.wangba.fr</a>


Includes the version 1.5.0 of the plugin searchHighlight

and the version 1.5.0 of the plugin advSearchHighlight


The release 1.8.5 includes:

All the template files have been saved with an utf-8 (without BOM) format


==== pcre_backtrack limit

The backtrack_limit setting sets the maximum number of bytes preg is allowed to search over before it gives up. This limit is automatically set to 1600000 at the beginning of the script and then restored to the initial value at the end of the script.

Should solve AJAXSEARCH-20 issue


==== fix the followings issues:

AJAXSEARCH-50 : Filter returns all records when it should return nothing

AJAXSEARCH-57 : CentOS - ajaxsearch 1.8.4 fails with a preg_replace() - lookbehind assertion

AJAXSEARCH-58 : Remove possibility of XSS attempts being passed in the URL of advSearch_Highlight and Search_Highlight plugins (JVN #46669729)

AJAXSEARCH-43 : Unable to get custom tv content (i.e. image link or other text) in template chunk


==== New language files

The Icelandic and Indonesian language files have been added

Odd problem: Getting no results from search on private pages even when logged in as a web user with access to those pages. I know the permissions are working because I can browse to the page when logged in but trying to search for anything on that page produces no results. Search works fine when page permissions are set to public. Any idea what I’m doing wrong? Urgent help needed, page is supposed to go live in two days.


UPDATE: I switched to non-ajax mode and it searches secure pages properly when logged in, but in ajax mode it produces no results. What up with that?

I found a bug in version 1.8.5, included in MODx 1.0.3

Using PHP5, UTF-8, mbstring – result of function getExtract invalid: «......» (no cut fragment).
To correct: in file ajaxSearch.class.inc.php after
$msgErr = "
<h3>AjaxSearch: php_mbstring extension required</h3>
";
$valid = false;
}
Add
elseif (($this->dbCharset == ’utf8’) && ($this->cfg[’mbstring’]))
mb_internal_encoding("UTF-8");

@claytonk

Congratulations! You find an issue that exists since the release 1.8.0 !
When you are logged as a web user the search with the ajaxSearch mode, didn’t take into account the private documents !
I and nobody never seen this issue before. This bug is now registered as AJAXSEARCH-61

Urgent help needed, page is supposed to go live in two days.

And you are a lucky man, because, somewhere in France, a guy has found one hour during his week-end to understand the reason of this issue.

To fix this issue in the assets/snippets/ajaxSearch/ajaxSearchPopup.php file replace the lines 48-49:by the following lines:
For your understanding the $_session variable wasn’t initialized with the ajax mode, so the script couldn’t find the private documents of the logged user.

Hope that with this fix, your site will be launched monday morning

The demo site has been updated with this fix. On this demo page, try to search "worker". When you are not logged you get one public result.
Use the login option menu (horizontal menu) and log you. Then redo the search. You get 2 private additional documents

@Akots

Using PHP5, UTF-8, mbstring – result of function getExtract invalid: «......» (no cut fragment).

Not sure to understand which results you get. You get an empty extract ?

Add
elseif (($this->dbCharset == ’utf8’) && ($this->cfg[’mbstring’]))
mb_internal_encoding("UTF-8");

You are right. But in the ajaxSearch 1.9.0 I have corrected this issue in the getExtract function. So I suggest to do the same.

So, in the classes/search.class.inc.php file - getExtract function replace:
by
Thanks for this feeback. I register this issue (and its fix) as AJAXSEARCH-62

Quote from: coroico at Apr 10, 2010, 10:42 AM

Not sure to understand which results you get. You get an empty extract ?

Yes, empty in some cases.

Urgent help needed, page is supposed to go live in two days.

And you are a lucky man, because, somewhere in France, a guy has found one hour during his week-end to understand the reason of this issue.

You’re the best! Thx, it works like a charm, all is good in the world.