Home News Contact Us Forum About Us Demos Products F.A.Q.
Shopping Cart
You currently have 0 items in your cart.


Recent Events
  • 05/09/2017 BIG Autumn SALE

    Use AUTUMN17 coupon code to buy our WordPress or Joomla! extensions with 25% discount. Hurry up! The offer is valid till 11 September.

  • 14/04/2017 Happy Easter

    Wish a Happy Easter and give 30% discount for all our WordPress and Joomla! extensions. Use EASTER17 coupon code. The offer is valid till 17 April.


2Checkout.com, Inc. is an authorized retailer of goods and services provided by ARI Soft. 2CheckOut




Follow us on twitter



Welcome, Guest
Please Login or Register.    Lost Password?

Validate html failure
(1 viewing) (1) Guest
Go to bottomPage: 12
TOPIC: Validate html failure
#12315
Validate html failure 6 Years, 7 Months ago Karma: 0
When I try to validate the html in my site, I am getting errors relating to the lightbox, and I am not sure what I am doing wrong. Can you advise? Thanks

The errors are as follows:
Line 651, Column 65: cannot generate system identifier for general entity "height"
…"#TB_inline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexyl…
✉
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.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

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.

Line 651, Column 65: general entity "height" not defined and no default entity
…"#TB_inline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexyl…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 71: reference not terminated by REFC delimiter
…nline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbo…
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

Line 651, Column 71: reference to external entity in attribute value
…nline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbo…
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

Line 651, Column 71: reference to entity "height" for which no system identifier could be generated
…nline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbo…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 64: entity was defined here
…="#TB_inline?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexy…
Line 651, Column 76: cannot generate system identifier for general entity "width"
…?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[ase…
✉
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.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

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.

Line 651, Column 76: general entity "width" not defined and no default entity
…?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[ase…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 81: reference not terminated by REFC delimiter
…neId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d…
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

Line 651, Column 81: reference to external entity in attribute value
…neId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d…
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

Line 651, Column 81: reference to entity "width" for which no system identifier could be generated
…neId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 75: entity was defined here
…e?inlineId=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[as…
Line 651, Column 86: cannot generate system identifier for general entity "modal"
…asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b922…
✉
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.

If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

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.

Line 651, Column 86: general entity "modal" not defined and no default entity
…asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b922…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 91: reference not terminated by REFC delimiter
…7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b9227bc1b…
✉
If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

Line 651, Column 91: reference to external entity in attribute value
…7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b9227bc1b…
✉
This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&'.

Line 651, Column 91: reference to entity "modal" for which no system identifier could be generated
…7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b9227bc1b…
✉
This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

Line 651, Column 85: entity was defined here
…=asl4d7b9227bd547&height=270&width=460&modal=1" rel="sexylightbox[asexy_4d7b92…
The administrator has disabled public write access.
 
#12316
Re:Validate html failure 6 Years, 7 Months ago Karma: 666
Hello,

Do you use the latest version of the extension (v. 1.8.12)?

Regards,
ARI Soft
The administrator has disabled public write access.
 
#12318
Re:Validate html failure 6 Years, 7 Months ago Karma: 0
no 1.8.8 but I just downloaded it last month? I will upload and try again
The administrator has disabled public write access.
 
#12319
Re:Validate html failure 6 Years, 7 Months ago Karma: 0
I have upgraded and still get the same issue. I am only using the plugin ai sexylightbox anywhere.

Can you advise how to resolve?
Thanks
The administrator has disabled public write access.
 
#12324
Re:Validate html failure 6 Years, 7 Months ago Karma: 666
Install the latest version, it should resolve the issue.

Regards,
ARI Soft
The administrator has disabled public write access.
 
#12326
Re:Validate html failure 6 Years, 7 Months ago Karma: 0
I have installed the latest version and it has made no difference!
Can you take a look? I sent an email with the site details previously.
Thanks
The administrator has disabled public write access.
 
Go to topPage: 12