Exclude TV's from Search not working.

33 Posts

pcmodem Reply #1, 16 years, 3 months ago

I am using AjaxSearch Version 1.9.0 and MODx Version 1.0.3.

I am trying to exclude email addresses from search and result pages. I have created a TV `person_to_email` and below is my code.

Snippet Call:

[!AjaxSearch? &showIntro=`0` &landingPage=`21` &moreResultsPage=`21` &showMoreResults=`1` &addJscript=`0` &whereSearch=`content:pagetitle,longtitle,description,alias,introtext,content|tv` &withTvs=`-:person_to_email` !]

Landing Page:

[!AjaxSearch? &ajaxSearch=`0` &showInputForm=`0` &whereSearch=`content:pagetitle,longtitle,description,alias,introtext,content|tv` &withTvs=`-:person_to_email`!]

Also, Is there a way to change the value of the Submit button from "Go!" to something else? I am formatting the Submit button to be a graphic with CSS and this works fine with FireFox. With Internet Explorer I am having the Go! text appear on top of the graphic. I don’t recall this being a problem before I upgraded to AS 1.9.0.

Here is my CSS code:

#ajaxSearch_submit {
	width:25px;
	height:24px;
	background:url(../images/but_search.png) no-repeat;
	border:0;
	cursor:pointer;
	overflow: hidden;
	text-indent:-5000px;
	margin:9px 0 0 2px;
	float: left;
}

Thanks,
Brian

1,717 Posts

coroico Reply #2, 16 years, 3 months ago

Exclude TV’s from Search not working.

You was right! And it was a tricky bug which give me trouble huh

Look at these demo pages "withTvs in" and "withTvs not int"

You could download the last release of AjaxSearch (#6971) with this bug fiexd on the download page here. Let me know if it’s ok now for you.
Just one remark: the "withTvs not in" option could generate an important select statement, so do some tests or prefer "withTvs" in option.

With Internet Explorer I am having the Go! text appear on top of the graphic. I don’t recall this being a problem before

I have the same differences on this demo page between IE and FF. But to be honest, I don’t know if it’s new or not. And as Css is not my cup of tea, I let the Css Guru find an explanation laugh

33 Posts

pcmodem Reply #3, 16 years, 3 months ago

I just upgraded to "ajaxsearch190-6976" and I am still having the same problem.

On a side note, I would suggest changing the version numbers between builds. For example Build 6970 is Version 1.9.0 and build 6976 is Version 1.9.1 or 1.9.0.1. Etc. This would help keep users straight.

1,717 Posts

coroico Reply #4, 16 years, 3 months ago

On a side note, I would suggest changing the version numbers between builds. For example Build 6970 is Version 1.9.0 and build 6976 is Version 1.9.1 or 1.9.0.1. Etc. This would help keep users straight.

I have used the Evo SVN changeset number to distinguish some builds before the delivery of Evo 1.0.4. The last build delivered with Evo 1.0.4 is the build #6976.
Issues are now registered in Jira. And the next release (probably 1.9.1) will provide corrections for some of these issues.
Nevertheless, as possible, for each issue, I provide on this board, the fix. But I will not create a new release of AjaxSearch at each fix.