22 hours ago, Gary said:

Hi @H5K,

There is a Raw HTML widget you can add when clicking on your display name/picture → Page Editor → search for HTML and it will pop up. Drag and drop the widget onto your community and away you go.

You can add the widget to any page on your community. I use the Pages and Commerce applications and both allow me to add this widget. If you are using the WYSIWYG Editor on a page for example, then no, source/raw HTML cannot be used within it.

Yes I am talking about the editor.

The IPV5 TipTap editor allows HTML in forum posts/comments but there is no functionality to enable the same for articles or article comments.

On 7/11/2025 at 3:47 PM, opentype said:

There should be an assistant to recreate the button functionality of 4.x, which creates the necessary code automatically in the background.

Absolutely!

On 7/12/2025 at 3:50 AM, H5K said:

Yes I am talking about the editor.

The IPV5 TipTap editor allows HTML in forum posts/comments but there is no functionality to enable the same for articles or article comments.

I probably misunderstand,* but in the Page Editor: Pages > Raw HTML

* I probably do misunderstand, since there is nothing like that in the posts editor.

I want to be on record as saying, I really despise this new editor. It causes me nothing but fits.

7 hours ago, My Sharona said:

I want to be on record as saying, I really despise this new editor. It causes me nothing but fits.

Ok.

It would be more useful if you could tell us what problems you're having though (outside of HTML editing because, that has been discussed a lot already).

Hhhm, daft question but where's the spoiler button?

What happens to existing spoilers created in IPS4 upon upgrading to IC5?

14 hours ago, My Sharona said:

I want to be on record as saying, I really despise this new editor. It causes me nothing but fits.

It may be a developer's wetdream, but it seems unfriendly for average users.

Click the plus, then click on "Wrap in box".

Click for more

Once you have done that, there is a settings button where you can click to make it expandable :)

Thanks! That's not very user friendly for average users to figure out the process, why not simply add a spoiler button?

Edited July 18, 2025Jul 18 by The Old Man

51 minutes ago, The Old Man said:

Hhhm, daft question but where's the spoiler button?

https://invisioncommunity.com/forums/topic/482354-any-idea-how-to-add-a-spoiler-button-to-the-post-builder/#findComment-2995463

How can I use HTML with this new editor?

3 hours ago, 403 - Forbiddeen said:

How can I use HTML with this new editor?

You cannot edit HTML via the WYSIWYG editor anyone. However, there is an app for this. But from what I have read from the Invision team, they are less than enthusiastic about for reasons I do not properly understand. Perhaps someone else here can explain why the app should be used with caution or if Invision's reservations are overblown. (I hope I am not misinterpreting/misremembering Invision's views about the app.)

The following linked post about the HTML addon includes a link to the free app:

https://invisiondevs.com/topic/234-edit-html-of-posts/

I should add that if using the Page Editor, a Raw HTML widget is available, which might be an option in some situations. But if you need the ability to edit HTML in posts, the third-party app appears to be the only option.

Edited August 3, 2025Aug 3 by Como

On 7/18/2025 at 4:07 PM, EliasM said:

https://invisioncommunity.com/forums/topic/482354-any-idea-how-to-add-a-spoiler-button-to-the-post-builder/#findComment-2995463

Thanks for the link, sorry I missed your reply!

On 7/18/2025 at 8:15 AM, Stuart Silvester said:

Ok.

It would be more useful if you could tell us what problems you're having though (outside of HTML editing because, that has been discussed a lot already).

I do think there is a lot of room to improve the editor in terms of admin customisation.

For example, on my community (which is gaming focused), the spoiler tag is used very frequently (perhaps the most frequently) and so asking a user to find the Wrap Box, then figure out they need to hit a dropdown on that box and then select "Expandable" (which is not very clear it also means "Spoiler"), is quite inconvenient. There should be an ability for admins to allow this particular functionality to be a top-level button on the editor.

Similarly, I do not quite understand the rationale for options that feel very much secondary, like Text Size and Font Color to be assigned top-level buttons, while primary functions such as Quote Boxes are tucked away in a dropdown menu. I also don't get why the Code Block is nested under the Paragraph dropdown when it makes more sense to place it under the "plus"/"+" dropdown...

Just seems like the priorities in terms of editor button placement needs serious work. But I understand that every admin has a different need (although I'd be incredibly surprised to hear if 99% of communities don't use Quote Box enough for it to be handed a top-level placement), so I think a good improvement in this area would be a section in AdminCP where admins can re-arrange buttons as they see fit to best suit their community needs.

I fuly agree with @Dreadknux . The colors alone you can choose from in the editor make my skin crawl, so dulled down... 🤢

10 minutes ago, riko said:

I fuly agree with @Dreadknux . The colors alone you can choose from in the editor make my skin crawl, so dulled down... 🤢

Most likely you're able to change those using custom css:

[data-i-background-color="red"] {
    --i-richtext-background-color: var(--i-color_red);
}

