Closed (fixed)
Project:
External Links Filter
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Apr 2010 at 13:14 UTC
Updated:
29 Jan 2014 at 17:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
xanoCan you show what text you were trying to post?
Comment #2
troybthompson commentedI'm having the same problem. HTML attached. Using the 4/26 version.
Comment #3
bennos commentedthis was just in the watchdog for a older node.
Have installed boost, and the node could be requested via boost.
will try it out, with a normal node request.
Comment #4
xanoI need a way to reproduce the error.
Comment #5
troybthompson commentedIt looks like it's having issues with the line 26 in my upload with the CDATA slashes, etc at the beginning of the google analytics code in the header.
Comment #6
xanoCan you post some code to reproduce the error?
Comment #7
troybthompson commentedI'd be happy to post something if you can be more specific what you need. The full html of the page is in post #2 and the error is referencing line 26.
Comment #8
xanoI want to know what piece of code causes the error. An entire page isn't useful, because that isn't what you filled in for the node body.
Comment #9
troybthompson commentedOk, I finally had time to do process of elimination on a test page to narrow down the problem. It happens when there's an ampersand inside the linked text (local, not external)
So the link "Special Offers & Coupons" gives the error:
* warning: DOMDocument::loadHTML() [domdocument.loadhtml]: htmlParseEntityRef: no name in Entity, line: 1 in /usr/www/users/cmcvb/sites/all/modules/elf/elf.module on line 128.
* warning: DOMDocument::loadHTML() [domdocument.loadhtml]: htmlParseEntityRef: no name in Entity, line: 1 in /usr/www/users/cmcvb/sites/all/modules/elf/elf.module on line 128.
but if I changed it to "Special Offers and Coupons" the error went away.
Does that help?
Comment #10
xanoThanks! I think I know the reason for the error to pop up. However, this is another error than the one in the first post of this issue. I tried reproducing that by submitting invalid HTML, but I got no errors during that quick test.
Comment #11
xanoThe problem in #9 should no longer occur now that #787980: Encoding Issues is fixed. Can we focus here on errors due to invalid markup?
Comment #12
elally commentedsubscribe
Comment #13
drupdruppalpal commentedsame error:
warning: DOMDocument::loadHTML() [domdocument.loadhtml]: Unexpected end tag : p in Entity, line: 1 in /.../sites/all/modules/elf/elf.module on line 129.
i've already patched #787980: Encoding Issues but the error went away too
regards
Comment #14
skizzo commentedAdding a empty block to a views-generated page I don't see this error. As soon as I add
<A href="http://drupal.org">drupal</A>to the block body (in content region) I get the following error
warning: DOMDocument::loadHTML() [domdocument.loadhtml]: Unexpected end tag : p in Entity, line: 2 in /var/www/drupal/sites/all/modules/elf/elf.module on line 129.The block uses a custom input format which includes the following filters, in that order:
- URL filter
- Line break converter
- BBCode
- Collapse text
- Add an icon to external and mailto links
- HTML corrector
Comment #15
hedac commentedwhy is this module needing to perform a validation in html ?
I think it is not needed.. and generates warnings...
I got this today
* warning: DOMDocument::loadHTML(): AttValue: " expected in Entity, line: 1 in /home/wwwdrupal/sites/all/modules/elf/elf.module on line 129.
* warning: DOMDocument::loadHTML(): Couldn't find end of Start Tag img in Entity, line: 1 in /home/wwwdrupal/sites/all/modules/elf/elf.module on line 129.
Comment #16
matulis commentedUse @ to suppress warnings
Comment #17
brad.bulger commentedContrary to #11, I am getting the same errors using 6.x-3.x-dev as described in #9. It doesn't seem like this is something that can be prevented, only hidden by suppressing errors as matulis suggests in #16, or maybe by using the libxml_use_internal_errors() function in some fashion. We've been avoiding upgrading this module from 2.1 because of just these kinds of problems, it still seems like the new approach is problematic.
specifics: loadHTML() of this text
causes the error
DOMDocument::loadHTML(): htmlParseEntityRef: no name in Entity, line: 1UPDATE: actually it does seem like suppressing the errors is probably the way, given that that's what Drupal 7.x Filter module is doing
Comment #18
mrded commented@matulis Thank you :)
Comment #19
mrded commentedComment #20
WorldFallz commentedAs of #1261568: Incompatible with PHP versions below 5.3.6, the module is using the drupal wrapper function so this should no longer be an issue for 7.x. If anyone wants to submit a patch for 6.x-3.x please open a new issue.