Support/Comments for AjaxSearch

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[atma]

If you had problems with search not latin symbols (cyrillic In my case), offer my decision.
Replace in file AjaxSearch.js line ~111:

Code:

search: s,

with

Code:

search: unescape( encodeURIComponent( s ) ),

and line ~140:

Code:

    $('current-search-results').setHTML(decodeURIComponent(request));

with

Code:

    $('current-search-results').setHTML(decodeURIComponent( escape( request ) ));

Only it works in Firefox 1.5, Internet Explorer 6.0.2900.2180, Opera 9.0.8502, Camino 1.0.2, Safari 2.0.4

[rthrash]

I'm assuming it also works in Firefox 2.0.x and IE 7, too?

[atma]

I'm assuming it also works in Firefox 2.0.x and IE 7, too?

Yes, of course
Works in Firefox 1.5, Internet Explorer 6.0.2900.2180, Opera 9.0.8502, Camino 1.0.2, Safari 2.0.4 and higher.

[FuryDE]

Hello.

I got a little (hope so) problem with this snippet. I'm using modX 0.9.5 and updated AjaxSearch to the current version 1.6.

I added

Code:

[!AjaxSearch? &ajaxSearch=`0` &AS_landing=`30` &AS_showResults=`0`!]

to my template and on page ID 30 I added

Code:

[!AjaxSearch? &AS_showResults=`1` &AS_showForm=`0` &showMoreResults=`1`!]

to the content. I intentionally deactivated ajaxSearch because it's my first steps with this snippet. So now to my problem: The search does not find any results. I have tried many different searches but they all lead to nothing. At last, I think that it finds nothing for nothing is outpu. The source just shows a

Code:

<div id="ajaxSearch_output" style="opacity:0;"> </div>

Well, that opacity:0 is interesting, but this is not the problem yet.

Can anybody help me here? BTW: all pages of my site are currently set to be "searchable".

Thanks and greetings from the "Bierstadt Einbeck" in Germany
Martin

[nos]

Always there is the problem with AS and special chars - utf-8 (atma's patch doesn't work for me)

is it AS or the server config?

my personal dilemma is that my knowledge of IT at this time does not allow to move the AS coders or my hoster to act.

With a search the PHP request header allows utf8 und ISO-8859-1. The response header only delivers ISO-8859-1.  DB config is like this:
collation_connection     utf8_general_ci     ok
collation_database     utf8_general_ci     ok
collation_server     latin1_swedish_ci   
I'm not allowed to change server configs. The Hoster surely doesn't want to  ("latin1_swedish_ci is a standard config in europe." he says).

One could say it is better to search the way FlexSearch for example does (that meens to change AS for more flexibility with hosters).

By the way: With &ajaxSearch=`0` search finds but is case sensitiv i. e. "über" doesn't find "Über" (in my 0.9.6 install).
Though modX is mostly an ingenious tool in my eyes (3. install), ...

[atma]

Always there is the problem with AS and special chars - utf-8 (atma's patch doesn't work for me)

is it AS or the server config?

Maybe you help this:
add in file AjaxSearch.inc.php after

Code:

$selected = mysql_select_db($database, $db) or die ("Cannot select database (connectForAjax)");

similar code (this in my case)

Code:

mysql_query("SET CHARACTER SET utf8;");
         mysql_query("SET NAMES 'utf8';");
         mysql_query("SET character_set_results = 'utf8';");
         mysql_query("SET collation_connection = 'utf8_general_ci';");

[OpenGeek]

Good call atma.  I thought this had been updated, but apparently not.  You only need the first call BTW:

Code:

mysql_query("SET CHARACTER SET utf8;");

See more information regarding this at http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html; and in particular, this section describes how SET CHARACTER SET works...

SET CHARACTER SET is similar to SET NAMES but sets character_set_connection and collation_connection to character_set_database and collation_database. A SET CHARACTER SET x statement is equivalent to these three statements:

SET character_set_client = x;
SET character_set_results = x;
SET collation_connection = @@collation_database;

I'll make sure and get AjaxSearch updated and into the 0.9.6.1 release.

[MotSmart]

This issue will be lost here, anybody made a bug/suggest yet?

[MEGU]

Dear All,

I thank your great work, Ajaxserch.

> Dear MotSmart.
I have also same trouble with strange black box under the search box.
I think that Ajaxsearch do not work with to that state.
I checked about this trouble in detail.
The result, AjaxSearch has some trouble with CACHE, I think.

I tried the the following:

First, create a simple document like the following.

Code:

<html>
<head>
</head>
<body>
<div id="search">[!AjaxSearch? ajaxSearch=`1` &addJscript=`1`!]</div>
</body>
</html>

The template of document is blank.
Document cache is "YES".

Access to the page which created the above.
At first, Ajaxsearch would work normally.

And again, access to  this page (not REROAD).
(The word "Search here..." will appear in textbox).

In this situation, AjaxSearch do not work.

Next, Clear cache in the manager.
Again, access to this page.
AjaxSearch works.

The same phenomenon is caused in the sample web site.
Then, the strange black box will appear under the search box with IE(6).

Sincerely yours,
---*---*---*---*---*---
P.S.
If document cache is "NO", this issue would not be caused.

[MotSmart]

Combination of ATMA and MEGU solutions worked like a charm for me... many thanks

[nos]

@ atma and the other AS friends

sorry, both of your suggestions don't work for me, not even in combination. Does that mean, the collation_server has to be utf8 too? (see Reply #214) or what could have been run the wrong way?

(Additional info: db fields are set to utf8 too, Editor is set to raw entity coding, modx is set to utf-8 coding, pages are ok in look and html's show original chars i.e. ä)

Looking via phpMyAdmin into a db field the word "Geräte" is written "Geräte" on the (utf-8 coded) page, in html source it reads there "Ger%C3%83%C2%A4te".

So, if I search for "Geräte" AS will find (no highlight in the page and "Geräte" in the search term message).

[atma]

I'm not allowed to change server configs. The Hoster surely doesn't want to  ("latin1_swedish_ci is a standard config in europe." he says).

but you have permission to phpMyAdmin... At the main page of phpMyAdmin this field are readonly?

After you will create (edit) page MODx and will receive the same result in phpMyAdmin, AjaxSearch too will earn normally... I hope 

So, if I search for "Geräte" AS will find (no highlight in the page and "Geräte" in the search term message).

What about CSS:
.AS_ajax_extract{xxx;}
.AS_ajax_highlight{xxx};
.ajaxSearch_highlight {xxx;}
.ajaxSearch_highlight1 {xxx;}
etc?

[nos]

thanks for reply atma,
I can not reach this page in phpMyAdmin. I've got three possible dbs from the hoster - creating a new db is only possible from a confixx interface. phpMyAdmin states: creating new db - no rights, so it's readonly - yes.

sql statement:
SHOW VARIABLES LIKE 'character_set%';
SHOW VARIABLES LIKE 'collation%';
results in
collation_connection     utf8_general_ci
collation_database    utf8_general_ci
collation_server    latin1_swedish_ci  <--- I can not change
(MySQL 5.0.32-Debian_7etch1-log)

as for AS highligting css): search without special chars is running fine.

[OpenGeek]

@nos: you do not need to change the server value.  You just need utf8 as the database_connection_charset value so that the MODx db connection knows what charset your database (and the tables in it) actually has.  That's what SET CHARACTER SET statement does; it switches the MySQL client connection to the proper charset/collation for whatever queries follow it.

[nos]

@opengeek
I agree and see it this way too. So why AS doesn't work accordingly? I did this changes dicussed here (see replies below) but nothing changes in AS output.