[data-i-background-color="orange"] {
    --i-richtext-background-color: var(--i-color_orange);
}

[data-i-background-color="yellow"] {
    --i-richtext-background-color: var(--i-color_yellow);
}

[data-i-background-color="green"] {
    --i-richtext-background-color: var(--i-color_green);
}

[data-i-background-color="blue"] {
    --i-richtext-background-color: var(--i-color_blue);
}

[data-i-background-color="indigo"] {
    --i-richtext-background-color: var(--i-color_indigo);
}

[data-i-background-color="violet"] {
    --i-richtext-background-color: var(--i-color_violet);
}

[data-i-background-color="default"] {
    --i-richtext-background-color: var(--i-color_root);
}

[data-i-background-color="root"] {
    --i-richtext-background-color: var(--i-color_root);
}

[data-i-background-color="soft"] {
    --i-richtext-background-color: var(--i-color_soft);
}

[data-i-background-color="hard"] {
    --i-richtext-background-color: var(--i-color_hard);
}

[data-i-background-color="theme_1"] {
    --i-richtext-background-color: var(--i-background_1);
}

[data-i-background-color="theme_2"] {
    --i-richtext-background-color: var(--i-background_2);
}

[data-i-background-color="theme_3"] {
    --i-richtext-background-color: var(--i-background_3);
}

[data-i-background-color="theme_4"] {
    --i-richtext-background-color: var(--i-background_4);
}

[data-i-background-color="theme_5"] {
    --i-richtext-background-color: var(--i-background_5);
}

[data-i-background-color="theme_6"] {
    --i-richtext-background-color: var(--i-background_6);
}

@Cedric V Thank you for that. I'll try that. 👍

Just keep in mind those colours have to be safe for both light and dark mode. Which is why we went with the colours we have.

We also take on the feedback about the spoiler and code box, we may change these but keep in mind that we now have one editor for all devices so we don't want it to look like this on a mobile device.

7 minutes ago, Matt said:

Just keep in mind those colours have to be safe for both light and dark mode. Which is why we went with the colours we have.

Yes, I just read up on that. Makes sense. I'll have to live with these muted colors as working with variables in CSS is way above my head.

6 minutes ago, Matt said:

We also take on the feedback about the spoiler and code box, we may change these but keep in mind that we now have one editor for all devices so we don't want it to look like this on a mobile device.

Oh I hear that, appreciate the consideration Matt! I'm thinking maybe there's a way to offer a drag/drop option in AdminCP (maybe it can work a bit like the new Menu Manager?) for admins who are SENSIBLE about button placement (and for those who aren't sensible, maybe add a limit to the number of buttons you can place on the editor row!) but just want to prioritise certain functions on the top level?

52 minutes ago, Matt said:

Just keep in mind those colours have to be safe for both light and dark mode. Which is why we went with the colours we have.

We also take on the feedback about the spoiler and code box, we may change these but keep in mind that we now have one editor for all devices so we don't want it to look like this on a mobile device.

This hurts my brain so much.

On 8/3/2025 at 6:33 AM, Como said:

I should add that if using the Page Editor, a Raw HTML widget is available, which might be an option in some situations. But if you need the ability to edit HTML in posts, the third-party app appears to be the only option.

I wish there was an option to edit in HTML everywhere, not just when editing a post. That alone is useful, but I also need to edit other things and I can’t. Since version 5, the fact that they removed this — when literally all they had to do was keep it enabled for admins — was, honestly, the worst decision the IPS staff has ever made.

Not even in the top 10.

I don't actually hate the new editor and have enjoyed the box wrap options particularly.

I have resigned myself to using more raw html widgets. It's fine for small bits but tedious for more substantial blocks and pages. I was hoping to use less HTML as the years go by.

The two things I miss most are

1. being able to drop a proper button (e.g., ipsButton--primary, etc) into a post/blog/event

2. being able to selectively prettify certain embedded images by classing them

Edited August 4, 2025Aug 4 by bradl

HTML editing has been discussed multiple times.

Here
Here
Here
Here

tl;dr modern editors can't do (tiptap, CKEditor 5, etc) due to treating HTML not as a string but as a node tree. We sanitise heavily and whitelist what can be retained to prevent bad actors breaking topics, etc so while you can save HTML with whatever you want in it in theory, you could never load it in an editor again without it stripping everything it isn't allowed to recognise.

12 hours ago, Matt said:

HTML editing has been discussed multiple times.

Here
Here
Here
Here

tl;dr modern editors can't do (tiptap, CKEditor 5, etc) due to treating HTML not as a string but as a node tree. We sanitise heavily and whitelist what can be retained to prevent bad actors breaking topics, etc so while you can save HTML with whatever you want in it in theory, you could never load it in an editor again without it stripping everything it isn't allowed to recognise.

Would that include quoted content which has had its HTML modified (by the third-party app or otherwise)?

Edited August 5, 2025Aug 5 by Como