Support/Comments for AjaxSearch

786 Posts

kjaebker Reply #131, 19 years, 7 months ago

pr0ph3t,
The altest version of AjaxSearch, found here: http://modxcms.com/forums/index.php/topic,11228.0.html

does support language files for all of the default messages. I don’t think it has been translated by anyone yet, but would be happy to include the translations with it when people complete them.

15 Posts

TDRWH Reply #132, 19 years, 7 months ago

Quote from: kylej at Feb 24, 2007, 12:13 PM

I don’t think it has been translated by anyone yet, but would be happy to include the translations with it when people complete them.

Well then, here is my German language file for AjaxSearch. I hope it’s alright, ... never done a ’highly official’ translation before

Bye,

TDRWH

144 Posts

andrazk Reply #133, 19 years, 7 months ago

Here is a translation for slovenian language (AS version 1.5).

Another idea: when you trigger a search that has only results in pagetitle (or fields other than ’content’), no summary excerpt is displayed.
In this case maybe the first N characters could be shown... even if they do not contain the search string.

It would sure look prettier. wink

160 Posts

hald Reply #134, 19 years, 6 months ago

Kyle; I think i posted this question in the wrong forum a while ago - Mark K is going to wonder ?
What i wanted to know is; the readme for version 1.6 does not mention index-ajax.php, nor was it in the update zip. Is it still needed?

Thanks,
Hal D

"Today’s headlines are nothing more than whispers of history"

160 Posts

hald Reply #135, 19 years, 6 months ago

I’m having trouble getting AjaxSearch to work.
This is the call in the template: [!AjaxSearch? &AS_showForm]=`1`!]
The results are as follows; In IE7 it sort of works, in fireFox 2 not at all, in Opera it sort of works. (see screen grabs)
I’v attached the FF error console (MooTools.js IS loaded as well as ajaxsearch.js)
I’ve checked all the options in FF tools and there is nothing I can see keeping it from working- javascript is enabled. I’m stuck as to how to proceed.
Thanks for any help,
HalD

"Today’s headlines are nothing more than whispers of history"

160 Posts

hald Reply #136, 19 years, 6 months ago

Kyle: I was reading some old posts in the ajax forum thread and it looks like the problem I’m having is caused by Quick-Edit. When it is logged off everything works ok. I’m using MODx v 0.9.6-rc1 and I thought the Quick-Edit problem was supposed to have been corrected in that version, so I didn’t think of it right away until I read a post by SirLancelot who was having the same problem. Can anything be done to fix this, besides logging out of QE?
BTW, QE is calling Mootools.js and not prototype/scriptolicous. Something is in conflict.
Cheers,
Hal D

"Today’s headlines are nothing more than whispers of history"

160 Posts

hald Reply #137, 19 years, 6 months ago

Logging off QE solved the problem of search not working in FF, and judicious manipulation of the CSS got the search box looking pretty much the same in FF2, Opera9 and IE7, but there are still two problems that I can’t get a handle on;
1) the drop-down results box is transparent and other items below it show through in all 3, and
2) still have a portion of the results window that shows all the time in IE which covers items below it.
Thanks,
HalD

"Today’s headlines are nothing more than whispers of history"

144 Posts

andrazk Reply #138, 19 years, 6 months ago

How difficult would be to implement searching just in a part of the document tree?
Say, Search only in children of document with parentId=`NN`, N levels down or all children?

Are there any plans to implement that? Otherwise I’m going to do it.

786 Posts

kjaebker Reply #139, 19 years, 6 months ago

@andrazk: that probably would not be that hard to implement, I would love to see your suggestions.

@hald: the issues with quickedit have been fixed in the latest version of 0.9.6 (from svn), I will try to get it all packaged up for download soon.

144 Posts

andrazk Reply #140, 19 years, 6 months ago

Quote from: kylej at Mar 20, 2007, 07:12 AM

@andrazk: that probably would not be that hard to implement, I would love to see your suggestions.

Well, instead of searching sitewide I’d like to narrow the search to the documents in a specified branch of the document tree.
That’s why I’d add a parameter, say "topNodeId" or "parentId", defining the top document for the search. This would mean that only it’s children would be searched and their respective TVs.
Considering the demo site included in the instlalation, parentId=`0` would search the whole document tree, parentId=`2` would search only the blog, parentId=`15` would search only the MODx Features, and so on.
Of course, you could specify many "parents" as in parentId=`2,4,3`

Next parameter is "includeParent" (boolean), which is rather selfdescribing.

Now, another parameter would be "depth" or "levels". If specified, only N levels of children would be searched. Level=`1` would search only the direct children of the parent document.
Level=`2` would include the children’s children also. Level=`0` would be a pretty useless setting, with or without includeParent set to true.

A wicked idea is maybe a parameter "lastChildOnly", which would search only the documents that have no children. In a structure

news (1)
  category 1 (2)
     article 1 (6)
     article 2 (7)
  category 2 (3)
     subcategory 1 (4)
       article 3 (8)
       article 4 (9)
     subcategory 2 (5)
       article 5 (10)
     article 6 (11)
     article 7 (12)

it would search only the articles (6,7,8,9,10,11,12), no other pages.

If this is too strict, add a parameter includeDocId=`3,4`, which would add individual pages to the search. As a counter-parameter, excludeDocId=`8,7` would exclude the document with Id = 7 and Id = 8, even if it is one of the articles.

Another feature, exclude a whole tree branch with excludeParentId=`4` (which in our example would exclude whole "subcategory 1").

Parameter consideration sequence:
1 - includeParent
2 - collect all children of parentId
3 - add includeDocId
4 - remove excludeDocId
5 - remove excludeParentId

All parameters take multiple ids.

Examples

[!AjaxSearch? &parentId=`2,3` &includeParent=`1`!] is equal to [!AjaxSearch? &parentId=`1` &includeParent=`0`!] 

[!AjaxSearch? &parentId=`2,3` &includeParent=`0`!] would search all documents where Id > 3

[!AjaxSearch? &parentId=`3`  &excludeDocId=`11` &lastChildOnly=`1` !] would search Id in [6,7,8,9,10,12]

[!AjaxSearch? &parentId=`3`  &excludeDocId=`11` &excludeParentId=`5` !] would search Id in [4,5,8,9,12]

[!AjaxSearch? &parentId=`3`  &excludeDocId=`11` &excludeParentId=`5` &includeParent=`1` !] would search Id in [3,4,8,9,12]

Anything else? grin

If help needed, tell me, glad to code.