Huch? Dein Eintrag ist mir glatt entgangen, weil ich einen eigenen schrieb. Öhm. Ich persönlich halte das für ein Problem, dass diese Behandlung auf Plugin und Core offenbar verteilt ist. Das müsste eigentlich in den Core, oder? Sonst muss das ja jedes AntiSPAM Plugin reproduzieren, jedenfalls wenn ...

You should! I still think it is no good to disable it at all, even when having other Antispam plugins installed. I "should" not (as i don't need it) but I "have to" so it seems, if that really is the case. I think, this message handling should go to core so we are able to disabl...

I don't use the spamblock plugin ..

The comments are handled correctly and moderated indeed (by bee and bayes). I see them moderated in the admins comment list. So the handling is okay.

Only the user is not informed correctly about that fact and I wonder why.

Okay, that are valid arguments, of course.

So I switch my testing blog to PHP 5.4 and have a look, if everything's working. I have "master" installed there, so I can test a little more.

Only to mention this: For a client it should be better to use the XMLRPC Api of s9y. If you want to know how, you can have a look at the iOS Wordpress client. It's open source.

But if you want to comment only, POSTing is good enough, I think.

With 2k11 (but with bullet proof, too) I have the situation, that comments being moderated by AntiSpam plugins are shown as "your comment was successfully saved" (green) instead of "your comment needs moderation". As far as I remember, there once was such a message (moderation ne...

@Garvin: If 1.6.2 really behaves strange with PHP 5.4, shouldn't we do an update release to fix that problem?

P.S.: I run S9y 1.6.2 productive on PHP 5.3 and don't have these kind of errors there. These problems are from 5.4 on only as it seems.

dyfustic wrote:But why aren't those headlines shown at all if this happens, even with broken characters?

I guess the answer is simple: Because the DB delivers content containing UTF8 chars as empty when called "native", as it can't handle the content.

(Not that I know, but it seems logical).

Well.. No matter how long it takes: The XML should not report a newer version it can deliver, should it? :) Spartacus will deliver, after Garvins computer calculated the new XML files and updated them on GitHub. My first update check was only 2 minutes after this took place. Perhaps this was the mai...

There actually is some error mentioned in the plugin administration, just saying "error" for an event plugin. When I remove it, the error shows up for another plugin. I reinstalled the plugins, but does not change the original effect. Hmm. So there is something other "strange" (...

Same configuration here (nearly) and no problems with Umlaute in the headlines. So I don't think, it's a general problem. As the titles are in the database saved correctly (you see them in the editor), it's a displaying problem. My first guess would be: It's your template doing some strange stuff wh...

Huh? I have a very strange situation: Spartacus reports a new version of a plugin, I press update and it installs without any error message (all downloads green and the plugin file holding the version number is downloaded). When I check my plugins, the plugin still is the old plugin (with old versio...

Well in my case I only need "check for plugin updates". I don't care personally, if they are sidebar or event. If they are new: Update them!

If I understand your problem right, I can tell you what's the reason (it's an old and nasty problem I trapped in often before): If I understood it right how Spartacus is working, "Update Event Plugins" will check for all event plugins lying in a serendipity_event_* directory, "Update ...

Da das nichts mit S9Y zu tun hat, war hier im Forum auch nichts zu finden. Wie gesagt: ich habe einfach mal Google bemüht, der erste Fund hatte diese Erklärung.