Suggestion for testing Customizer/widget changes?
-
I’ve read your warning and understand the purpose of this plugin. I get it. At the moment I’m comfortable with my theme and templates, but need to go beyond that.
Many themes give us the Customizer option to change which widgets appear, and details about those widgets. That information is saved in database location #1. Then through some decision in code location #2, those widgets are available in the Widgets area for maintenance. Widget details are then saved in database location #3. And at runtime, some code in location #4 (a template?) finds the flags and details, and pulls in the content for each widget.
I am a developer but I have not ventured into this area. Based on what you know, and have intentionally not implemented for undestandable reasons, I’m hoping you can provide some insight into where the data is saved for the above #1-4 features. This might be a good blog topic? Could you offer a recommendation for another plugin or code that can help get the more rigorous A/B switching that includes the above?
I just looked at the Nelios A/B plugin but it does not offer a trial for theme switching, and I won’t pay without seeing how it works.
I’d be happy with links and a good ol’ RTFM. I’m just starting my inquiry in this area and will do my homework as required. Thanks!
- The topic ‘Suggestion for testing Customizer/widget changes?’ is closed to new replies.