Serendipity Forums

If I want to send a comment in my blog (recently updated to 1.7-rc3), I get the error message below.

I get the same exception when I call the options of the spamblock-plugin in the backend.

Fatal error: Uncaught exception 'ErrorException' with message
'Serendipity error: preg_match(): Compilation failed: missing
terminating ] for character class at offset 7' in
/home/hanno/websites/hboeck.de/htdocs/include/compat.inc.php:118
Stack trace:
#0 [internal function]: errorToExceptionHandler(2, 'preg_match():
C...', '/home/hanno/web...', 1500, Array)
#1 /home/hanno/websites/hboeck.de/htdocs/plugins/serendipity_event_spamblock/serendipity_event_spamblock.php(1500):
preg_match('@([url=)@i', 'So sieht es aus...', Array)
#2 /home/hanno/websites/hboeck.de/htdocs/plugins/serendipity_event_spamblock/serendipity_event_spamblock.php(1080):
serendipity_event_spamblock->wordfilter('/home/hanno/web...', Array,
NULL, Array)
#3 /home/hanno/websites/hboeck.de/htdocs/include/plugin_api.inc.php(1073):
serendipity_event_spamblock->event_hook('frontend_saveCo...',
Object(serendipity_property_bag), Array, Array)
#4 /home/hanno/websites/hboeck.de/htdocs/include/functions_comments.inc.php(1002):
serendipity_plugin_api::hook_event('front in
/home/hanno/websites/hboeck.de/htdocs/include/compat.inc.php on line
118

Hi

Strange!
Did you add content filter stopwords to spamblock?
How does it look like?
Maybe it is even more weired and you have an error occuring in spamblock (1.79) because of an error in freetag plugin.
Did you upgrade your plugins before updating Serendipity to 1.7 RC3? Also flattr needs an upgrade..

Hi!

It c ould help to set $serendipity['production'] = true in your serendipity_confg_local.inc.php - that should revert the error reporting to a more minimal one. Then you should be able to access the spamblock configuration and fix the regular expressions in the content filter; I guess there are some non-escaped characters like [ and ] in one of the filters.

HTH,
Garvin

I just tried uninstalling and reinstalling the spamblock-plugin and all its options and the problem persists. So I don't think there's anything wrong with the config.

Garvin, setting production to true makes it work again, however in the backend I get this warning:
Warning: Invalid argument supplied for foreach() in /home/hanno/websites/hboeck.de/htdocs/plugins/serendipity_event_spamblock/serendipity_event_spamblock.php on line 223

You now updated your plugins. Did you ever add own content filter stopwords to spamblock? (Inside the content-filter collapsible box) -The values are stored in the database. So, if you ever did (and maybe unescaped ones) they would still be there.

The errors reason may also be somewhere else or a mixture of different constellations.

What PHP environment do you use (modul cgi, fcgi)?
Are there any specials in the Server environment and configuration?
Do you use the serendipity_event_karma Plugin?
(I do ask this, since you now have lots of errors which is the and karma is making use of it.)

I checked and during I had the spamblock-plugin off, all settings were removed from the database. So I hoped I've resetted the plugins options with that.
I think I once set manual keywords, but I think they should be gone now. Where are they stored in the database so I can check?

I have:
* mod_fcgid, apache 2.2, php 5.4, nothing very special in server configuration
* No karma-plugin

You don't have access to the input field in spamblock config because of the error?

They are stored in the *_config table:
serendipity_event_spamblock:hash/contentfilter_authors
serendipity_event_spamblock:hash/contentfilter_emails
serendipity_event_spamblock:hash/contentfilter_urls serendipity_event_spamblock:hash/contentfilter_words

Edit:
The "Illegal string offset 'properties'..." errors will likely come from freetag, which might as well be a "flushing follow" error, since spamblock produces this "missing terminating ] for character class" error.

The 1.7-RC3 Line error 1634 is the same line, like in current plugin_api.inc.php file, line 1625. This issue is fixed for upcoming Serendipity 1.7.4.
See Garvin note in viewtopic.php?f=3&t=19492&start=15 ff, to self fix. Thanks.