There is no attribute prefix ошибка - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

Здравствуйте, помогите исправить ошибку я новичек, недавно только сайт создал. Валидаторе всего 1 ошибка.

Line 2, Column 14: there is no attribute

«prefix»

<html prefix= » og: http://ogp.me/ns#»xmlns=»http://www.w3.org/1999/xhtml» xml:l…

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.

Источник

Hi, just ran a report on my site www.in2town.co.uk and i received the following problems but i am not sure what they mean or how i solve them.

i used http://validator.w3.org/check?uri=in2town.co.uk

any help would be great.

Validation Output: 2 Errors

Error Line 1, Column 135: there is no attribute «prefix»

…xhtml1-transitional.dtd»><html prefix=»og: http://ogp.me/ns#» xmlns=»http://ww…

✉

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.
Error Line 7, Column 4411: there is no attribute «data-direction»

…2″ style=»width:100%;» data-direction=»ltr»><div class=»nspArts bottom» style=…

✉

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.
Warning Line 21, Column 1866: character «&» is the first character of a delimiter but occurred as data

…><span id=»module1286″>Lifestyle News & Features</span></h3><div class=»conten…

✉

This message may appear in several cases:
You tried to include the «<» character in your page: you should escape it as «<«
You used an unescaped ampersand «&»: this may be valid in some contexts, but it is recommended to use «&», which is always safe.
Another possibility is that you forgot to close quotes in a previous tag.

In2town Magazine is a popular magazine covering celebrity gossip, travel news, lifestyle news, gadget news and so much more. visit http://www.in2town.co.uk

Источник

Line 4, Column 9: document type does not allow element «HEAD» here
<head>
✉
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).

Line 8, Column 11: document type does not allow element «BODY» here
<body>
✉
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).

Line 10, Column 9: NET-enabling start-tag requires SHORTTAG YES
<br/>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.

This warning and related errors may also be caused by an unquoted attribute value containing one or more «/». Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

Line 12, Column 9: NET-enabling start-tag requires SHORTTAG YES
<br/>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.

Line 16, Column 17: NET-enabling start-tag requires SHORTTAG YES
<br/>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.

Line 19, Column 7: NET-enabling start-tag requires SHORTTAG YES
<br/>
✉
For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the «/» character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible «self-closing» tag, then you need to use XHTML or HTML5.

Line 21, Column 116: duplicate specification of attribute «TITLE»
…age» alt=»картинка отсутствует» title=»image» height=»200″ width=»300″ border…
✉
You have specified an attribute more than once. Example: Using the «height» attribute twice on the same «img» tag.

Line 23, Column 63: there is no attribute «HEIGHT»
…enter» border=»4″ width=»1356″ height=»768″ bordercolor=»blue» cellpadding=»1…
✉
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).

Line 23, Column 82: there is no attribute «BORDERCOLOR»
…width=»1356″ height=»768″ bordercolor=»blue» cellpadding=»10″ cellspacing=»0″>
✉
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).

Line 31, Column 58: document type does not allow element «P» here; missing one of «APPLET», «OBJECT», «MAP», «IFRAME», «BUTTON» start-tag
… <h3><p><strong>КиберФорум</strong> — компьютер…
✉
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>»).

Line 38, Column 19: end tag for element «P» which is not open
</p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 43, Column 76: there is no attribute «BODERCOLOR»
… <table align=»left» border=»2″ bodercolor=»green» width=»455″ height=»1000″>
✉
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).

Line 76, Column 75: required attribute «ALT» not specified
<img src=»https://www.cyberforum.ru/file base/navbits_start.gif» width=»20″ height=»20″>
✉
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>.

Line 77, Column 28: document type does not allow element «H3» here; missing one of «APPLET», «OBJECT», «MAP», «IFRAME», «BUTTON» start-tag
<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>
✉
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>»).

Line 77, Column 71: end tag for «H3» omitted, but its declaration does not permit this
<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, «start tag was here» points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Line 77, Column 25: start tag was here
<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>
Line 77, Column 71: end tag for «STRONG» omitted, but its declaration does not permit this
<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, «start tag was here» points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Line 77, Column 17: start tag was here
<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>
Line 79, Column 81: end tag for element «STRONG» which is not open
… Техподдержка — DevArt.Pro<h3></strong>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 80, Column 139: end tag for element «P» which is not open
…t» alt=»image not found» width=»90″ height=»50″ title=»Рейтинг на mail.ru»></p>
✉
The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

If this error occurred in a script section of your document, you should probably read this FAQ entry.

Line 83, Column 15: end tag for «H3» omitted, but its declaration does not permit this
</td>
✉
You forgot to close a tag, or
you used something inside this tag that was not allowed, and the validator is complaining that the tag should be closed before such content can be allowed.
The next message, «start tag was here» points to the particular instance of the tag in question); the positional indicator points to where the validator expected you to close the tag.

Line 79, Column 69: start tag was here
… Техподдержка — DevArt.Pro<h3></strong>
Line 107, Column 7: «HEAD» not finished but containing element ended
</html>
✉
Line 107, Column 7: end tag for «HTML» which is not finished
</html>
✉
Most likely, you nested tags and closed them in the wrong order. For example <p><em>…</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>…</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is «not finished», not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

