Search results page - submit button & "contact us" behaviour

[MNWF]

I'm stumped (and so is Actinic tech support right now) over a variation of an old chestnut. I've searched through all the relevant threads, but there's still no solution, and I've run out of ideas. This is a summary of the problem:-

- this is a new site, about to launch, developed with v7.0.5 Catalog

- the development site was built at a domain in the form of "www.dev.mydomain.co.uk". The live environment is at "www.mydomain.co.uk".

- both sites/domains share a 1&1 host, in /dev and /live directories respectively.

- After backing up the finished dev site, I modified its network settings to create the live site and uploaded it to the live webspace/domain. Network settings are:-

HTTP Proxy: direct

FTP Proxy: direct

FTP Server: www.mydomain.co.uk
User: *******
Password: ********
Using passive FTP transfers.
Path to the CGI-BIN Directory:
/live/cgi/
Path from the CGI-BIN Directory to the Catalog Directory:
/live/acatalog/

Catalog URL: http://www.mydomain.co.uk/acatalog/

Codebase: ./

CGI-BIN URL: http://www.mydomain.co.uk/cgi/
Perl Location: /usr/bin/perl
CGI Script Extension: .pl
Path from the CGI-BIN Directory to the Catalog Directory (as viewed from the CGI Script):
../acatalog/
CGI Script ID: 200

Mail Server: auth.smtp.oneandone.co.uk
Email Address: sales@mydomain.co.uk

- The live site works fine in every respect other than certain behaviour in the search results page. The "contact us" link on this page shows the URL of www.dev.mydomain... instead of www.mydomain... . A further from the search results page uses the form action of www.dev.mydomain... instead of www.mydomain...too.

- The search results page is using Act_Primary. Even when I hard code the correct full absolute URL for the "contact us" button in this template (instead of using NAVBMAILLINK), the URL on the search results page itself remains www.dev... !

- I've changed the script ID for the live site to a different one to the dev site and it makes no difference.

- I've done countless full refreshes & purges and it's made no difference.

- I've tried clearing cookies, and have used a fresh PC that's never been on the dev site before (in case cookies / sessions are the source of the problem) and that makes no difference either.

Can anyone please help? I need the site to be working properly tomorrow for its "official" launch, and time's running out...

Thanks,

Mark

[wjcampbe]

On my 1 & 1 site I have set up the domain root home directory as my equivalent of your /live/

I then have

Catalog URL http://www.mydomain.co.uk/acatalog/
CGI-BIN URL http://www.mydomain.co.uk/cgi-bin/
Path to CGI-BIN /live/cgi/
Path from cgi-bin to catalog ../acatalog/

The last line quoted is the one I would look at

[MNWF]

Hi Bill, thanks for taking the trouble to look at this. I've tried the CGI-BIN to path set to ../catalog/ as in your config, but to no avail.

I just can't see where the www.dev.mydomain.. link and form actions are being picked up from - for example, the search results page is built from the same Act_Primary as the rest of the site, and Act_Primary has the correct URL for the "contact us" link explicitly hardcoded!

I've noticed that the view basket and checkout links from the search results page are also incorrect (in the same way):-

http://www.dev.mydomain.co.uk/cgi/ca000200.pl?ACTION=SHOWCART

and

http://www.dev.mydomain.co.uk/cgi/os000200.pl?ACTION=Start&BASE=http://www.mydomain.co.uk/acatalog/

I've also noticed that the source for the generated search result page has this:-

<BASE HREF="http://www.mydomain.co.uk/acatalog/">

whereas the source for other pages built using Act_Primary has:-

<Actinic:BASEHREF VALUE="http://www.mydomain.co.uk/acatalog/"/>

Is that difference to be expected?

Grateful for any other thoughts.

Mark

[wjcampbe]

Well, now that you have given away the URL, I just had a navigate around, and I see no problem. Search, Contact Us, View cart - all lead to the correct pages - no errors. Tried quicksearch then reached the full search - all working fine.

[wjcampbe]

You know, the minute I sent that response - it stopped working.... now getting a 404 from search.

[MNWF]

Really!? - sounds like something being retained by the browser? But I've cleared cookies, and even tried a different PC that's not seen the dev or live site before to my knowledge, and have still got the problem.

The 404 errors you saw are because I was carrying out major surgery! When the keyhole surgery doesn't work, unfortunately its tempting to get the hacksaw out!

I'll finish refreshing the site again, maybe install a completely new browser to test it.

Fingers crossed...

[MNWF]

No, a completely fresh PC & browser still gets the wrong link URLs and form actions on the search results page...

Bill, I suspect when you scooted around the site you probably saw that the links all worked from other pages, but not in fact from the search results page(?)

I'll have to give it a fresh look tomorrow morning.

[wjcampbe]

I've found your problem - here are the sources of your template files

Brochure
<Actinic:TEMPLATE type="begin" filename="C:\Program Files\Actinic v7\Sites\Site1\Act_BrochurePrimary_index.html"/>

Shop
<Actinic:TEMPLATE type="begin" filename="C:\Program Files\Actinic v7\Sites\Site1\Act_Primary.html"/>

Search
<Actinic:TEMPLATE type="begin" filename="C:\Program Files\Actinic v7\Sites\Site2\Act_Primary.html"/>

Now all you need to know is where to change search to use the site1 Act_Primary and problem solved - if I find it I will amend this post.

[MNWF]

Bill, many thanks indeed for identifying that Search Results is drawing on a template from a different site/path. That's narrowed the hunt enormously.

I can't see why or where this is being picked up though - will keep searching for it.

Mark

[1stweb]

What was the solution??

Hi,

I am having a similar issue and would like to know what the solution was.

[wjcampbe]

Mark,

are you talking about the honeyfarm site? I just tried a search there and got this javascript error

Error: [Exception... "'Permission denied to get property XULElement.selectedIndex' when calling method: [nsIAutoCompletePopup::selectedIndex]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location: "JS frame :: http://www.thehoneyfarm.com.au/acatalog/search.html :: <TOP_LEVEL> :: line 35" data: no]
Source File: http://www.thehoneyfarm.com.au/acatalog/search.html
Line: 35

[MNWF]

There were two causes:-

- the site was built in (and exported from) Business under a Site2 directory, then imported into a Catalog instance under a Site1 directory for live operation. For some reason a trace of the development site's URL and paths remained for certain templates.

- the raw HTML was initially used for the Quick Search functionality in the Primary templates, and once this was changed back to NETQUOTEVAR:SIMPLESEARCH the search issues were solved.

Hope this helps.

Hi,

I am having a similar issue and would like to know what the solution was.