Support/Comments for AjaxSearch

MODX Staff
10,725 Posts

opengeek Reply #281, 19 years ago

Are you using SEOStrict plugin? It seems that your results page is specified as index.php?id=1 and I think it’s doing a 301 to the site_url and losing the request being POSTed to the URL.

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

MODX Staff
2,502 Posts

Jay Gilmore Reply #282, 19 years ago

Quote from: OpenGeek at Sep 27, 2007, 10:58 AM

Are you using SEOStrict plugin? It seems that your results page is specified as index.php?id=1 and I think it’s doing a 301 to the site_url and losing the request being POSTed to the URL.

No, but I think I know what is going on though. The domain is not a subdirectory but an account directory on my reseller account so Apache is 301ing the account dir onto the smashingredhost.com domain. It seems to be doing the same thing with the ip address with the account directory as well so I assume that it is being mapped as well. I don’t know how to address this until I transfer the domain so I will just leave it until I go live.

The only thing is that fURLs work okay so I wonder why the POST request won’t get forwarded through the 301 as well?

Alas, I will just wait and see.

Thanks Jason,

Jay

Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub

MODX Staff
10,725 Posts

opengeek Reply #283, 19 years ago

Because, a redirect always sends a new REQUEST altogether. Unless you specifically save this data to session and reload it after the redirect, you will not have any of the original POST data. If you were using $modx->sendForward() then you would still have the REQUEST data, but the URL would remain the same as requested. See the dilemma?

Jason Coward
Chief Architect @ MODX
http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek

MODX Staff
2,502 Posts

Jay Gilmore Reply #284, 19 years ago

Ahh,

Thanks. Learn something new everyday. I will assume that all will be fine once I am using DNS based addresses with no Apache redirects.

As always, all the best,

Jay

Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub

14 Posts

netpuppy Reply #285, 19 years ago

I was wondering if someone could tell me what mootools functions ajaxsearch uses. The mootools 1.0 that is included in the manager throws an error with Internet Explorer over an https connection stating the there is mixed content on the page. I want to update to mootools 1.1 as this version has fixed the bug but I do not want to make the mootools.js any larger than it needs to be by including unnecessary functions.

34 Posts

Caledai Reply #286, 18 years, 11 months ago

Has there been any solution to AjaxSearch on MODx 0.9.6 [Upgrade & Clean Install] when called from the default MODxHost template, in regards to a search being successful only if a front end user is not logged in?

I have tried playing around with [[...]] [!...!] Cached/Uncached to no avail.
I manually installed AjaxSearch 1.6 over the top, and also copied the default MODxHOST template from a clean install over to no avail.

I have this issue on several sites I am using as an intranet - and if logged in users cannot do a search, it kind of defeats the purpose of having a site in the first place.

This problem has only existed since I upgraded from 0.9.5 to 0.9.6 to bring all the sites I manage into line, but also exists on a clean install of 0.9.6

203 Posts

knightknight Reply #287, 18 years, 11 months ago

How do I replace the Ajax Search button using CSS.

I’ve tried using the #ajaxSearch_submit { background: url(../images/search.gif) no-repeat; } which adds in the search.gif, but still overlays the Go text. I’ve managed to edit out the Go text in english.inc.php but that not great when you switch off CSS.

I’m a bit stuck any help?

MODX Staff
2,502 Posts

Jay Gilmore Reply #288, 18 years, 11 months ago

@knightknight

In your css #ajaxSearch_submit rule:

text-indent:-10000px;

Another option is to change the input submit to a button in the template. This would allow better styling anyway and really should be used instead anyway.

Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub

203 Posts

knightknight Reply #289, 18 years, 11 months ago

@smashingred

worked like a charm, would never have thought of that!

1,717 Posts

coroico Reply #290, 18 years, 11 months ago

I use AjaxSearch 1.6 with the option &ajaxSearch=`1` with IE 6.0 And I have the two following troubles :

1/ With IE, unnecessary lines are added. These lines disrupt the css display by pushing down the input form

The build of ajaxSearch_form by the snippet with IE6.0 (and probably IE 7.0) generate a blank line which push down the input form.
Here is the generated code under IE6:

<div id="header">
  
		
		<form id="ajaxSearch_form" action="index.php?id=1" method="post">
			<label for="ajaxSearch_input">
				<input id="ajaxSearch_input" type="text" name="search" value="Saisissez votre recherche ici..." onfocus="this.value=(this.value=='Saisissez votre recherche ici...')? '' : this.value ;" />
			</label>
			<label for="ajaxSearch_submit">
				<input id="ajaxSearch_submit" type="submit" name="sub" value="rechercher!" />
			</label>
		</form>
		
		<div id="ajaxSearch_output" style="opacity:0;"> </div>

An another blank line is added between </form> and <div id="ajaxSearch_output" style="opacity:0;"> </div>

These 2 blank lines aren’t generated under Firefox and the input form is at a correct place.

Does anybody know why these lines are generated under IE.
I read the snippet code and I do not understand why these lines are generated under IE.

2/ Opaque color output results window is always visible with IE 6.0 even without results

With IE, If the div block ajaxSearch_output has an opaque color, then it is visible.
This is due the fact that the style order "opacity:0;"" doesn’t work with IE.
The correct style for IE6 should be "filter:alpha(opacity=0);""
Does anybody know how i could specify in the style order the difference between IE and Firefox.

Does anybody use AjaxSearch with the true AjaxSearch mode with an opaque color output results window

Thanks for your answers