13 Bugs Found at Inout Scripts Socialtiles

20 months ago, I spent $447 buying Inoutscripts Socialtiles and its addons, but found nothing is working. They did not solve any issues and refused to refund me. In addition, I lost a lot with hosting. I checked online, there are 13 bug with this script. The below is the details of its coding bugs.

  1. Warning Line 73, Column 25character “<” is the first character of a delimiter but occurred as data
    			  if (opera.version()<11){

    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.
  2. Warning Line 82, Column 17character “<” is the first character of a delimiter but occurred as data
    		 if (ffversion<5){

    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.
  3. Warning Line 149, Column 10character “<” is the first character of a delimiter but occurred as data
    		if (num<5){

    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.
  4. Error Line 236, Column 87document type does not allow element “div” here; missing one of “object”, “applet”, “map”, “iframe”, “button”, “ins”, “del” start-tag
    …s://shensor.com/social/index.php?page=index/index"><div class="logo"></div></a>

    The mentioned element is not allowed to appear in the context in which you’ve placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you’ve forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as “<p>” or “<table>”) inside an inline element (such as “<a>”, “<span>”, or “<font>”).

  5. Error Line 242, Column 52there is no attribute “data-reveal-id”
    …lass="sign_up jpclick" data-reveal-id="myModal" data-animation="none">SignUp</…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  6. Error Line 242, Column 77there is no attribute “data-animation”
    …ass="sign_up jpclick" data-reveal-id="myModal" data-animation="none">SignUp</a>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  7. Error Line 428, Column 163there is no attribute “onSubmit”
    …or.com/social/index.php?page=index/login" onSubmit="return verifyForm_login()">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  8. Error Line 437, Column 92there is no attribute “placeholder”
    …name"  id="username"  class="text username_input" placeholder="用户名" value="" />

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the “Strict” document type with a document that uses frames (e.g. you must use the “Transitional” document type to get the “target” attribute), or by using vendor proprietary extensions such as “marginheight” (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  9. Warning Line 726, Column 9character “<” is the first character of a delimiter but occurred as data
    	if (num<5){

    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.
  10. Warning Line 772, Column 18character “&” is the first character of a delimiter but occurred as data
    	if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )

    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.
  11. Warning Line 772, Column 19character “&” is the first character of a delimiter but occurred as data
    	if ( ( !start ) && ( name != document.cookie.substring( 0, name.length ) ) )

    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.
  12. Error Line 802, Column 7end tag for “div” omitted, but OMITTAG NO was specified
    </body>

    You may have neglected to close an element, or perhaps you meant to “self-close” an element, that is, ending it with “/>” instead of “>”.

  13. Info Line 256, Column 1start tag was here
    <div class="mainBoard">

 

2 comments

  1. laker Reply

    You should never purchase the Inout Scripts. These scripts are full of issues, and they’ll never refund you a penny. Avoiding Inoutscripts and the scammers is avoiding loss of your money. They said: “Premium e-Commerce platform with Multi-Vendor capability. Start your own online shopping cart with multiple sellers, brands, categories in any currency. Sell physical or digital products in cyberspace to any buyer around the world. Inout Shopping Cart is far more than a storefront to sell your products. You can turn your ecommerce platform into a fully diverse multi-vendor shopping portal. More vendors, more buyers.” I purchased this inout script one year ago, but I had to give up finally. Why? There are 8 bugs and 23 warnings by code checking. The Cronjob data had never been renewed. The database was attacked 3 times. The technique support never solved the issues. They always blamed the servers, even though the servers were properly set up, and did not have errors by third party organization. The site and its owner would be sued by vendors at any time. It was a potential loss of huge money.

  2. donald Reply

    Inout search google theme is another scamming plugin, since the core files are not working at all. It’s not a search engine, but a meta tool.

发表评论

电子邮件地址不会被公开。 必填项已用*标注

Sections

Shows

Local News

Tools

About Us

Follow Us

跳至工具栏