Now we know: Don is a SPAMmer... , since ix.dnsbl.manitu.net is a serious RBL by heise.de! A very trustable service here, over the pond! These S9y spamblock Plugins do not report this to any RBL, ... as far as I know (but maybe Uberspace listens on mail() somehow?).

if (strpos($eventData, '.serendipity_BlahBlah') === false) { $this->addToCSS($eventData); } or if (strpos($eventData, '.serendipity_BlahBlah') === false) { $eventData .= 'fake example for the styles you wish to append'; } I normally do for 2.1 cases if (version_compare($serendipity['version'], '2.0...

For me it does not make sense to push everything to streamed serendipity.css! There are special plugin cases, where we have little CSS only, which is easy to add, say append to the serendipity.css $eventData. In other more extended cases, this just blows up that file. Then a secondary css file added...

yellowled wrote:add it to master in /templates/default/style_fallback.css so that we can remove fixchrome.css from the plugin once 2.1 is released

No. We can't do this for compat. But we can write a condition for >= 2.1 to not use it.

Great! Was this a matter of an updated webkit? Or does it even work with "older" webkit engined Browsers (lets say ~1 year old...)?

I cannot answer this, since it is something like before DOM, while DOM and after DOM manipulating. It expects something set or not set, to start working.

It was an easy to use approach having it like this ... and remember, I only did that by request!
I see the issue with end of month. But fetching future events here takes a little more work and is woth some pennies. I am not sure I want to spend this....

Don, the all categories link is set, when you use that option. But I found a style.css restriction which removes the view. In my template it looked like #contactform .serendipity_commentDirection, .category_link_all a { display: none; } Better check your template for something like this and remove ,...

Fifth: Do what I did testwise.
Take what we have already and use it in a new plugin. Shall I paste that testwise to 2.1 plugins?

and we will have to use this in the same function adding the "!isset($month)".

I also managed to re-add the "by week" archive (#serendipity_plugin_archives) option again. function serveArchives() { global $serendipity; $serendipity['view'] = 'archives'; $_args = locateHiddenVariables($serendipity['uriArguments']); + foreach ($_args AS $k => $v){ + if ($v[0] == 'W') {...

Yes, but related. MultiAuthor is the serendipity_plugin_authors Plugin. Nothing broken.
If you acticate it for the frontend sidebar (before your removements in it), you are able to select entries by authors or multiAuthors, like suggested in the diffs.

Thanks for comming up with that, Don! I also had in my mind that this removement commit https://github.com/s9y/Serendipity/commit/55ae435c898bfcff1a4722a34e25116188a1079c was at least, ... lets say "suspicious". Now I remembered to give it a try. Using the "old" Serendipity index...

- Wenn ich ein normaler Redakteur bin sehe ich im Dashboard nur die Kommentare zu Einträgen, die ich selber erstellt habe. Alle Einträge, die ich sehe, kann ich bearbeiten. - Wenn ich ein Chefredakteur oder Admin bin, sehe ich im Dashboard die Kommentare zu allen Einträgen, egal von wem die stammen...

Das ist auch nicht ganz so einfach..., denn die Einstellungen werden grundsätzlich im sidebar plugin gemacht und dann vereinzelt per interner Übergabe an das event Plugin weitergereicht und auch dort noch als spezielle event config Einstellungen gespeichert. Sind das zwei separate Installationen? Ab...