<!DOCTYPE html PUBLIC «-//W3C//DTD HTML 4.01 Transitional//EN»>

<html>

<head>

<title> www.cyberforum.ru </title>

</head>

<body>

<br/>

<a target=»_blank» href=»https://www.cyberforum.ru»> <strong> www.cyberforum.ru </strong> </a>

<br/>

<br/>

<br/>

<tr>

<td>

<tr>

<td>

<p> <h1> <i> Cyberforum.ru </i> </h1>

<h3><p><strong>КиберФорум</strong> — компьютерный форум начинающих и

профессиональных программистов, системных

администраторов, администраторов баз данных.

Бесплатная помощь в <u><i>решении задач</i></u> по

программированию, решение проблем с компьютером.

</h3>

</p>

</td>

</tr>

</table>

<tr>

<td>

<p><strong>КиберФорум — компьютерный форум начинающих и

профессиональных программистов, системных

администраторов, администраторов баз данных.

Бесплатная помощь в решении задач по

программированию, решение проблем с компьютером.</strong></p>

</td>

</tr>

</table>

<tr>

</td>

</tr>

</table>

<tr>

<td>

<p><strong><h3>Powered by vBulletin® Version 3.8.7 PL2</p>

Техподдержка — DevArt.Pro<h3></strong>

</td>

</tr>

</table>

</td>

</tr>

</table>

Источник

0 Пользователей и 1 Гость просматривают эту тему.

5 Ответов
2049 Просмотров

Добрый день. Столкнулся с такой вот проблемой. Установил последнюю версию AdsManager (2.9.10). На главной странице объявлений компонент выходит за рамки шаблона. А на странице категории уже все в порядке. Кто-то сталкивался с такой ситуацией? Где-то читал, что пропущен div, но пропущенных не нашел. Прилагаю скрин

Может хоть кто-то сталкивался с подобным??

« Последнее редактирование: 25.04.2014, 11:24:43 от Siber »

Записан

Вам скрин в фотошопе помочь перерисовать?

Записан

«Жираф — это лошадь, выполненная по всем требованиям заказчика» (с) кто-то из дизайнеров

Проверка выявила след.ошибки:
-Line 2, Column 14: there is no attribute «prefix» — <html prefix=»og: http://ogp.me/ns#» xmlns:fb=»http://ogp.me/ns/fb#» xmlns=»ht…
-Line 4, Column 13: duplicate specification of attribute «xmlns:fb» — xmlns:fb=»http://ogp.me/ns/fb#»
-Line 90, Column 46: there is no attribute «data-excluded» — … type=’text/javascript’ data-excluded=’img.caption,.itemAuthorAvatar,.subCateg…
-Line 156, Column 66: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified — <div id=»gkContent» class=»gkMain gkCol gkPaddingTBLR» style=width:>
-Line 162, Column 54: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified — <div id=»gkComponentWrap» class=»gkMain » style=width:>
-Line 332, Column 145: there is no attribute «autocomplete» — …form_password1″ value=»» autocomplete=»off» class=»validate-password required»…
-Line 347, Column 42: reference to non-existent ID «jform_captcha» — <label id=»jform_captcha-lbl» for=»jform_captcha» class=»hasTip required» t…

В данных ошибках пропущенных тегов div не видно.
В первую очередь исправьте

style=width:>

Источник

