Import and export theme settings fixed to support child theme export / import to parent theme and vice versa

[kimcoleman]

All Submissions:

• Have you followed the Contributing guidelines?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

Improves the theme import and export settings functionality to support settings imported or exported between child themes or Memberlite sites without child themes.

The export file now includes a "template" attribute, which should always be the parent theme ("memberlite") slug, instead of the child theme slug

How to test the changes in this Pull Request:

1. Export theme settings from a site using a Memberlite child theme
2. Try to import them into a site not using a child theme or using a different named child theme
3. Without this code, the validator would flag this as a wrong theme.
4. With this code, the validator will successfully import the theme settings.

Other information:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you successfully run tests with your changes locally?

Changelog entry

• BUG FIX/ENHANCEMENT: Now supporting theme settings import and export between child themes and parent themes.

[Copilot]

Pull request overview

This PR fixes theme settings import/export functionality to support transferring settings between Memberlite child themes and parent theme installations. Previously, exports from child themes would only import to that exact child theme.

Changes:

• Export now uses parent theme slug (template) instead of active theme slug (stylesheet)
• Import validation now accepts settings if they match either the parent theme or active theme (for backward compatibility)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[RachelRVasquez]

My Testing Steps:

1. Downloaded the child theme that's available from the PMPro site
2. Installed on my local env on Memberlite 6.1.0. Activated the child theme.
3. In the child scheme, I changed the color scheme in customizer, changed a few colors individually, and added a random CSS change in the stylesheet. My color scheme is now "custom".
4. Exported the theme settings file.
5. Went to my second local env on Memberlite 6.1.1. No child theme.
6. Imported the theme settings file. No errors on the front-end. Nothing in the debug.log ✅
7. Checked my customizer. My "custom" color scheme is active and my individual color changes are there. ✅ Anything that doesn't live in theme settings like the styles I added in the child theme don't carry over. That's intentional. 👍

Looks good to me! 👍