AjaxSearch Upgrade Issues with MODx upgrades, more of a rant.

Ok guys, I love what you do. MODx is an awesome CMS.

However, this crap that happened with ajaxsearch from 1.0.3 and now to 1.0.4 is ridiculous.

Everysite I have that used ajaxsearch requires CSS edits at the least because of markup change, and usually a snippet call updated because the AjaxSearch snippet changed a parameter from jScript to jscript.

Now I’m just trying to get some of my sites to work again, but that’s my problem. Lets stay consistent some if at all possible is all I’m saying or put some thought into backwards compatibility.

You’re not forced to update AjaxSearch...

I respect your opinion, however it’s been a long day and I’ll regret this later I’m sure.

So you’re saying I should first some how know they’ve changed things, and that they’ll potentially break current snippet functionality and not be feature or security updates. Then if I have managed to discern this, I should remove all associated files from the MODx System upgrade that was suposed to fix a XSS vulnerability that we’ve all been advised to install. And then yes after all this I can uncheck "Upgrade AjaxSearch".

Surely you can see that this possibly has merit. Yes I am calling you Sherly.

I realise that it’s no solution to fixing the problem that lies on the table already.

What else do you expect people to respond to a topic like this?


Edit: perhaps as a help migrating, can this topic help you? http://modxcms.com/forums/index.php/topic,49555.msg289027.html#msg289027

Nothing more than to get it off my chest. I feel better allready

Quote from: neon_eddy at Jun 29, 2010, 03:35 PM

I respect your opinion, however it’s been a long day and I’ll regret this later I’m sure.

So you’re saying I should first some how know they’ve changed things, and that they’ll potentially break current snippet functionality and not be feature or security updates. Then if I have managed to discern this, I should remove all associated files from the MODx System upgrade that was suposed to fix a XSS vulnerability that we’ve all been advised to install. And then yes after all this I can uncheck "Upgrade AjaxSearch".

Surely you can see that this possibly has merit. Yes I am calling you Sherly.

Absolutely a valid complaint, IMHO. Still, remember what you paid for both MODx and AjaxSearch.

I share quite a bit of the same feelings, having spent about half a day trying to migrate my search solution to the 1.9.0 version (that comes with modx 1.0.4)

Normally I try to wait 24 hours if something makes me angry, but most of the anger has now worn off so ...

I respect the amount fine grained modularity that is in the ajaxsearch solution (which has lots of and lots of placeholders), maybe a little overdone for my taste but an extra bit flexibility never hurt ..

What is missing is an overview, the cheat sheet and docs for instance don’ t clarify how to achieve a simple non-ajax, non-grouped result listing ...

I ll try and have a look at it, some other time, for now i just choose to stick with ajaxsearch 1.8.5, certainly for upgrades of existing sites.. so ’ll just upgrade to modx 1.0.3 and then to modx 1.0.4 but for that upgrade i ll make sure not to install the new ajaxsearch

Hi All

Just tried to do the upgrade to 1.0.4 and then when I got the Ajax errors, I found this!!

OK,so just in the processing of reverting back to backed up site (with fingers, toes and many other appendages crossed) and the obvious questions are:

1. Will not selecting Ajax during the upgrade selection mean the error WILL NOT re-appear?
2. If I do upgrade Ajax, what do I do to fix the error (please, bear in mind I am a mere beginner at PHP so go gentle! )

Thanks
Daz

Hi sumodaz, maybe my answer comes too late ..

but .. what you also could do is leave it MODx 1.0.4 ... and downgrade ajaxsearch ... that’s right ...
do to this .. you delete (well perhaps backup first) everything in the assets/snippets/AjaxSearch folder (including all the folders and stuff. )
Download the 1.8.5 version of AjaxSearch (double check , but should be this url : http://modxcms.com/extras/package/8?version=1193 )

unpack the 1.8.5 version :
copy the files in the right location ( assets/snippets/AjaxSearch )

then in the modx manager : go to elements > manage elements > snippets >> edit ajaxsearch snippet ...
You will see that it has version 1.9.0 ...
now, in the unpacked 1.8.5 version of the snippet you should find a file that has ’snippet’ in it’s name ; or look in the documentation in the unpacked files, because there is one piece of code that you will need to copy
paste into the snippet code in the modx manager

If you have done that, don’ t forget to edit the description of the snippet as well because it is now v1.8.5 and not v1.9.0 anymore ... save the snippet

@Bartnelis

Rather to promote a downgrade to AjaxSearch 1.8.5, it could be better to explain which issues you meet with AjaxSearch 1.9.0 !

Your first post is not very precise. Thanks to provide more informations, if you want a relevant help.

I just don’t succeed at having it a perform a regular results output instead of a groupedresults output .. It seems the pagination subtemplating has changed and i’m a bit at a loss...

wonder whether it really pays to upgrade ...