|
Home > Archive > Microsoft Content Management Server > April 2005 > NRORIGINALURL needs replacing AA compliance
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
NRORIGINALURL needs replacing AA compliance
|
|
| Mick Marriott 2005-04-26, 2:48 am |
| We need to meet W3C AA compliance.
CMS is generating "NRORIGINALURL" which causes an error.
cannot generate system identifier for general
entity "NRORIGINALURL"
Is there a way to stop cms doing this.
I think it is more to do with the use of & in urls than
the actual entity reference.
Cheers
Mick
| |
| Stefan [MSFT] 2005-04-26, 7:47 am |
| Hi Mick,
what exactly is the problem?
The fact that there is a querystring parameter with name NRORIGINALURL? The
content of this parameter?
Please state exactly what is causing the problem.
Thanks,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"Mick Marriott" <Mick@discussions.microsoft.com> wrote in message
news:027b01c54a2f$fdaa4540$a601280a@phx.gbl...
> We need to meet W3C AA compliance.
> CMS is generating "NRORIGINALURL" which causes an error.
> cannot generate system identifier for general
> entity "NRORIGINALURL"
>
> Is there a way to stop cms doing this.
> I think it is more to do with the use of & in urls than
> the actual entity reference.
>
> Cheers
>
> Mick
| |
|
| Thanks for the swift reply stefan
The line of code is
<base
href="http://www.rotherham.gov.uk/Rotherham/Templates/Home
/Home.aspx?NRMODE=Published&NRORIGINALURL=%
2fgraphics&NRNODEGUID=%7bF453DDF2-0B2F-4395-89D2-
157918455CBB%7d&NRCACHEHINT=Guest">
When run throgh w3c validator we get this error recurring
Line 45, column 92: cannot generate system identifier for
general entity "NRORIGINALURL"
....ates/Home/Home.aspx?NRMODE=Published&NRORIGINALURL=%
2fgraphics&NRNODEGUID=%7b
An entity reference was found in the document, but there
is no reference by that name defined. Often this is
caused by misspelling the reference name, unencoded
ampersands, or by leaving off the trailing semicolon (;).
The most common cause of this error is unencoded
ampersands in URLs as described by the WDG in "Ampersands
in URLs".
Entity references start with an ampersand (&) and end
with a semicolon (;). If you want to use a literal
ampersand in your document you must encode it as "&"
(even inside URLs!). Be careful to end entity references
with a semicolon or your entity reference may get
interpreted in connection with the following text. Also
keep in mind that named entity references are case-
sensitive; &Aelig; and æ are different characters.
Note that in most documents, errors related to entity
references will trigger up to 5 separate messages from
the Validator. Usually these will all disappear when the
original problem is fixed.
Hope this clarifies the situation.
Cheers
Mick
>-----Original Message-----
>Hi Mick,
>
>what exactly is the problem?
>The fact that there is a querystring parameter with name
NRORIGINALURL? The
>content of this parameter?
>Please state exactly what is causing the problem.
>
>Thanks,
>Stefan
>
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights
>
>New to MCMS?
>Check out this book: Building Websites Using MCMS:
http://tinyurl.com/6zj44
>----------------------
>
>
>"Mick Marriott" <Mick@discussions.microsoft.com> wrote
in message
>news:027b01c54a2f$fdaa4540$a601280a@phx.gbl...
error.[vbcol=seagreen]
>
>
>.
>
| |
| Stefan [MSFT] 2005-04-26, 7:47 am |
| Hi Mick,
ok, when the problem is being caused by the base tag then I would suggest to
disable the BASE tag completly by adding the following line in the Page_Load
event of your templates:
RobotMetaTag1.RenderBaseHref = false;
Be sure that all your resource references in the template files (like CSS,
JS and other references) use absolut URLs starting from the web site root.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
<anonymous@discussions.microsoft.com> wrote in message
news:027401c54a38$c02129b0$a401280a@phx.gbl...[vbcol=seagreen]
> Thanks for the swift reply stefan
> The line of code is
> <base
> href="http://www.rotherham.gov.uk/Rotherham/Templates/Home
> /Home.aspx?NRMODE=Published&NRORIGINALURL=%
> 2fgraphics&NRNODEGUID=%7bF453DDF2-0B2F-4395-89D2-
> 157918455CBB%7d&NRCACHEHINT=Guest">
>
> When run throgh w3c validator we get this error recurring
>
> Line 45, column 92: cannot generate system identifier for
> general entity "NRORIGINALURL"
>
> ...ates/Home/Home.aspx?NRMODE=Published&NRORIGINALURL=%
> 2fgraphics&NRNODEGUID=%7b
>
> An entity reference was found in the document, but there
> is no reference by that name defined. Often this is
> caused by misspelling the reference name, unencoded
> ampersands, or by leaving off the trailing semicolon (;).
> The most common cause of this error is unencoded
> ampersands in URLs as described by the WDG in "Ampersands
> in URLs".
>
> Entity references start with an ampersand (&) and end
> with a semicolon (;). If you want to use a literal
> ampersand in your document you must encode it as "&"
> (even inside URLs!). Be careful to end entity references
> with a semicolon or your entity reference may get
> interpreted in connection with the following text. Also
> keep in mind that named entity references are case-
> sensitive; &Aelig; and æ are different characters.
>
> Note that in most documents, errors related to entity
> references will trigger up to 5 separate messages from
> the Validator. Usually these will all disappear when the
> original problem is fixed.
>
> Hope this clarifies the situation.
>
> Cheers
>
> Mick
>
> NRORIGINALURL? The
> confers no rights
> http://tinyurl.com/6zj44
> in message
> error.
|
|
|
|
|