i've been basically doing that now with my template and css names.. (prepending resource names with a 'theme' name), such as "theme_description_of_resource"calguy1000 wrote: Imported templates and stylesheet names are prefixed with the theme name, which stops most interference, and the system won't let you install a theme twice![]()
that could get interesting..
i have: aura_2col_layout, aura_2col_screen, aura_2col_print in one "theme"
i export it as a theme name of cmsms_aura10.
someone imports it and all the resources get tagged cmsms_aura10_aura_2col_xxxxx.
they repackage it (changing things or not) as a new theme. now we end up with
theme aura_reloaded_11, that when reimported by a third person, contains resource names like aura_reloaded11_cmsms_aura10_aura_2col_xxxxx


i gather you're anticipating a scenario like this and have planned ahead a bit, so the theme manager knows when a resource was imported via a theme and can strip out the old theme name on a re-export (as a different theme name)?