Mike Schinkel

Thanks, and by the way, the core feature is called “customize changesets” whereas the feature plugin where it was first developed (and where additional features are being prototyped) is called “Customize Snapshots”.

My bad, I forgot which was the new name.

Nevertheless, the “customize” part is in both, you’re right. The reason for it being tightly coupled to the Customize API is because it is in fact part of the Customize API. Changesets are just a way to store customized data, the values for settings that are registered with the customizer. It’s the Customize API that has the framework for modeling things (options, posts, terms, etc) in WordPress via the WP_Customize_Setting and its interface for getting a value, sanitizing a value, previewing a value, and updating a value.

And that is the most worrying part, that they are too tightly coupled.

What would be really good would be to validate that it it not too tightly coupled and implement the functionality in something completely unrelated to customizer like in ACF, Pods, or similar. My concerns when I reviewed the code was that it too tightly coupled to be used in any other way.

BTW, where is the current codebase? I’d like to review it again but I have not been able to find it right now.

Name *

Email *

Website:

Topic Title (Maximum Length: 80):

Forum:
— No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor