about . contact . resell e-junkie

address along benefit button buy cart code com content data display ejejc example fixed href html issue javascript listen modification option page php post properly replace reply requires resolve return show situation standard subject system tag thank-you url view website www

When I run my website through http://validator.w3.org, there are four (4) categories of e-junkie errors that repeatedly appear. How can these errors be fixed, so that my website's code is in compliance?

---> Error #1 XML Parsing Error: EntityRef: expecting ';'

Line 28, column > 80: XML Parsing Error: EntityRef: expecting ';'
…www.e-junkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="…



---> Error #2 reference to external entity in attribute value

Line 28, column 81: reference to external entity in attribute value
…ww.e-junkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="j

Line 28, column 81: reference to external entity in attribute value
…ww.e-junkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="j
Line 28, column 91: reference to external entity in attribute value
…e.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="javascript:



---> Error #3 reference not terminated by REFC delimiter

Line 28, column 81: reference not terminated by REFC delimiter
…ww.e-junkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="j

Line 48, column 832: reference not terminated by REFC delimiter
…ef="index.php?option=com_content&view=article&id=59" title="Listen, shop and



---> Error #4 cannot generate system identifier for general entity X

Line 28, column 79: cannot generate system identifier for general entity "cl"
…/www.e-junkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick=
Line 28, column 88: cannot generate system identifier for general entity "ejc"
…nkie.com/ecom/gb.php?c=cart&cl=11918&ejc=2" target="ej_ejc" onclick="javascri

Thank you.

Please see http://www.e-junkie.com/bb/topic/79

First of all, the code that's generating this error is the code that is generated by e-junkie and is obtained at e-junkie's "get button code." Why hasn't this issue been addressed at the code generation level?

Secondly, that topic/79 post you referenced is not helpful.

The initial answer on topic/79 says:
1. Remove the target="..." part
2. Replace & with &
3. Add an alt='buy this' to the image tag

In a later reply it says:
Have you replace all occurence of & in the URL with & amp;

So which is it?

For the sake of simplicity, please take the following snippet of code that's generating the error, and show us what it SHOULD look like to resolve this W3C compliance issue:

<a href="https://www.e-junkie.com/ecom/gb.php?c=cart&i=63713&cl=11918&ejc=2" target="ej_ejc" class="ec_ejc_thkbx" onClick="javascript:return EJEJC_lc(this);">

Thank you.

Your example should look something like this:

<a href="https://www.e-junkie.com/ecom/gb.php?c=cart& amp;i=63713& amp;l=11918& amp;ejc=2" alt="Add to Cart" class="ec_ejc_thkbx" onClick="javascript:return EJEJC_lc(this);">

(Note that for demonstration purposes, I had to enter a [space] between the "&" and "amp;" which should be run together in practice -- without the [space]s I inserted, your browser would display it as a plain "&" without the "amp;" part being visible)

BTW, I presume you are using XHTML because it is being used within, or interoperating with, the larger scope of an XML data framework you have developed? Since I don't know your specific situation, consider the following as general advice (perhaps at least for the benefit of others playing along at home :^):

If you are not using XML, then there's really no reason to use XHTML, with all the pitfalls and tradeoffs that entails. XHTML is not the "latest standard" for HTML (that would be HTML 4.01), it's just a special modification of HTML that can be included within XML data records. As such, XHTML is subject to the much stricter parsing validation of XML (where one syntax error could devastate the functioning of an entire dataset and any programming schema dependent on that data). Perfectly valid HTML will not validate as XML, so XHTML was invented to address that specific need for certain developers; some browsers will refuse to render an XHTML page at all if it's not perfect, whereas they're much more forgiving with "regular" HTML (which can also be optimized to load quicker with less code, whereas XHTML requires extra code bloat to complete the XML syntax and validate properly at all). FYI and FWIW, YMMV. ;^D