Scott,
Choose to go with 5.0 or 5.5 style encoding, and then use something
outside of the witango editor to batch convert the files to the other
style.
The problem you are going to have though is that in addition to the
name changing of the encoding attributes, you have to deal with the
fact that the default encoding went from HTML to NONE. So in those
cases, you don't have anything to search and replace for.
In our case we used the <replace> task in an ant build.xml file.
We use ant for many other things so this was a nobrainer.
Another way to get around it for us was to abandon 5.0. When we add
new features to our CMS, it is for 5.5 only. Yes we still have a
server running 5.0 out there somewhere, but that server doesn't get new
features added to it. In order to support new features that server
will have to upgrade to 5.5 first.
5.0 crashes several times a day... 5.5. runs for days at a time.
/John
Scott Cadillac wrote:
Thank you for the suggestion Robert,
But therein lies the problem.
My customer has multiple Witango 5.0 and 5.5 Server machines and instances,
and the code-base is almost constantly being worked in some fashion or
another. And upgrading all servers at once is not trivial in this case.
Ultimately we want one code-base.
Thank you for your feedback.
-----Original Message-----
From: Robert Shubert [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 11:54 AM
To: [email protected]
Subject: RE: Witango-Talk: Am I totally brain dead?
It is true that using a var as the encoding type doesn't
work. Went through that a while ago with another client. The
easiest thing to do is just dupe your folder of TAFs and run
them with a search and replace routine. You'll be done in 2
minutes and have a 5.0 folder and a 5.5 folder of code. Once
you've moved to 5.5 hopefully you won't have to look back. Robert
-----Original Message-----
From: Scott Cadillac [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 1:46 PM
To: [email protected]
Subject: RE: Witango-Talk: Am I totally brain dead?
Thank you Ted,
Yes we tried that too, it's a no go.
But thanks, eh.
-----Original Message-----
From: Ted Wolfley [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 11:44 AM
To: [email protected]
Subject: RE: Witango-Talk: Am I totally brain dead?
Hi,
have you tried the following or variant:
<@VAR request$dynamicStuff <@IF EXPR='<@VERSION> beginswith
5.5'>ENCODING="META"<@else>ENCODING="METAHTML"</@if>>
Ted
-----Original Message-----
From: Scott Cadillac [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 1:06 PM
To: [email protected]
Subject: RE: Witango-Talk: Am I totally brain dead?
Thank you Bill,
I tried your suggestion, but that doesn't help.
Placing @@request$fixEnc by itself in the sample returns the value
META just fine.
The ENCODING attribute is just not accepting it.
Am I crazy, or shouldn't any Metatag attribute accept a
dynamic value?
-----Original Message-----
From: William M Conlon [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 10:56 AM
To: [email protected]
Subject: Re: Witango-Talk: Am I totally brain dead?
How about quoting attributes?
<@IF EXPR="<@VERSION> beginswith 5.5">
<@ASSIGN SCOPE="request" NAME="fixEnc" VALUE="META"> <@ELSE>
<@ASSIGN SCOPE="request" NAME="fixEnc" VALUE="METAHTML"> </@IF>
On Jan 13, 2006, at 9:48 AM, Scott Cadillac wrote:
Thank you Bill,
But that part works okay. It's the dynamic setting of the
ENCODING
attribute that is the problem.
The ENCODING attribute does not want to accept a
dynamic variable
value, and in the case of my example the <@VERSION>
metatag is not
evaluating
- it's
returning the raw text of <@VERSION>, not executing the
metatags.
The ENCODING is defaulting to NONE on 5.5, not the META
value I'm
trying to set.
By the way, I've already tried searching the List archive
on this, but
no luck.
Thanks.
-----Original Message-----
From: William M Conlon [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 13, 2006 10:43 AM
To: [email protected]
Subject: Re: Witango-Talk: Am I totally brain dead?
Try quoting '5.5' I'm betting 5.5 is getting cast as a number.
On Jan 13, 2006, at 9:34 AM, Scott Cadillac wrote:
Hi All,
I know I said I wouldn't do it again, but I couldn't help
myself - it
felt sooo gooood!
I'm writing Witango code again, but I'll leave you
guessing who I'm
working for :-)
Why doesn't the following work? Witango 5.0 or 5.5 on Windows.
<@IF EXPR="<@VERSION> beginswith 5.5"> <@ASSIGN
request$fixEnc
VALUE=META> <@ELSE> <@ASSIGN request$fixEnc
VALUE=METAHTML> </@IF>
<@ASSIGN request$dynamicStuff VALUE="<@LITERAL
VALUE='<@VERSION>'>">
<@VAR request$dynamicStuff ENCODING=@@request$fixEnc>
Has it just been so long since writing Witango code for
me, that I
can't remember some basic principle here?
Shouldn't I be able to dynamically set any attribute
value for a
Metatag?
Thank you for any feedback.
From ~ Scott Cadillac,
Software Programmer For Hire
Email ~ [EMAIL PROTECTED]
Phone ~ 403-254-5002
Web ~ http://www.xmlx.ca
Mail ~ XML-Extranet
P.O. Box 69006
RPO Bridlewood SW
Calgary, Alberta
Canada T2Y 4T9
_____________________________________________________________________
_
__
TO UNSUBSCRIBE: Go to
http://www.witango.com/developer/maillist.taf
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
______________________________________________________________
__________
TO UNSUBSCRIBE: Go to
http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to
http://www.witango.com/developer/maillist.taf
Bill
William M. Conlon, P.E., Ph.D.
To the Point
345 California Avenue Suite 2
Palo Alto, CA 94306
vox: 650.327.2175 (direct)
fax: 650.329.8335
mobile: 650.906.9929
e-mail: mailto:[EMAIL PROTECTED]
web: http://www.tothept.com
______________________________________________________________
__________
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
______________________________________________________________
__________
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
|
