Closed (fixed)
Project:
Comment bury/promote
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Sep 2008 at 13:51 UTC
Updated:
8 Oct 2008 at 17:12 UTC
I get the following error(s) on any page with a buried comment.
* warning: preg_replace() [function.preg-replace]: Compilation failed: missing terminating ] for character class at offset 2 in /modules/comment_bury_promote/comment_bury_promote.module on line 411.
* warning: preg_replace() [function.preg-replace]: Compilation failed: missing terminating ] for character class at offset 2 in /modules/comment_bury_promote/comment_bury_promote.module on line 412.
This is only when I leave the disemvowelling field empty. But the disemvoweling only seems to work for the subject and not the body. I think this is because I'm using FCKEditor as my wysiwyg, and something is screwing up.
Comments
Comment #1
mercmobily commentedHi,
Hummm interesting.
Are you ticking "disemvoweling" checkbox, though, and leaving the setting "Letters that will be killed in buried comments " empty? I don't think the module is meant to work like that -- you have to specify some letters if you turn it on!
Pleasel et me know :-D
Merc.
Comment #2
jazzdrive3 commentedI have the box checked and then nothing in the disemvowel box, as per the instrucitons on the admin page itself that says to do that if you just want to delete the comment body. I only tried that because disemvoweling wasn't working at all. Nothing in a buried comment was changing. Only the subject changed. It seemed to work before I enabled a wysiwyg editor as default for users. Maybe the parser isn't working with
tags that are inserted? Not sure.
Comment #3
mercmobily commentedHi,
Very strange.
OK, let's try this. What if you change:
Into:
...? Does it work with this?
Merc.
Comment #4
jazzdrive3 commentedThat worked.
Thanks!
Comment #5
mercmobily commentedHi,
Excellent.
Keep the patch -- I've committed the code, so your updates will be in sync.
Merc.
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.