Adam,
I have no comments for or against the ( instead of [ trick - but if
it works that certainly helps, doesn't it? I would guess it has more
to do with the code shorthand not being handled properly though - and
could also be handled by a search and replace. I always write things
out a bit more, like:
<@var request$exampleArray[<@var request$rowCounter>,FieldName]>
You might try doing a replace on one file and see if it works. It's
certainly more 'correct' than using the parentheses, although I
really don't know if that's going to help.
Good luck with it!
Jason
-----
Jason Pamental
Director of Web Services
North Sails
Office: 401.643.1415
Fax: 401.643.1420
Mobile: 401.743.4406
Email: [EMAIL PROTECTED]
On Feb 7, 2007, at 4:26 PM, Adam Leisring wrote:
Thanks for the info. Jason. I've actually figured out a work-
around, but it's not one that I feel comfortable implementing.
The issue seems to occur in IF actions (not metatags), I've pasted
examples below:
Non-working example in 5.5 - working in 5.0:
@@request$exampleArray[@@request$rowCounter,FieldName]
Working example in 5.5 - not tested in 5.0:
@@request$exampleArray(@@request$rowCounter,FieldName)
You'll notice that all I've done to fix the issue is replace the []
brackets with () parenthesis. I've checked Witango documentation,
this is not correct syntax, but works none-the-less.
It seems like the Witango interpreter is getting hung up on [] used
in extracting array data in IF actions... maybe related to the
CDATA encapsulators?
Has anyone encountered an issue like this? Can someone from the
Witango team provide any insight? This issue affects around 20% of
our applications and has thrown a wrench into our conversion timeline!
Our environment is a Windows 2000 Advanced Server using Witango
5.5.20 and a Pervasive 9.5 Database.
Thanks to any help anyone can provide!
Adam Leisring
Fischer Homes, Inc.
>>> [EMAIL PROTECTED] 02/06/07 12:08PM >>>
Adam,
The only major 'gotcha' I encountered was making sure that all
places where I used 'encoding=multilinehtml' were change to
'encoding=multiline'. Otherwise I don't think I had any problems.
Things to look at though would also be customizations you may have
made to the witango.ini file - like default scope for variables.
It would help to know the server platform though, and any other
details you can think of. If you look at two or three of the files
that are producing errors you might find a common thread.
Hope that helps-
Jason
-----
Jason Pamental
Director of Web Services
North Sails
Office: 401.643.1415
Fax: 401.643.1420
Mobile: 401.743.4406
Email: [EMAIL PROTECTED]
On Feb 6, 2007, at 11:19 AM, Adam Leisring wrote:
Hello everyone,
We're in the process of upgrading our Witango Server from 5 to 5.5
and we've encountered an odd issue. Applications that work
properly in the 5 environment are throwing Syntax errors.
Specifically, it deals with 'Missing closing brackets' and
'Missing quote at the end of the statement' kinds of problems.
Again, these applications work without issue in the 5 environment.
Has anyone encountered something like this? Am I missing a
configuration option? Is there a conversion application I should
run against the Witango 5 applications to bring them up to 5.5?
Any help is greatly appreciated!
Thanks,
Adam Leisring
Fischer Homes, Inc.
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
