Niet in staat om een download thema component te wijzigen/aan te passen na update

AI-generated summary

After upgrading to Discourse 2.7.0.beta1, HeyRR noticed they could no longer modify downloaded theme components like the Xmas hats component, though local-created components remained editable. michaeld clarified this is an intentional feature designed to prevent users from losing customizations when remote themes are updated — referencing a meta discussion. HeyRR acknowledged the oversight in their search and expressed that users should bear responsibility for maintaining their themes, valuing the convenience of in-place edits. michaeld countered that allowing direct edits risks breaking themes during updates, and recommends stacking modifications in separate components instead — referencing another meta topic — likening unrestricted edits to leaving out sharp knives, since warnings alone aren’t always sufficient to prevent issues.

Just upgrade my Discourse and found out I cannot modify a download component any more, I’m on 2.7.0.beta1. Not sure if it’s an expected behavior.

Just use Xmas hats component as example, I saw this issue on multiple components, in the meanwhile I can still edit local-created theme component.

It’a a feature: Restrict editing of remote themes

I see. Thank you for the information. I guess I missed some keywords when searching for similar topics. I really didn’t think about this is a feature.

IMHO it’s user’s choose to keep remote theme updated with Discourse or not. Hence user is the one takes the risk and responsibility to maintain them.

Also being able to make in-place modification is really convenient.

Until something changes that impacts your theme component and you cannot update it because it would mean you would lose your modifications. Theme components can be stacked so you can (and should) put modifications in a separate component.

Sometimes it’s better to put away the sharp knives, since warnings don’t always work.