Timbalu wrote:I am going to change this ...
No, sorry!
Well, the bad thing about this is the following, let me resume:
I thought I could easily avoid this behaviour by
not using the third parameter (force_frontend_fallback).
And I forgot to remember, that this will not work, since '
2k11' or the '
default' (dir) theme will
always be in the Serendipity fallback line. This is a
general behaviour ([0] "user"-theme - [1] "default"-theme - [2] "standard"-theme) which is much more
vital for the system than the user.css file includement and having to overset (0) or remove an already stated file in (1)
or 2.
We could have had decided to output the user.css file by
- not using serendipity_getTemplateFile() as it was before, since we had it called by {$serendipityHTTPPath}templates/{$template}/user.css
(but decided to automatically include the user.css file with 2.0.1) or
- by manipulating serendipity_getTemplateFile() for the users.css fallback cases.
The latter was the thing we decided
not to do, since that would cost performance in this central function.
Since we knew this was something at least
unexpected and now a need to give away into the users responsibility, we wrote this:
https://github.com/s9y/Serendipity/blob ... /NEWS#L185 (see first & last sentence)