Samples for basics makes no sense

[Piotr Jasiun]

When you open samples in basics preset some (most) of them does not work properly (as described). In example:

• Toolbar Configuration: there is long list of toolbarGroups and everything what user see are 9 buttons (​http://dev.ckeditor.com/ticket/10338),
• ENTER Key Configuration: DIV mode doesn't work,
• Using CKEditor JavaScript API: "set editor content" doesn't set expected content (no H2 tag),
• Replace DIV with CKEditor on the Fly: when you start editing any part, the header is changed to standard text so the content is modified event if you do nothing,
• Data Filtering and Features Activation: this sample does not make much sense at all,
• Inline Editing by Code: content looks terrible (there should be different content),
• Full Page Editing: how I can use it (check it) in basics preset?

This is only small list for basic preset and there could be similar problems for standard. I think that for a user who just want to check how basics editor works all of this things look like bugs.

[Piotrek Koszuliński]

There was also a ticket in which we were working on an alert box with information that in given configuration some content was stripped from editor by the ACF. This is especially important for custom CKEditor builds where we don't have any control over what will be displayed. I cannot find the ticket though.

[Wiktor Walc]

The other ticket: #10228

Keep in mind that we're not talking about just a Basic package. Samples must be valid for each custom package, including e.g. a preset with Image plugin removed etc.

A simple features detection that shows/hides/modifies certain parts of a sample would do the trick I guess.