Option to Reset Module at Page-Level

Currently, if a module has been edited at the page-level, those edits take precedence over any changes made to the module's default settings at the template-level. This allows for modules to continue to present the correct information on the pages in which they live, but there are situations in which it would be convenient for users to be able to easily hit a "reset" button on a per-page basis to reset a module to its default settings. 

 

For example, if one were to create a custom module that contained four separate fields and added it to a page, and then subsequently edited that module on the page, but then later decided that the fourth field wasn't necessary and deleted it from the module, that page is still going to display all four fields. In order to update the module on that particular page, you have to remove and re-add it– the tech support old faithful of turning it off and back on again. 

 

It'd be convenient to have a toggle in the module that would allow you to choose to reset the module to its current state in the design manager so that you didn't have to go through the process of removing and re-adding it. This would also be highly beneficial for instances in which a local module group was edited at the page level and then later converted to a global group, at which time changes to the global group won't be reflected on the page since it'd still be holding onto the settings specified at the page-level from the previous version of the module. 

6 Replies
nickdeckerdevs Regular Contributor | Diamond Partner
Regular Contributor | Diamond Partner

I wish I had more than one upvote

Jon_McLaren Esteemed Contributor | Platinum Partner
Esteemed Contributor | Platinum Partner

great idea, temporary workaround- rename the variables for the fields, breaks the association with existing pages values. It will set all instances to their defaults for that field however.

nickdeckerdevs Regular Contributor | Diamond Partner
Regular Contributor | Diamond Partner

Yeah @Jon_McLaren I've done that in the past and copy / paste the current content into the default content in the module, or I've opened up two windows and copy / paste into the new module I create. It is a tiring work around, but the best options at the moment. When it is for a module with 20+ fields it becomes exhausting!

Jon_McLaren Esteemed Contributor | Platinum Partner
Esteemed Contributor | Platinum Partner

@nickdeckerdevs i completely agree. Definitely would be better to have a better way

Adesignl
Occasional Contributor

Upvote this one!

Reg Regular Contributor | Platinum Partner
Regular Contributor | Platinum Partner

Fantastic Idea! This would save me a lot of time.