Inoutscripts Shopping Cart Made a New Guiness World Record （514 Bugs)

It is well known that Inoutscripts is the No. 1 phishing scamming software company lacated in Kerala India. Inout Scripts Shopping Cart has 514 bugs (errors and warnings) and it created a new Guiness World Record. It's true. It's not a joking.

https://www.upfan.net/2018/03/its-not-a-joking-more-than-400-bugs-with-inoutscripts-shooping-cart.html

https://www.mail178.com/can-you-believe-it-514-bugs-with-inout-scripts-shopping-cart/

http://onlinor.com/index.php/business/281-it-s-not-a-joking-514-bug-with-inoutscripts-shooping-cart

https://baojii.com/news/show.php?itemid=193

https://wordpress.com/post/talkscripts.wordpress.com/226

Too greedy! These Indian Inout Scripts Scammers (这些印度Inoutscripts骗子太贪婪、太猖狂了）

Fooled by their advertising online, I bought their inout search engine and its addons for 1070 USD, and Inout Spider for $2950. the so called big data based spider not only stopped crawling after installation, but produced huge amount of errro log and core files that caused the server down finally. On the other hand, the Inout Spider was not compatible with the Inout search engine v8. I contacted their support and head Kumar, but they did not get them fixed with one year.

They said they could provide reinstallation of the same script, but wanted to charge $80 more. I guessed the things would happen, since they did not revise the scripts.

With my suggestion, they agreed that they could install the Nutch to replace the Inout spider, but they had to charge $480 for the Nutch installation and integration with Inout search engine. I had no choice and paid the money by Paypal. What happened next? The Nutch they installed did not work. It had just crawled 6GB data with 5 months, and it did not match with the Inout search engine. They said it might be the limitation of Nutch. You know Nutch is an open source enterprise spider having been used by a lot of commercial websites with no limitation.

Finally, they took the cash and left me nothing working. They did not refund, and did not fix the issues.

We sued to Paypal, but Paypal said this was not physical items, and they could not guaranteed the safe purchasing.

The team of scammers are Jacob, Kumar, Nair, and Saranya.

Joomla Tutorials for Beginners

Tutorials:Beginners - Joomla! Documentation

https://docs.joomla.org/Tutorials:Beginners

Mar 2, 2016 - This page is a Portal to a list Tutorials aimed at Beginning Joomla! Users, please note the timestamp on the above notice. If you have any ideas, please create redlinks to topics you would like covered under Wanted Topics below. Contents. [hide]. 1 Topics. 1.1 Joomla! 3.x; 1.2 Joomla! 2.5. 2 Wanted ...

Joomla Tutorials - Joomla Tutorials

https://www.joomlatutorials.com/

Joomla Tutorials will help you learn to use Joomla. Learn how to use Joomla with animated tutorials, along with other tricks and tips. Help and tutorials are available for all current versions of Joomla.

Joomla Tutorial

https://www.tutorialspoint.com › Joomla › Joomla - Home

Joomla Tutorial for Beginners - Learn Joomla in simple and easy steps starting from basic to advanced concepts with examples including Overview, Installation, Architecture, Control Panel, Toolbar, Site Menu, Menus Menu, Content Menu, Components Menu, Extensions Menu, Tools Menu, Help Menu, Create Menus, ...

Joomla 3.6 Tutorial for Beginner - YouTube

▶ 1:00:39

https://www.youtube.com/watch?v=tRj3ZDaMaj0

Jul 17, 2016 - Uploaded by Kursus Joomla

JOOMLA 3.7 Tutorial - https://www.youtube.com/watch?v=ANqE6DaMd7g FREE PERFORMANCE JOOMLA ...

Don't be scammed. Inoutscripts search v8 is just a kind of meta tool.

Inout Scripts Search v8 is not a real search engine script, but a kind of meta tool. You have to pay a lot to get the APIs from Yahoo, Google, Bing.

I bought their inout search engine and its addons for 1070 USD, and Inout Spider for $2950. the so called big data based spider not only stopped crawling after installation, but produced huge amount of errro log and core files that caused the server down finally. On the other hand, the Inout Spider was not compatible with the Inout search engine v8. I contacted their support and head Kumar, but they did not get them fixed with one year.

They said they could provide reinstallation of the same script, but wanted to charge $80 more. I guessed the things would happen, since they did not revise the scripts.

With my suggestion, they agreed that they could install the Nutch to replace the Inout spider, but they had to charge $480 for the Nutch installation and integration with Inout search engine. I had no choice and paid the money by Paypal. What happened next? The Nutch they installed did not work. It had just crawled 6GB data with 5 months, and it did not match with the Inout search engine. They said it might be the limitation of Nutch. You know Nutch is an open source enterprise spider having been used by a lot of commercial websites with no limitation.

Finally, they took the cash and left me nothing working. They did not refund, and did not fix the issues.

We sued to Paypal, but Paypal said this was not physical items, and they could not guaranteed the safe purchasing.

https://www.upfan.net/2018/03/its-not-a-joking-more-than-400-bugs-with-inoutscripts-shooping-cart.html

https://www.mail178.com/can-you-believe-it-514-bugs-with-inout-scripts-shopping-cart/

http://onlinor.com/index.php/business/281-it-s-not-a-joking-514-bug-with-inoutscripts-shooping-cart

https://baojii.com/news/show.php?itemid=193

https://talkscripts.wordpress.com/

https://www.complaintsboard.com/inout-scripts-nesote-technologies-b120320

United Kingdom unveils online AI tool to block ISIS content

The UK government has unveiled a new technology that can automatically detect by using artificial intelligence the ISIS propaganda materials and violent videos which are used for recruiting cadres online.

Developed by the UK Home Office and London-based company ASI Data Science, the technology uses advanced machine learning to analyse the audio and visuals of a video to determine whether it could be ISIS propaganda. The Home Office said in a statement yesterday that its new tool can automatically detect 94 per cent of ISIS propaganda with 99.995 per cent accuracy.

“The purpose of these videos is to incite violence in our communities, recruit people to their cause, and attempt to spread fear in our society. We know that automatic technology like this can heavily disrupt the terrorists actions, as well as prevent people from ever being exposed to these horrific images,” UK home secretary Amber Rudd said in reference to the new tool. “This government has been taking the lead worldwide in making sure that vile terrorist content is stamped out,” she said.

The announcement came as she addressed a Digital Forum in Silicon Valley during a US visit this week.

She discussed the new anti-terror tool on her visit during talks with internet service providers in the country as part of the Global Internet Forum to Counter Terrorism, which was launched last year in the aftermath of the UK Parliament attack in March 2017. The Home Office and ASI said they will be sharing the methodology behind the new model with smaller companies, in order to help combat the abuse of their platforms by terrorists and their supporters.

According to them, many of the major tech companies have developed technology specific to their own platforms and have publicly reported on the difference this is making in their fight against terrorist content. But smaller platforms are increasingly targeted by ISIS and its supporters and they often do not have the same level of resources to develop technology. “The model, which has been trained using over 1,000 ISIS videos, is not specific to one platform so can be used to support the detection of terrorist propaganda across a range of video-streaming and download sites in real-time,” the Home Office said.

Separately, new Home Office analysis revealed that ISIS supporters used more than 400 unique online platforms to push out their poisonous material in 2017, highlighting the importance of technology that can be applied across different platforms. Previous research has found the majority of links to ISIS propaganda are disseminated within two hours of release, while a third of all links are disseminated within the first hour. The new research also shows 145 new platforms from July 2017 until the end of the year had not been used before.

https://upfan.net/

Most detailed analysis of Inoutscripts Shopping Cart Codes (514 bugs)

1.  Line 25, Column 37: required attribute “type” not specified

    <script src="js/jquery-ui1.10.3.js"></script>

   The attribute given above is required for an element that you’ve used, but you have omitted it. For instance, in most HTML and XHTML document types the “type” attribute is required on the “script” element and the “alt” attribute is required for the “img” element.

   Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
2.  Line 88, Column 32: cannot generate system identifier for general entity “pro_qty”

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

   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.
3.  Line 88, Column 32: general entity “pro_qty” not defined and no default entity

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

   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.
4.  Line 88, Column 39: reference not terminated by REFC delimiter

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

   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.
5.  Line 88, Column 39: reference to entity “pro_qty” for which no system identifier could be generated

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

   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.
6.  Line 88, Column 31: entity was defined here

    data: "cartid="+cartid+"&pro_qty="+pro_qty,

7.  Line 105, Column 40: reference not terminated by REFC delimiter

   … data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

   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.
8.  Line 105, Column 40: reference to entity “pro_qty” for which no system identifier could be generated

   … data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

   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.
9.  Line 88, Column 31: entity was defined here

    data: "cartid="+cartid+"&pro_qty="+pro_qty,

10.  Line 105, Column 53: cannot generate system identifier for general entity “cartid”

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
11.  Line 105, Column 53: general entity “cartid” not defined and no default entity

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
12.  Line 105, Column 59: reference not terminated by REFC delimiter

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
13.  Line 105, Column 59: reference to entity “cartid” for which no system identifier could be generated

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
14.  Line 105, Column 52: entity was defined here

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

15.  Line 105, Column 71: cannot generate system identifier for general entity “userid”

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
16.  Line 105, Column 71: general entity “userid” not defined and no default entity

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
17.  Line 105, Column 77: reference not terminated by REFC delimiter

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
18.  Line 105, Column 77: reference to entity “userid” for which no system identifier could be generated

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
19.  Line 105, Column 70: entity was defined here

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

20.  Line 111, Column 22: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
21.  Line 111, Column 23: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
22.  Line 129, Column 36: document type does not allow element “span” here

    view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
23.  Line 134, Column 34: document type does not allow element “span” here

    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
24.  Line 141, Column 36: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
25.  Line 185, Column 40: reference not terminated by REFC delimiter

    …  data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    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.
26.  Line 185, Column 40: reference to entity “pro_qty” for which no system identifier could be generated

    …  data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+…

    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.
27.  Line 88, Column 31: entity was defined here

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

28.  Line 185, Column 59: reference not terminated by REFC delimiter

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
29.  Line 185, Column 59: reference to entity “cartid” for which no system identifier could be generated

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
30.  Line 105, Column 52: entity was defined here

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

31.  Line 185, Column 77: reference not terminated by REFC delimiter

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
32.  Line 185, Column 77: reference to entity “userid” for which no system identifier could be generated

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

    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.
33.  Line 105, Column 70: entity was defined here

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

34.  Line 189, Column 22: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
35.  Line 189, Column 23: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
36.  Line 209, Column 37: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
37.  Line 213, Column 39: document type does not allow element “span” here

     view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
38.  Line 219, Column 34: document type does not allow element “span” here

    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
39.  Line 226, Column 36: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
40.  Line 273, Column 39: reference not terminated by REFC delimiter

     data: "cartid="+cartid+"&userid="+userid,

    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.
41.  Line 273, Column 39: reference to entity “userid” for which no system identifier could be generated

      data: "cartid="+cartid+"&userid="+userid,

    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.
42.  Line 105, Column 70: entity was defined here

    …data: "pro_id="+pro_id+"&pro_qty="+pro_qty+"&cartid="+cartid+"&userid="+userid,

43.  Line 287, Column 36: document type does not allow element “span” here

      view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
44.  Line 292, Column 34: document type does not allow element “span” here

    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
45.  Line 298, Column 36: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
46.  Line 332, Column 39: reference not terminated by REFC delimiter

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
47.  Line 332, Column 39: reference to entity “pro_qty” for which no system identifier could be generated

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
48.  Line 88, Column 31: entity was defined here

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

49.  Line 359, Column 40: reference not terminated by REFC delimiter

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
50.  Line 359, Column 40: reference to entity “pro_qty” for which no system identifier could be generated

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
51.  Line 88, Column 31: entity was defined here

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

52.  Line 365, Column 22: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
53.  Line 365, Column 23: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
54.  Line 384, Column 37: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
55.  Line 388, Column 36: document type does not allow element “span” here

    view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
56.  Line 394, Column 34: document type does not allow element “span” here

    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
57.  Line 401, Column 36: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
58.  Line 440, Column 40: reference not terminated by REFC delimiter

       data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
59.  Line 440, Column 40: reference to entity “pro_qty” for which no system identifier could be generated

      data: "cartid="+cartid+"&pro_qty="+pro_qty,

    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.
60.  Line 88, Column 31: entity was defined here

     data: "cartid="+cartid+"&pro_qty="+pro_qty,

61.  Line 444, Column 22: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
62.  Line 444, Column 23: character “&” is the first character of a delimiter but occurred as data

     x=data.split("[&&]");

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
63.  Line 453, Column 36: document type does not allow element “span” here

     view1 ='<span class="grnSuc"><b>'+view+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
64.  Line 458, Column 34: document type does not allow element “span” here

    view1='<span class="grnSuc"><b>'+err+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
65.  Line 465, Column 36: document type does not allow element “span” here

    view1 ='<span class="redEror"><b>'+error+'</b></span>';

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements — such as a “style” element in the “body” section instead of inside “head” — or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML’s rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML’s “self-closing” tags for “meta” and “link” in the “head” section of a HTML document may cause the parser to infer the end of the “head” section and the beginning of the “body” section (where “link” and “meta” are not allowed; hence the reported error).
66.  Line 556, Column 22: character “<” is the first character of a delimiter but occurred as data

    if (topmenuTopPos < -100)

    This message may appear in several cases:

    • You tried to include the “<” character in your page: you should escape it as “&lt;”
    • You used an unescaped ampersand “&”: this may be valid in some contexts, but it is recommended to use “&amp;”, which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
67.  Line 707, Column 93: cannot generate system identifier for general entity “keyword”

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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 “&amp;” (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 &aelig; 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.
68.  Line 707, Column 93: general entity “keyword” not defined and no default entity

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
69.  Line 707, Column 100: reference not terminated by REFC delimiter

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
70.  Line 707, Column 100: reference to entity “keyword” for which no system identifier could be generated

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
71.  Line 707, Column 92: entity was defined here

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid…

72.  Line 707, Column 113: cannot generate system identifier for general entity “vendorid”

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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 “&amp;” (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 &aelig; 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.
73.  Line 707, Column 113: general entity “vendorid” not defined and no default entity

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
74.  Line 707, Column 121: reference not terminated by REFC delimiter

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
75.  Line 707, Column 121: reference to entity “vendorid” for which no system identifier could be generated

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
76.  Line 707, Column 112: entity was defined here

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

77.  Line 721, Column 100: reference not terminated by REFC delimiter

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
78.  Line 721, Column 100: reference to entity “keyword” for which no system identifier could be generated

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
79.  Line 707, Column 92: entity was defined here

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid…

80.  Line 721, Column 121: reference not terminated by REFC delimiter

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
81.  Line 721, Column 121: reference to entity “vendorid” for which no system identifier could be generated

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

    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.
82.  Line 707, Column 112: entity was defined here

    …ng/index.php?page=product/productviews&keyword="+keyword+"&vendorid="+vendorid;

83.  Line 770, Column 37: cannot generate system identifier for general entity “page”

           data: "product_id="+pro_id+"&page="+pagestat,

    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 “&amp;” (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 &aelig; 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.
84. https://www.upfan.net/2018/03/its-not-a-joking-more-than-400-bugs-with-inoutscripts-shooping-cart.html
    
    
    https://www.mail178.com/can-you-believe-it-514-bugs-with-inout-scripts-shopping-cart/
    
    
    http://onlinor.com/index.php/business/281-it-s-not-a-joking-514-bug-with-inoutscripts-shooping-cart
    
    
    https://baojii.com/news/show.php?itemid=193
    
    
    https://wordpress.com/post/talkscripts.wordpress.com/226