This was mainly the not checked thumbnail_name and needed to be silenced too.
I am not sure id that issue can happen with type 'file' renaming too.
References #220
Don't show the select form on install, where there are no categories anyway, and disable the "Show All Categories" link by default, since he is on normal configurations redundant with the frontpage
Before this, ckeditor was configurable by editing the wysiwyg_init.tpl in 2k11/admin. Now, the flow is like this:
1. wysiwyg_init.tpl is responsible for initializing the editor and the plugins
2. we provide a htmlare/ckeditor/serendipity_config.js where we specify a sane default configuration, including a small toolbar without harmful elements
3. if the user wants to overwrite our configuration upgrade-safely, he can do this in htmlare/ckeditor/userconf.js
Inter alia removes the ALL option, which "resets" the selection.
As a Smarty only fix, this will now circumvent the ALL logic in plugins.inc.php
Reference #200
This is a – possibly temporary - fix. serendipity_editor.js depends
on this file, so it needs to be included in the preview iframe as
well.
See http://board.s9y.org/viewtopic.php?p=10440336 (German only) for
further info on the issue this is related to.
In order to be able to call `serendipity_plugin_api_pre_event_hook` in a template's config.ini.php from serendipity.css.php, Smarty must be initialized first.
In case of a 'css' event, within the event hook $eventData contains the template's CSS which can now be manipulated and/or extended.
Some plugins make use of additional entry properties (title, body, extended, author) after being called by the 'backend_publish' hook, e.g.
* serendipity_event_forum
* serendipity_event_freetag
* serendipity_event_ljupdate
* serendipity_event_trackback
* serendipity_event_versioning
* serendipity_event_entryproperties
* serendipity_event_mailer
* serendipity_event_twitter
Thus we need to set these properties in the serendipity_updertEntry() method to make sure the plugins get the required data. Of course, we could fetch the entry either in overview.inc.php or again in each plugin, but that would mean an additional query to the DB.
When no categories are delivered to serendipity_updertEntry this can mean two things:
- categories need to be un-assigned
- categories where not addressed/fetched/passed to the function [see include/admin/overview.inc.php for publishing a post! Or plugins like freetag, using serendipity_updertEntry]
To address this a new serendipity[had_categories] is added to the backend template, which can be checked for.
Feedback appreciated!
