Styles getting lost after saving

That's a new "Feature".

Info about ACF here http://docs.ckeditor.com/#!/guide/dev_advanced_content_filter-section-2

Jduty, it would be cool if you stopped advertising Advanced Content Filter as the culprit of all issues in CKEditor, really. We already know you are not a fan of this feature, which is fine, but I see no reason to confuse other users with suggestions such as this. ACF was introduced in CKEditor 4.1, so it can't really be blamed for digvijayun's problem in CKEditor 3.5...

Thats true, oopse. My bad.

So, whats the culprit in 3.5?

And as to not a fan, I could have been a fan if I haden't been blind sided by my code getting ripped out without any notice as to why and had to hunt for an answer for hours on end. Better docs, maybe a little snippit on the main page or even a clearly defined example ( easy to find, not barried in docs if there is one, I still can't fine one ) would have made the experience of upgrading to v4.1 not a nightmare.

I've been using CK ( or FCK if you will ) for 9 or 10 years. If I remember correctly we used it way back in the rainbow portal. I was a huge fan of this tool and if I can get past my current frustration I will be again. But everytime I find another "adjustmet" without documentation ( as far as I can find ) I get frustrated again. I'm not like most of your customers I'm not just slapping it in place and using it we have many custom plugins attached to a document management system of strictly formatted legal documents. These little "adjustments" have caused many hours of work. If you want fan boys running around shouting how cool your tool is then don't put "backward compatable" on it then break ALL of my plugins.

Toodles...

As a "documentation person" here I am really curious as to how you proceed with CKEditor updates that you somehow manage to skip all the documentation, notices, warnings etc.

What we did was:

• Since we were releasing a major version (which is visible in numbering) with a huge feature that broke backwards compatibility, we have decided to have a Release Candidate to give everyone plenty of time to get acquainted with the new feature and gather feedback. This was released along with a blog post that linked to full Developer's Guide documentation on ACF, and was clearly visible in the changelog. A new datafiltering.html sample was added to all CKEditor installation packages.
• When CKEditor 4.1 was released, another blog post followed. And even the CKEditor 4.0.3 release post contained a note stating that this is the "last CKEditor release without content filtering turned on by default."
• Around the CKEditor 4.1 release we also published some more materials on how to upgrade to CKEditor 4.1 and how to upgrade custom plugins and the documentation was further expanded.

If I remember correctly, *all* these texts explained how to turn the feature off. We also explained why we decided to turn it on by default (and this was not an easy decision to make, believe me -- to how many such situations with CKEditor can you point?).

All this information was also added on our social pages, including Facebook, Twitter and Google+.

So you had: a changelog, numerous blog posts (with RSS updates for anyone interested), social pages, developer's documentation, working sample with a few examples for different scenarios, API docs and, additionally, we tried to answer all ACF-related posts on the forum, in blog comments, on our social pages ASAP.

So my question is: what else would you expect? Replacing our website with a huge red notice "Beware of ACF in CKEditor 4.1!"? A flashing popup in each CKEditor installation? Where, do you think, lies the point where it is a developer's responsibility to check what he/she upgrades to, when CKSource can no longer be blamed for not providing enough information about a new feature? And please treat this as a serious question, we really want to learn from this situation and want to know how we can improve our communication in such cases.