with the new editor an all, is this option that’s available on IPS4 still present on IPS5?

on IPS4 it can be found Customization → Editor → Settings → Advanced

You cant add html on the editor, so not sure what purpose that would actually serve. What is it you are trying to achieve with this, first of all? We can then see if we can point you in the right direction

It’s available as a development setting for an application. Developer Center > (your application) > Front-End > Parser Settings.

we currently use some pre-defined css classes for unique messages and buttons. wondering if this will be available on the new version.

Take a look at the following, which shows how the new editor works

so this means that any css classes we use will be removed by default? but if we create an extension for it then we can bring the functionality back?

Now, you may be thinking, "like the editor itself, won't the server side HTML Parser will strip any content that is not whitelisted"? Well, the answer is yes and we added a new AdminCP Dev Center tool to create Parser Whitelist Rules inside Invision Community Apps (again more on all this later). With the coupling of the Parser Whitelist and Editor Extensions, admins can rest assured that their editors will just "work" when you install Extensions.

44 minutes ago, David.. said:

so this means that any css classes we use will be removed by default? but if we create an extension for it then we can bring the functionality back?

Yes that is correct, the HTML attributes supported by the editor are strictly defined, but creating an editor extension to apply Formatting Marks or wrap content inside a Containing Node should allow you to support the class names you’ve been using

19 minutes ago, Matt Finger said:

Yes that is correct, the HTML attributes supported by the editor are strictly defined, but creating an editor extension to apply Formatting Marks or wrap content inside a Containing Node should allow you to support the class names you’ve been using

thank you for clearing that up! will this retroactively remove from older ips4 posts too? or only when edited?

2 minutes ago, David.. said:

thank you for clearing that up! will this retroactively remove from older ips4 posts too? or only when edited?

It only takes effect when edited

A non-dev solution to maintain this more easily would be really good. Because it was so simple to add buttons and custom classes in 4.x, many IPS admins will have used this, but just a fraction of them will be devs who can move this stuff to an app.