Re: YA 4.5.1 problem

This WebDNA talk-list message is from

2004

It keeps the original formatting. numero = 58027
interpreted = N
texte = We ran into this using WebDNA on OSX-Running webstar. The only solution at that time that we could figure is we shortened all the variable names to fall under the 255 character limit. You may want to ask Dan Schutzsmith for more info if he is still on the list. He's the one that actually dealt with it.You should call webstar as well, or visit their support. There was a time when they released an update for webstar which caused this to occur. It was a cgi-plugin problem which affected everyone who upgraded that was running webdna, lasso, etc.good luck-dylanOn May 25, 2004, at 4:08 PM, Patrick Junkroski wrote:> We are using 4.5.1 with WebSTAR 5.3.2 on OS 10.3.3 - dual 1.8 Ghz G5. > 1GB RAM.>> Upon moving several of our customers from our OS 9/ WebDNA 4.0 server > to the above configuration, I began getting reports about sorting > preferences and shownext contexts breaking down.>> I have used this code for years:>> [hideif [numfound]<[_max]]>

More Results: > [math show=F]location=0[/math][shownext position=begin] SIZE="3" FACE="Arial"> > [math]location=[location]+1[/math]> [/shownext][shownext position=middle] FACE="Arial">[math]location=[location]+1[/math] > [/shownext][shownext position=end] FACE="Arial"> HREF="adminresults.tpl?[formvariables > name=_&exact=F][name]=[url][value][/url]&[/ > formvariables]startat=[start]"> > [math]location=[location]+1[/math] [/shownext]> > [/hideif]>> It has worked universally.>> However, with a few clients, the form variables are so numerous as to > make a URL that exceeds 255 characters. It never mattered on the old > server; Results always worked as needed. But the long URL is the only > explanation I can come up with for it to have stopped working on the > new server.>> I've replaced the code with this:> [hideif [numfound]<[_max]]> >

> > > >

More Results: [math > show=F]location=0[/math][shownext position=begin][/shownext]

[shownext position=middle] FACE="Arial">[math]location=[location]+1[/math][/ > shownext]

[shownext position=end][/shownext]>

> > [/hideif]>> So that form variables are passed as hidden inputs instead of via a > URL. However, I can't get it to look "pretty".>> My questions are:> 1) Why did this happen when we moved to the new configuration? Has > anyone else experienced this problem?> 2) Can someone help me improve my table to make this look nicer?> 3) We purchased 6.0 but I've been afraid to install it because I want > to get on top of this (and other) problems first. Does anyone know if > 6.0 "fixes" this, or if there are other caveats I need to heed?>> Your help is appreciated. Thanks!> -----> Patrick Junkroski> http://www.vsm.net> 239.642.0304>>> -------------------------------------------------------------> This message is sent to you because you are subscribed to> the mailing list .> To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/>-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

Re: YA 4.5.1 problem ( "eLists" 2004)
Re: YA 4.5.1 problem ( Patrick Junkroski 2004)
Re: YA 4.5.1 problem ( eLists 2004)
Re: YA 4.5.1 problem ( Dylan Wood 2004)
Re: YA 4.5.1 problem ( Patrick Junkroski 2004)
Re: YA 4.5.1 problem ( Dylan Wood 2004)
YA 4.5.1 problem ( Patrick Junkroski 2004)

We ran into this using WebDNA on OSX-Running webstar. The only solution at that time that we could figure is we shortened all the variable names to fall under the 255 character limit. You may want to ask Dan Schutzsmith for more info if he is still on the list. He's the one that actually dealt with it.You should call webstar as well, or visit their support. There was a time when they released an update for webstar which caused this to occur. It was a cgi-plugin problem which affected everyone who upgraded that was running webdna, lasso, etc.good luck-dylanOn May 25, 2004, at 4:08 PM, Patrick Junkroski wrote:> We are using 4.5.1 with WebSTAR 5.3.2 on OS 10.3.3 - dual 1.8 Ghz G5. > 1GB RAM.>> Upon moving several of our customers from our OS 9/ WebDNA 4.0 server > to the above configuration, I began getting reports about sorting > preferences and shownext contexts breaking down.>> I have used this code for years:>> [hideif [numfound]<[_max]]>

More Results: > [math show=F]location=0[/math][shownext position=begin] SIZE="3" FACE="Arial">[url][value][/url]&[/ > formvariables]startat=[start]"> > [math]location=[location]+1[/math]> [/shownext][shownext position=middle] FACE="Arial">[math]location=[location]+1[/math] > [/shownext][shownext position=end] FACE="Arial"> HREF="adminresults.tpl?[formvariables > name=_&exact=F][name]=[url][value][/url]&[/ > formvariables]startat=[start]"> > [math]location=[location]+1[/math] [/shownext]> > [/hideif]>> It has worked universally.>> However, with a few clients, the form variables are so numerous as to > make a URL that exceeds 255 characters. It never mattered on the old > server; Results always worked as needed. But the long URL is the only > explanation I can come up with for it to have stopped working on the > new server.>> I've replaced the code with this:> [hideif [numfound]<[_max]]> >

> > > >

More Results: [math > show=F]location=0[/math][shownext position=begin][/shownext]

[shownext position=middle] FACE="Arial">[math]location=[location]+1[/math][/ > shownext]

[shownext position=end][/shownext]>

DOWNLOAD WEBDNA NOW!

Re: YA 4.5.1 problem

2004

Top Articles:

Related Readings: