search

soflyy / oxygen-bugs-and-features

Bug Reports & Feature Requests for Oxygen
https://oxygenbuilder.com/
316 stars 31 forks source link

Name Re-Usable Parts Based On Template Name #1588

Open j-ki opened 3 years ago

j-ki commented 3 years ago

Describe the feature you'd like to see included in Oxygen. When adding a single re-usable part (non-editable), instead of Oxygen naming the part something like "Reusable (post: 47) (#80)", I'd like Oxygen to incorporate the template name like "Facebook Pixel codeblock - reusable (post: 47)(#80)" - or something to that effect.

What are the use cases for this feature? I have certain codeblocks, like Facebook pixel script or Microsoft UET, that I want running on specific pages. But other pages like contact or about us shouldn't have these scripts.

Because these are non-editable codeblocks, when I see a part that says "Reusable (post: 47) (#80" and I need to know what's in them, I need to leave the current template, go to the re-usable template, and look at the JavaScript or PHP to remind myself what it does.

By naming the codeblock based on the template name, I can immediately know that this is a Facebook pixel reusable part, another is a date PHP code, etc.

I know I should be renaming them as I add them but sometimes, I get into a groove and I forget to rename them.

karmaral commented 2 years ago

+1, I always get annoyed when defining a reusable that I have to rename it. In theory, if you bring the reusable as "editable" it preserves the nicename, but it kinda loses the point of reusability since it no longer mirrors the template.

BertMammoet commented 11 months ago

+1 @Spellhammer @KittenCodes is this on the roadmap? Or can i make a workaround for this? We need this feature enhancement big time. Users should be able to rearrange blocks, but not edit te elements within these blocks. And if the users only see Reusable (post: 89) (#545) in their navigation of layers they get confused. Please add this to the roadmap, kind regards.