Hinterlasse einen Kommentar

1. Marc Cathomen sagt:

   30. Juli 2009 um 18:39

   We would like to use your plugin on a new wp-site using the latest atahualpa theme. seems not to work. any hints?
   thx marc

   Auf diesen Kommentar antworten
   • Bernhard sagt:

     30. Juli 2009 um 19:08

     Hi Marc,

     you are just a few hours to quick. I was searching for a diffrent theme for this blog and found out, that many themes doesn’t set the id attribute for the input field. I just installed the Atahualpa 3.4.1 theme to test it. This theme also uses only the name attribute.
     So after realising that many themes doesn’t have the needed id attribute I decided to add another option to be able to select the field by id or by name (or even another CSS selector).

     I have to test the new option with prototype and jQuery but I am pretty sure, that I will release the new version by tomorrow (maybe today).

     I hope this willl help not only you. Do you have any other ideas of how to improve the plugin?

     Bernhard

     Auf diesen Kommentar antworten
     • Marc Cathomen sagt:

       31. Juli 2009 um 08:00

       Hello Bernhard
       everthing works perfectly now with tha Atahualpa 3.4.1 theme!
       thank you very much for the great support!

       what i did:
       - updated the plugin to 1.6.1.
       in the plugin configuration:
       - changed the selectortype to name
       - changed the javascript Framework to jQuery

       that’s it. now it works

       Auf diesen Kommentar antworten
2. Hans sagt:

   3. August 2009 um 09:22

   I have some weird behaviour when searching for either “di” or “no” (without the quotes.)

   It then parses the style of under wrong.

   If you want to reproduce try searching for: (di)splay or no(ne)on my website.

   Auf diesen Kommentar antworten
   • Bernhard sagt:

     3. August 2009 um 11:30

     Hi Hans,

     I could reproduce the problem. I use a default jQuery plugin for the autocomplete feature. This plugin doesn’t provides the feature of an onclick handler so I have to add the link the the article in a hidden span. To make it hidden I used inline formating with display: none. But the jQuery plugin seems to destroy HTML-Markup when hightlighting the found words.

     So I have to either find a new jQuery Plugin or I have to use single character markups and a diffrent CSS Layout for the results.

     I think I can give you an updated version this evening which than should work with jQuery as good as with scriptaculous. Until than you might use scriptaculous to avoid this problem.

     Bernhard

     Auf diesen Kommentar antworten
     • Hans sagt:

       4. August 2009 um 13:46

       Hi Bernhard,

       version 1.7 fixed the bug I mentioned. Thanks for the support!

       Auf diesen Kommentar antworten
3. Daniel sagt:

   12. August 2009 um 11:42

   In v1.8 I still get “Warning: cannot yet handle MBCS in html_entity_decode()! in /htdocs/wp-content/plugins/kau-boys-autocompleter/autocompleter_results.php on line 72″

   It was working great up until v1.5 and then it has stopped. Tried uninstalling / reinstalling – any further ideas?

   Auf diesen Kommentar antworten
   • Bernhard sagt:

     12. August 2009 um 17:03

     Hi Daniel,

     I search the web for your problem and it is a bug in PHP 4 (http://bugs.php.net/bug.php?id=27626). I use html_entity_decode to convert all characters to non-entities to avoid destroying them when limiting the title/content length.

     But as PHP 4 (pre 4.3.3) lacks a full support of UTF-8 it might be a prblem with the encoding. So the first thing you should try is to go to the settings page and change the multibyte encoding to ISO-8859-1.

     If that doesn’t work, try to replace line 72 in autocompleter_results.php. To do so, navigate to Plugins->Installed and click edit on the plugin. From the list at the right choose the autocompleter_results.php. Then replace this line:

     $str = html_entity_decode(trim($str), ENT_NOQUOTES, $encoding);

     with this line:

     $str = utf8_encode(html_entity_decode(trim($str)));

     As I don’t have a running Server with PHP4 I can’t test it myself right now.

     Bernhard

     Auf diesen Kommentar antworten
     • Daniel sagt:

       29. September 2009 um 13:11

       Thanks Bernhard, all is now working.

       Many thanks again.

       Auf diesen Kommentar antworten
4. Fiz sagt:

   27. November 2009 um 18:48

   Hi and thanks for your very beautiful plugin. One only thing about styling of autocompleter.css -> ac_result class:
   * add parameter left:-9999px; to disappear its border (if added) to the bottom of the page
   * add !important to width

   Bye!

   Auf diesen Kommentar antworten
5. Sascha sagt:

   30. Januar 2010 um 13:36

   Unfortunately it does not work while Relevanssi is activated! I’s a pitty. Bothe plugins are valuable and nice! However, I will have to go for nice search results rather than for autocomplete…

   Anyway thanks for this nice plugin!

   Auf diesen Kommentar antworten
   • Bernhard sagt:

     30. Januar 2010 um 15:57

     Hi Sacha,

     I checked out the relevanssi plugin and found out that this plugin sets some filters that affects other plugins for searches. I now added some code to make my plugin working with the relevanssi plugin enabled.

     Auf diesen Kommentar antworten
     • Sascha sagt:

       31. Januar 2010 um 17:24

       Hi Bernhard!
       Your update just worked fine! Really smooth. Now everything seems OK. Just had to donate some money for the super quick service!
       Thanks and best regards Sascha

       Auf diesen Kommentar antworten
6. Sascha Postner : Waidwerk : Blog über Kommunikation, Webstandards und Public Relations» Blogarchiv » Wordpress Suche verbessern sagt:

   2. Februar 2010 um 23:16

   [...] sinnvoll sofort den ersten Treffer zu selektieren) ist es ein spitzen Plugin. Außerdem sollte noch der tolle Einsatz des Autoren betont werden und dessen schnelle [...]

   Auf diesen Kommentar antworten