Thanks everybody for jumping in trying to help.
Anthony Humphreys was able to help me resolve my issue. It had to do with
changing datasources.
Best,
Caroline Wise
Senior Applications Developer
Interactive Sites
480-707-1600 x223 (office)
480-707-1717 (direct)
a cheap way to make search args SEO friendly is to just append keyword
laden arguments. If your taf is looking for something like ?
_function=listcat=3 which a search engine overlooks, append
descriptive arguments that may or may not actually be used in the taf,
such as ?
Thanks for your response, Robert.
IE 7 is installed on the 64bit server. Did you find a way to make it
work with IE 7 installed, or did you have to go back to an older version
of IE to get it going? If you had to go back to an older version, did it
work out of the box, or were there other
Here's a little more help on this issue:
IIS: set the 404 error handling in the Custom Errors tab to: URL: /main.taf
(or whatever is going to handle this)
At the top of main.taf use code something like this:
@ASSIGN url @CGIPARAM name=http_search_args
@ASSIGN parsed_url @TOKENIZE
Actually, we had the option to not use HTTPS so we didn't resolve the issue.
My suggestion is to verify that IE 6 is still installed on the server where
it works, and if so, try uninstalling IE 7, and test. The theory here is
that Witango is using some built-in windows call for the @URL
Uninstalling IE7 made it work. Thanks again.
-Richard
From: Robert Shubert [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2008 08:39
To: witango-talk@witango.com
Subject: RE: Witango-Talk: Are there any issues with @URL on
Professional version of
Hi Everyone,
Has anyone worked with Paypal IPN? I'm struggling a bit with constructing
the IPN Postback Validation post in Witango. Do you have a snippet of
code that you could share with me that does this?
Thanks,
Stefan
=
Database WebWorks:
