You are viewing this forum as a guest. Login to an existing account, or create a new account, to reply to topics and to create new topics.
In changing the welcome page I ran into a problem with the functioning. It seems whenever I reload the Update Page it takes it upon itself to change my <IMG SRC=<... and <A HREF=,.. tags in the HTML to <IMG SRC><... and <A HREF><... which really messes things up if I don't manually change them back before updating. What is going on?
Nick, let me make a couple of before and after screen shots and send them to your email address. Was driving me up a wall.
Got the screenshots - here was the response...
The program is not doing this, but by the looks of the screenshots you're using XP. Maybe it's something to do with that OS and the IE that's shipped with it. I think I have a fix, though. I've noticed that you're not using quotes in your HREFs and IMG SRCs. You really should - it's proper to do it that way. Instead of:
<A HREF=<CGIVAR>xxx</CGIVAR>>
Try:
<A HREF="<CGIVAR>xxx</CGIVAR>">
And so on... See if that cures your issue. As I said, the program is not doing it - must be the browser as it's rendering the page to you and posting back to the server. I think this solution will work, though.
Offline
Noticed something similar when I was importing products where I had added some html to the display text. After importing it changed all " quotation marks to 2 '' apostrophes.
After changing every item to a single ' it then stripped even that out on the next save.
So what started as <a href="something">
became <a href=''something''>
which I changed to <a href='something'>
and finaly cpp5 changed it again too <a href=something>
Not a big deal as other than that initial change it all still loads fine. But figured you'd want to know about the potential there for problems.
Myros
In the fields that are not displayed as TEXTAREA fields in admin, it is necessary to replace double quotes (") with something else, so we chose two single quotes (''). The reason for this is that HTML form elements depend on double quotes to limit the VALUE tag. Including double quotes in a VALUE tag blows apart a form.
For SQL databases, a single single quote (1 of them - ') is bad news because that's used to determine quotes within SQL. That said, here's what the program does in non-TEXTAREA fields:
" - ''
' - deleted
A necessary evil. This is not the case here as the HTML Hal's editing is within a TEXTAREA and the issue is Win XP related (I think).
Offline
Definitely Win XP Pro related as I had the same erroneous result with Opera and Netscape as browsers on the XP box and did not experience the problem on a Win98SE box. Now what?
I guess we're going to have to re-work the CGIVAR and CGIGET tags in the update to use something other than < >. Could you test out using:
%CGIVAR% %/CGIVAR% and see if any replacement occurs?
Also try: <%CGIVAR%> <%/CGIVAR%>
The second one is how ASP uses variables. I wonder if they screwed that up too. If you could do this test ASAP I would appreciate it, as I would like to get the update out this afternoon. Thanks.
Offline
From Hal:
The %CGIVAR%xxx%/CGIVAR% was not changed in the reopening of the edit box but obviously didn't work in displaying the HTML page while <%CGIVAR%>xxx<%/CGIVAR%> suffered from the same "change the " to a >" problem.
Response:
Sounds like they screwed themselves with ASP & XP. Oh well. I'm
going to re-write the CGIVAR and CGIGET logic in the update to use % % instead of < >. Keep your eyes peeled for the update.
Offline
Doesn't look very HTML "element" like, but if it works... Will you be making the change to all <CGI... elements as I notice some don't seem to be affected?
Some reason your server quit letting me get to the forum. Sorry for the hiatus.
Should have expanded on my comment, all <CGIVAR>xx</CGIVAR> elements seem to be affected. There was a <CGIGET TYPE="SUB" VALUE="ste_prod_disp"> statement in that same splash edit box which was not affected. I was trying to ask whether you intended %CGIGET TYPE... for this guy as well?
I think I may want to use ( ) instead of percents, but for whatever we do, it will be for both types of tags. Can you test out:
(CGIVAR) (/CGIVAR)
And see if that is troublesome? Thanks.
Offline
Caused no problems and the () definitely looks less hoaky than %%. Looking forward to the update, as I am sure all WinXPers will.