Support/Comments for AjaxSearch

• • 
  • 1,717 Posts
  coroico Reply #391, 18 years, 8 months ago

  Thanks MotSmart for your encouragement. Do not hesitate to suggest some improvements if needed.
• • ☆ A M B ☆
  • 1,031 Posts
  Jako Reply #392, 18 years, 8 months ago

  Quote from: coroico at Jan 14, 2008, 03:29 PM

  
  

  ajaxSearch.php, Line 53ff
  ’utf8_general_ci’ => ’UTF-8’,
  should be added

  Here we speak about a mapping between the connexion charset of the database and the html page. We don’t speak of the collation. utf8 is enough.

  
  Without the line I’ve got this error:
  

  AjaxSearch: unknown database_connection_charset = utf8_general_ci
  Add the appropriate Html charset mapping in the ajaxSearch.php file

  
  BTW: It is (now) the latest 1.7 from the repository.
  
  
• • 
  • 1,717 Posts
  coroico Reply #393, 18 years, 8 months ago

  @Jako
  
  

  AjaxSearch: unknown database_connection_charset = utf8_general_ci
  Add the appropriate Html charset mapping in the ajaxSearch.php file

  Ok, in fact this message is quite ambiguous.
  It comes from the fact you have the value utf8_general_ci in your $database_connection_charset variable of your /manager/includes/config.inc.php file. It’s not due to the possible absence of the charset.
  For a site in utf-8 the appropriate charset is utf8. Set

  $database_connection_charset = 'utf8';

  in your manager/includes/config.inc.php file and it will run.
  
  More informations. See http://modxcms.com/forums/index.php/topic,21593.msg133273.html#msg133273
  on a near subject
  
  
• • 
  • 99 Posts
  traveller Reply #394, 18 years, 8 months ago

  Hi, coroico!
  
  1. Clear and incomprehensible problems and patches for AS for today are placed out in a thread http://modxcms.com/forums/index.php/topic,21568.msg133521.html#new, Reply #24.
  AKots has made patches and identifed problems for verson 1.7.
  The made updates will help to improve highlighting in the found documents for your site also, it’s probably. I have checked up highlighting on my local Web-server (UTF8). It’s OK.
  
  2. It decided to leave a file of russification AS which you mentioned in Zip-archive.
  
  admin note: edited to make the link to the topic work
• • ☆ A M B ☆
  • 1,031 Posts
  Jako Reply #395, 18 years, 8 months ago

  Quote from: coroico at Jan 15, 2008, 06:24 AM

  
  Set

  $database_connection_charset = 'utf8';

  in your manager/includes/config.inc.php file and it will run.

  Thanks Now the search works in Firefox.
  
  In IE(7?) the version checking of AjaxSearch.js gives an error and after searching the error-page is displayed (page 0).
  
  In Safari 3.0 Mac (no Beta) the utf8-chars were not displayed as utf8.
  
  IMHO a bit too much bugs for a non beta.
  
  Regards
  Jako
  
  
• • MODX Staff
  • 12,272 Posts
  Ryan Thrash Reply #396, 18 years, 8 months ago

  I believe the Safari problem is in fact a bug in Safari.
  Ryan Thrash, MODX Co-Founder
  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
• • ☆ A M B ☆
  • 1,031 Posts
  Jako Reply #397, 18 years, 8 months ago

  Quote from: rthrash at Jan 15, 2008, 12:59 PM

  
  I believe the Safari problem is in fact a bug in Safari.
  

  Maybe, but i’ve had no problems with the utf8-patched 1.6.
  
• • 
  • 1,717 Posts
  coroico Reply #398, 18 years, 8 months ago

  @jako
  

  In IE(7?) the version checking of AjaxSearch.js gives an error and after searching the error-page is displayed (page 0).

  I have done a javascript analyse of http://www.partout.info/90.html
  For that I have installed companion.js a javascript debugger for IE. This trouble don’t occur on Firefox.
  
  And I found the two following classical javascript errors on your page :

  This object doesn't manage this property or method

  (translation of the french message)
  
  - line 192 - slimbox.js : window.addEvent(’domready’, Lightbox.init.bind(Lightbox));
  and then
  - line 34 - 90.html : version = ’1.7’;
  
  Regarding the second error I spend some time but I found a conflict between the javascript variable version and :
  

  <meta name="version" content="MODx 0.9.6.1 (rev 3118)" />

  
  
  I have dowloaded your page with all the js & css files, and when I suppress this line in the code of your html page, the version-checking is not activated
  
  This explain why I haven’t this issue on my site (I haven’t a meta with a name version).
  Suppress this line on your site, clean the buffer of your browser and retest. Thanks to confirm my diagnostic.
  
  So as the simple solution to avoid this kind of trouble is that I rename the variable version by as_version.
  For the next MODx 0.9.6.2, I will deliver tomorrow a new package 1.7.0.1 with the following corrections :
  
  In ajaxSearch.js : return instead of exit (line 40)
  In snippet.ajaxSearch.inc.php, Line 313: suppression of the tab at the end of the line
  In both files : use of as_version instead of version
  + the typo corrected in the german file
  
  Regarding Safari, as I do my tests on XP and as Safari 3.0 is always a Beta release, i prefer await a stable version.
  
• • 
  • 99 Posts
  traveller Reply #399, 18 years, 8 months ago

  Hi coroico.
  
  I have corrected my #411 Reply on this page.
• • ☆ A M B ☆
  • 1,031 Posts
  Jako Reply #400, 18 years, 8 months ago

  Thanks for debugging the code. The ’<meta name="version" …’ is displayed by the ’MetaTags’ snippet.
  
  I’ll try to get some more information for the Safari issue.

This discussion is closed to further replies. Keep calm and carry on.