By larry on

Ok,
99.99999999999% of the time contributed modules on Drupal work...the htmlwrap.module is the exception to this rule. It's happily sitting in the 4.7 releases and I do not know why. Perhaps, I'm wrong on this but I doubt it. When I install the module and turn on the filter, the site is inaccessible. I literally must remove the module itself from the modules directory in order to get my site back.

Has anyone gotten this to work on 4.7.3? If not, are there any alternatives? I don't want to be at the mercy of some joker fiddling with my template.

thanks,

larry

⋅ Categories: Drupal 4.7.x

Comments

vm’s picture

vm commented

I just installed this module to try and confirm. I cannot. My installation went perfectly well. I enabled the module, then enabled the input filter for htmlwrap.

maybe its a conflict with another module ? or filter ?

larry’s picture

larry commented

Hello Kenn,

That being the case, the issue must be with me on my setup. Looks like it's time for me to go through the variables table and fiddle with the enabled modules/filters. Thanks for checking it over for me. It's much appreciated.

cheers,

larry

--There are no Kangaroos in Austria--

dman’s picture

dman commented

If you Check the issues you will see that there is a known problem.
Looks to me like the regular expression being used may be eating itself. Always a danger with lookaheads.
Doesn't look like anyone's tried to fix it for a while tho.
You'll need to narrow it down to just what chunk of input triggers it. Nobody can solve the problem if they can't replicate it.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards

larry’s picture

larry commented

Hello .dan.,

I thank you for your reply. Actually, I did check the issues page and saw that there were indeed problems with this module, which is why I posted this thread. I wanted to see whether others still had the same problem as the issues page is rather old for this module with 0 progress having been made on the known issues.

Your idea about the regexp is interesting and I appreciate it. You are totally correct, if others can't replicate the problem it can't be fixed. If that's the case, the problem must be with me on my setup. I'll pound my head against the computer a bit more and see what comes of it...thanks again.

cheers,

larry

--There are no Kangaroos in Austria--

dman’s picture

dman commented

It's likely not your setup so much as the actual content of the node body string that will be triggering the error.
Try pasting just bits into a new node until you find the line that kills it. International characters of course may be problematic, or it may be something simple like a $ sign.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards