Re: Shownext on AOL

This WebDNA talk-list message is from

2003

It keeps the original formatting. numero = 46951
interpreted = N
texte = Hi Glenn,I've never used ShowNext, so I'm not familiar with the details. If your HTML validates...I had a problem that could be similar to your problem. I have an application that is a lot of Javascript and WebDNA (and HTML and CSS, it probably goes without saying) mixed together. The application worked great (and validated) in the browsers I tested, but parts of it wouldn't work for one particular user, and it turned out those same parts didn't work in several operating system/browser combinations--the particular pages weren't finding data on the browsers in which it wasn't working.The problem turned out to be the way Javascript passed the parameters to the WebDNA pages. The parameters were joined with & (which I presumed to be proper in a URL even in Javascript--still haven't looked for the spec). In most circumstances, the & was properly trimmed, leaving correct variable names. In some browser/OS combinations, the variables came through with amp; at the beginning of variable names. Thus searches found nothing. The first parameter came through correctly (preceded by the ?), so it was a problem only on pages where multiple parameters were passed.I was pretty fried by the time I tracked this down, so I didn't look for an elegant solution. I just looked for variables beginning with amp; at the top of my WebDNA on the affected pages, and trimmed off the first four characters. This fixed the problem, without breaking it on the machines/browsers where it already worked. Except for on one combination, which nobody needed, and I didn't pursue what was going on there.I suppose your problem could be a problem with how AOL is passing parameters. But like I said, I've never used SHOWNEXT and don't quite get how it works.VelmaAt 01:25 PM 01/18/03, you wrote:>Thanks for the feedback, guys.>>I really don't think it's an html error in my code. I've checked it 40 >ways from Sunday and had a validator look at it, too. No probs show up.>> >> >> >Next, check to see whether or not the browser is caching pages it should > not cache. If so, you may need to put a unique value into every link in > your web site -- in order to force the browser to get the page from the > server instead of from its cache.>>I have a Startat= thing in the URL. It shows either Startat=1 or >Startat=21. Is that not adequate as a unique value?>>It could be AOHell's notorious server cache. I need to look into that more.>>It may also be the version of that particular browser. I think AOL was >using IE with its V4 software, but I'm not sure...not that anything from >MS ever does unusual or non-standard things, of course.>>I found this info about browser caching in some old files, but can't >remember where it is online.>> >Expires> >This tells the browser the date and time when the document will be > considered expired. If a user is using Netscape Navigator, a request > for a document whose time has expired will initiate a new network > request for the document. An illegal Expires date such as 0 is > interpreted by the browser as immediately. Dates must be in the RFC850 > format, (GMT format):> >> >> >Pragma> >This is another way to control browser caching. To use this tag, the > value must be no-cache. When this is included in a document, it > prevents Netscape Navigator from caching a page locally.> >> >> >These two tags can be used as together as shown to keep your content > current-but beware. Many users have reported that Microsoft's Internet > Explorer refuses the META tag instructions, and caches the files anyway. > So far, nobody has been able to supply a fix to this bug. As of the > release of MSIE 4.01, this problem still existed.>>>Glenn>>------------------------------------------------------------->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/--------------------------------------------------------------------------Velma KahnGlory Day Software Company200 Tanager Ln NW, Floyd, Virginia 24091, U.S.A.phone: 540-745-6469 * fax: 651-321-4884email: vkahn@glorydaysoftware.comwww.glorydaysoftware.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: Shownext on AOL (Glenn Busbin 2003)
Re: Shownext on AOL (Kenneth Grome 2003)
Re: Shownext on AOL (Donovan 2003)
Re: Shownext on AOL (Glenn Busbin 2003)
Re: Shownext on AOL (Kenneth Grome 2003)
Re: Shownext on AOL (Velma Kahn 2003)
Re: Shownext on AOL (Glenn Busbin 2003)
Re: Shownext on AOL (Kenneth Grome 2003)
Re: Shownext on AOL (Pedro Rivera 2003)
Shownext on AOL (Glenn Busbin 2003)

Hi Glenn,I've never used ShowNext, so I'm not familiar with the details. If your HTML validates...I had a problem that could be similar to your problem. I have an application that is a lot of Javascript and WebDNA (and HTML and CSS, it probably goes without saying) mixed together. The application worked great (and validated) in the browsers I tested, but parts of it wouldn't work for one particular user, and it turned out those same parts didn't work in several operating system/browser combinations--the particular pages weren't finding data on the browsers in which it wasn't working.The problem turned out to be the way Javascript passed the parameters to the WebDNA pages. The parameters were joined with & (which I presumed to be proper in a URL even in Javascript--still haven't looked for the spec). In most circumstances, the & was properly trimmed, leaving correct variable names. In some browser/OS combinations, the variables came through with amp; at the beginning of variable names. Thus searches found nothing. The first parameter came through correctly (preceded by the ?), so it was a problem only on pages where multiple parameters were passed.I was pretty fried by the time I tracked this down, so I didn't look for an elegant solution. I just looked for variables beginning with amp; at the top of my WebDNA on the affected pages, and trimmed off the first four characters. This fixed the problem, without breaking it on the machines/browsers where it already worked. Except for on one combination, which nobody needed, and I didn't pursue what was going on there.I suppose your problem could be a problem with how AOL is passing parameters. But like I said, I've never used SHOWNEXT and don't quite get how it works.VelmaAt 01:25 PM 01/18/03, you wrote:>Thanks for the feedback, guys.>>I really don't think it's an html error in my code. I've checked it 40 >ways from Sunday and had a validator look at it, too. No probs show up.>> >> >> >Next, check to see whether or not the browser is caching pages it should > not cache. If so, you may need to put a unique value into every link in > your web site -- in order to force the browser to get the page from the > server instead of from its cache.>>I have a Startat= thing in the URL. It shows either Startat=1 or >Startat=21. Is that not adequate as a unique value?>>It could be AOHell's notorious server cache. I need to look into that more.>>It may also be the version of that particular browser. I think AOL was >using IE with its V4 software, but I'm not sure...not that anything from >MS ever does unusual or non-standard things, of course.>>I found this info about browser caching in some old files, but can't >remember where it is online.>> >Expires> >This tells the browser the date and time when the document will be > considered expired. If a user is using Netscape Navigator, a request > for a document whose time has expired will initiate a new network > request for the document. An illegal Expires date such as 0 is > interpreted by the browser as immediately. Dates must be in the RFC850 > format, (GMT format):> >> >> >Pragma> >This is another way to control browser caching. To use this tag, the > value must be no-cache. When this is included in a document, it > prevents Netscape Navigator from caching a page locally.> >> >> >These two tags can be used as together as shown to keep your content > current-but beware. Many users have reported that Microsoft's Internet > Explorer refuses the META tag instructions, and caches the files anyway. > So far, nobody has been able to supply a fix to this bug. As of the > release of MSIE 4.01, this problem still existed.>>>Glenn>>------------------------------------------------------------->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/--------------------------------------------------------------------------Velma KahnGlory Day Software Company200 Tanager Ln NW, Floyd, Virginia 24091, U.S.A.phone: 540-745-6469 * fax: 651-321-4884email: vkahn@glorydaysoftware.comwww.glorydaysoftware.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/ Velma Kahn

DOWNLOAD WEBDNA NOW!

Re: Shownext on AOL

2003

Top Articles:

Related Readings: