WordPress.org

Make WordPress Core

Opened 16 months ago

Last modified 3 months ago

#22880 new enhancement

Customize Themes without activation

Reported by: kkkrys Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Appearance Keywords: needs-patch
Focuses: ui Cc:

Description

Add a posibility to customize deactivated themes with the Theme-Customizer without activating them by default.
Useful for Blogs running multiple Themes between which the frontend user can switch.

Change History (4)

comment:1 SergeyBiryukov16 months ago

  • Component changed from Themes to Appearance

comment:2 celloexpressions3 months ago

  • Keywords needs-patch ui-focus added

This sounds like a good idea; essentially we just need to add a "Save but don't activate" button. Your use case is probably uncommon, but this would be a nice way to allow users to work on customizing different themes before activating without doing it all at once. As additional features such as widgets are added to the customizer, allowing users to save work-in-progress customizations without activating the theme is a pretty important feature.

comment:3 follow-up: helen3 months ago

I think it's probably more than a differently labeled button (and the storage mechanism to go with). What's the experience when a user customizes an inactive theme, saves those customizations but doesn't activate the theme, and then goes back to customize it later? Do we then need a reset button? Is it less useful because there's no selective or step-by-step undo?

comment:4 in reply to: ↑ 3 celloexpressions3 months ago

Replying to helen:

What's the experience when a user customizes an inactive theme, saves those customizations but doesn't activate the theme, and then goes back to customize it later? Do we then need a reset button? Is it less useful because there's no selective or step-by-step undo?

We don't have the ability to reset or selectively undo changes for active themes either, so I don't think we need to worry about that here. That really sounds like something that customizer revisions would handle (like .com's snapshots I believe), which would be super cool but are a separate (and much bigger) issue. For now, having the ability to save changes without activating is more important than adding the ability to reset all options or undo revisions, since you could almost call the current behavior a bug.

In terms of the storage mechanism; I'm guessing it's pretty much already in place, we just need to skip the theme switching part (or if that happens first, switch back). This could also allow users who can't switch_themes but can edit_theme_options to make customizations to inactive themes. I think we'd probably retain the existing button as the primary, and add a new secondary one for this.

Note: See TracTickets for help on using tickets.