Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Lee, there was a 'glitch' somewhere

Jan 4, 2005 7:16PM PST

Discussion is locked

- Collapse -
From what I remember when the
Jan 4, 2005 9:50PM PST

new CNET software was brought in, this was discussed by members who know coding well and they discovered a bad leak that could exploit the forum software if normal HTML coding was allowed to stand. The software people made the decision at that time to block normal HTML coding (which is why we can't use pictures for sigs anymore, too)and the double quotes was discussed pretty heavily at that time. Some members, including you it seems, has forgotten about that issue and have inadvertently used normal HTML coding for shortened links and have run into this wall. I don't think this is a glitch per se but rather a deliberate block to protect the integrity of the forum software.

TONI

- Collapse -
maybe so Toni
Jan 5, 2005 1:07AM PST

but i don't know the difference between
no quotes
quotes and


and i wouldn't even know what to do with them, where and why Sad

jonah


.

- Collapse -
by using the NO QUOTES
Jan 5, 2005 1:38AM PST

the shortened link will work to go where you want it to go because the CNET software will fill in the blanks required. If you put in one set of quotes, the software doubles it automatically and sends the return loop as basically dead.

Kind of the same way it can read the < > marks to be incorrect and we have to use the brackets [ ] instead and it decodes it automatically to be the correct < > marks. LOL

TONI