This is tested in all Browsers I can reach (Firefox, Chrome, IE) and works fine with current 2.0 beta5 checkouts and the Serendipity 1.7 Series. Ever noted any Chrome issues in changelog or this thread were fixed or removed. And I never
noted to not use Chrome browser for using CKEditor in general.
Czorneboh wrote:The 2 points beneath the yellow (or ochre) marked text are fullfilled. The plugin is the 2nd last in the plugin list. The last is the extended properties plugin.
And the wysiwyg option in "Eigene Einstellungen" is activated. else you would not have the cke in staticpages, I assume.
Czorneboh wrote:yellow marked text says: deactivate body, extended and nugget parsing global in NL2BR plugin or/and entry via entryproperties.plugin and / or for static pages.
NL2BR is not in my plugin list.
In the entryproperties-plugin I did not found the place, where I can switch off the parsing, as told in the installation hint.
Well, if the nl2br is not istalled and activated, it will for sure not be
in the entryform entryproperties select list: "Formatierungs-PlugIns für diesen Eintrag deaktivieren", or needs to be de-formated in staticpages.
Czorneboh wrote:One of my installed plugins is "serendipity_event_xhtmlcleanup".
Perhaps this has an influence?
If you hold that as possible, I will next tell you my settings of that or I can deactivate it yet.
I myself don't use it. But no, I don't think that it may stop ckeditor to open up in entryforms. About other influences for text parsing you will have to see yourself.
Czorneboh wrote:I use s9y 1.7.8 on php 18.104.22.168 +squeeze xx (do not know what that "squeeze" does mean)
This is Debian. Debian takes packages from php.net until the version development, here named squeeze, got freezed. Behind this date it sticks to this version - like in this case 5.3.3 - then the squeeze revision .7, but all further security and other package fixes go to the next cipher(s) https://packages.debian.org/search?keywords=php5
So this is a kind of versioning.
Now, back to the issue:
Czorneboh wrote:I prooved, if the wysiwyg-editor is visible. No, it is not. Now in the article writing scope there is no more editor active.
All Browsers mentioned have a development tool on board called by keyboard F12
Now, open up the console and reload you entryforms backend page. Then you should see any errors preventing cke to show up.
I expect it is another plugin, like autosave, or something else, which produces an error and halts the follow up loads. The autosave plugin is known for a long time to not work with any WYSIWYG-Editors, producing js errors, halting the system.