1. For the coding UTF8 at discrepancy of the register of letters highlighting does not work. It is connected to features of functions preg - it is necessary to add a key "u". In the file search.class.inc.php correction:I know this update done by yourselft for the Russian language. I haven’t integrated this update because it doesn’t run on my environment with english or french langauge in UTF8.
$finalExtract = preg_replace( ’/’ . preg_quote( $searchTerm, ’/’ ) . ’/iu’, …
and in the plugin searchHighlight:
$pattern = ’/’ . preg_quote($word, ’/’) . ’(?=[^>]*<)/iu’;
2. At use html entitys a scrap of a required fragment can give out only a part, for example &quo or something similar. For correction in the file search.class.inc.php at the beginning of function getExtract it is necessary to add something like:As we use, urlencode, htmlentities is not required and generate lot of issue. About that look at this post:
$text=html_entity_decode($text, ENT_QUOTES, "UTF-8");
and at the end of function to correct a command approximately so:
$finalExtract .= $extracts[$i][’etcLeft’] . htmlentities($mbSubstr($text,$extracts[$i][’left’],$extracts[$i][’right’] - $extracts[$i][’left’]+1), ENT_QUOTES, "UTF-8") …
☆ A M B ☆
@rossco
Which highlight plugin do you use. If you use the new advSearchHighlight plugin, you need to frame the area of text you want highlight by <!--start highlight--> and end it by <!--end highlight-->
If you use the classical searchHighlight plugin, nothing as change, except that now it takes into account of the &advSearch parameter.
i assumed it was the same idea as the original one.No, with the classical plugin, you couldn’t frame the part you would like highlight and you cant’ have many areas in the same document. Only one : <body> </body>
and keep care do not add any id like
☆ A M B ☆
i assumed it was the same idea as the original one.No, with the classical plugin, you couldn’t frame the part you would like highlight and you cant’ have many areas in the same document. Only one : <body> </body>
<body id="type-a"> otherwise, it does’nt run it.
I have updated and keep the classical plugin for compatibility.
Select "Exact phrase" and search ", 58" – result: " ...amp;test for MODx". I wrote about it. It seems to me what better to correct it.
On http://www.modx.wangba.fr/index.php?id=144 choose the french documents (accented language) And run the following tests:
<body id="type-a">
<div id="header">
<div id="logo">
<h1>AjaxSearch</h1>
</div>
[!Wayfinder? &startId=`50` &level=`2` &outerTpl=`wfOuter` &innerTpl=`wfInner` &rowTpl=`wfRow` &hereClass=`active` &firstClass=`first` &lastClass=`last` &titleOfLinks=`description`!]
</div>
<!--start highlight-->
<div id="content">
<div id="colOne">
[*content*]
</div>
</div>
<!--end highlight-->
<div id="footer">
{{ajaxSearchFooterEN}}
</div>
</body>
I wrote, that if to put in the beginning of function getExtract:
Any suggestion to improve this is welcome.
I know this update done by yourselft for the Russian language. I haven’t integrated this update because it doesn’t run on my environment with english or french langauge in UTF8.