`
$ echo $PATH

/usr/local/share/python:/usr/local/git/bin:/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/usr/bin/X11:/usr/local/bin/X11:/Users/I831533/bin:/opt/local/bin:/opt/xindice/bin:/opt/local/lib/postgresql84/bin:/usr/bin:/bin:/usr/contrib/bin:/sbin:/usr/sbin:/usr/lib:/usr/ucb:/usr/etc:/etc:/.pyenv/bin/:/usr/local/opt/go/libexec/bin:/Users/butch/Library/Python/3.7/bin:/usr/local/share/python:/usr/local/git/bin:/usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/usr/bin/X11:/usr/local/bin/X11:/Users/I831533/bin:/opt/local/bin:/opt/xindice/bin:/opt/local/lib/postgresql84/bin:/usr/bin:/bin:/usr/contrib/bin:/sbin:/usr/sbin:/usr/lib:/usr/ucb:/usr/etc:/etc:/.pyenv/bin/:/usr/local/opt/go/libexec/bin:/Users/butch/Library/Python/3.7/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:.:/Users/I831533/.platformio/penv/bin:/Users/I831533/src/esp_toolchain/xtensa-esp32-elf/bin:/usr/local/heroku/bin:/Users/I831533/.rvm/bin:.:/Users/I831533/.platformio/penv/bin:/Users/I831533/src/esp_toolchain/xtensa-esp32-elf/bin:/usr/local/heroku/bin:/Users/I831533/.rvm/bin

$ echo $PYTHONPATH

$ python —version
Python 3.7.4

$ pip —version
pip 8.1.1 from /Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg (python 2.7)

$ pip list
altgraph (0.10.2)
backports.ssl-match-hostname (3.5.0.1)
bdist-mpkg (0.5.0)
bonjour-py (0.3)
macholib (1.5.1)
matplotlib (1.3.1)
modulegraph (0.10.4)
numpy (1.8.0rc1)
paho-mqtt (1.1)
pip (8.1.1)
py2app (0.7.3)
pyobjc-core (2.5.1)
pyobjc-framework-Accounts (2.5.1)
pyobjc-framework-AddressBook (2.5.1)
pyobjc-framework-AppleScriptKit (2.5.1)
pyobjc-framework-AppleScriptObjC (2.5.1)
pyobjc-framework-Automator (2.5.1)
pyobjc-framework-CFNetwork (2.5.1)
pyobjc-framework-Cocoa (2.5.1)
pyobjc-framework-Collaboration (2.5.1)
pyobjc-framework-CoreData (2.5.1)
pyobjc-framework-CoreLocation (2.5.1)
pyobjc-framework-CoreText (2.5.1)
pyobjc-framework-DictionaryServices (2.5.1)
pyobjc-framework-EventKit (2.5.1)
pyobjc-framework-ExceptionHandling (2.5.1)
pyobjc-framework-FSEvents (2.5.1)
pyobjc-framework-InputMethodKit (2.5.1)
pyobjc-framework-InstallerPlugins (2.5.1)
pyobjc-framework-InstantMessage (2.5.1)
pyobjc-framework-LatentSemanticMapping (2.5.1)
pyobjc-framework-LaunchServices (2.5.1)
pyobjc-framework-Message (2.5.1)
pyobjc-framework-OpenDirectory (2.5.1)
pyobjc-framework-PreferencePanes (2.5.1)
pyobjc-framework-PubSub (2.5.1)
pyobjc-framework-QTKit (2.5.1)
pyobjc-framework-Quartz (2.5.1)
pyobjc-framework-ScreenSaver (2.5.1)
pyobjc-framework-ScriptingBridge (2.5.1)
pyobjc-framework-SearchKit (2.5.1)
pyobjc-framework-ServiceManagement (2.5.1)
pyobjc-framework-Social (2.5.1)
pyobjc-framework-SyncServices (2.5.1)
pyobjc-framework-SystemConfiguration (2.5.1)
pyobjc-framework-WebKit (2.5.1)
pyOpenSSL (0.13.1)
pyparsing (2.0.1)
pyserial (3.1.1)
python-dateutil (1.5)
pytz (2013.7)
requests (2.11.0)
scipy (0.13.0b1)
setuptools (18.5)
six (1.4.1)
socketIO-client (0.7.0)
vboxapi (1.0)
websocket-client (0.37.0)
xattr (0.6.4)
You are using pip version 8.1.1, however version 19.2.1 is available.
You should consider upgrading via the ‘pip install —upgrade pip’ command.

$ pip3 —version
/usr/local/Cellar/python/3.7.4/Frameworks/Python.framework/Versions/3.7/lib/python3.7/distutils/init.py:15: UserWarning: The virtualenv distutils package at %s appears to be in the same location as the system distutils?
warnings.warn(«The virtualenv distutils package at %s appears to be in the same location as the system distutils?»)
pip 19.1.1 from /usr/local/lib/python3.7/site-packages/pip (python 3.7)

$ pip install —upgrade pip
Collecting pip
Using cached https://files.pythonhosted.org/packages/62/ca/94d32a6516ed197a491d17d46595ce58a83cbb2fca280414e57cd86b84dc/pip-19.2.1-py2.py3-none-any.whl
Installing collected packages: pip
Found existing installation: pip 8.1.1
Uninstalling pip-8.1.1:
Exception:
Traceback (most recent call last):
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/basecommand.py», line 209, in main
status = self.run(options, args)
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/commands/install.py», line 317, in run
prefix=options.prefix_path,
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/req/req_set.py», line 726, in install
requirement.uninstall(auto_confirm=True)
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/req/req_install.py», line 746, in uninstall
paths_to_remove.remove(auto_confirm)
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/req/req_uninstall.py», line 115, in remove
renames(path, new_path)
File «/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/pip/utils/init.py», line 267, in renames
shutil.move(old, new)
File «/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py», line 300, in move
rmtree(src)
File «/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py», line 247, in rmtree
rmtree(fullname, ignore_errors, onerror)
File «/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py», line 252, in rmtree
onerror(os.remove, fullname, sys.exc_info())
File «/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/shutil.py», line 250, in rmtree
os.remove(fullname)
OSError: [Errno 13] Permission denied: ‘/Library/Python/2.7/site-packages/pip-8.1.1-py2.7.egg/EGG-INFO/PKG-INFO’
You are using pip version 8.1.1, however version 19.2.1 is available.
You should consider upgrading via the ‘pip install —upgrade pip’ command.
`

Looks like there is an issue with pip (python is version 3, pip is version 2, pip3 seems FUBAR).

[Sorry, entering code doesn’t seem to be working for me.]

Источник