See #1029058: [META ISSUE] Change skin configuration for reference; Comment #4 to be more precise.

We also discussed that skin configurations can be applied to multiple themes currently. Ideally, we leave that to a separate issue, and keep the idea in mind that "cloning" an existing skin configuration for another theme would be the simplest solution.

Comments

moonray’s picture

moonray commented

Now that #744706: Add Features support is in, we can consider cloning.

What would it involve?

  • Add a skin configuration specific form that only edits or adds a new skin configuration and allows changing the module, element, theme, group, skin options.
  • Add clone links to skin configuration listing form.

Is adding cloning of individual skin configurations really useful, though?

moonray’s picture

moonray commented
Category: Task » Feature request
Issue summary: View changes
moonray’s picture

moonray commented
Status: Active » Postponed
astonvictor’s picture

astonvictor commented
Status: Postponed » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.