Does it work with child theme?

The plugin is designed to work with both twentytwentyone as the main theme or as a parent theme.

Having said that, the plugin has been designed specifically so that you don’t have to use a child theme ??

I cannot think what might be causing the options to appear and then disappear. The plugin is designed to only run if the parent theme has been detected and if it does run there isn’t anything that would cause the options to disappear again that we can think of. Can you please confirm that this happens with all other plugins disabled?

Perhaps we should look at adding a slider to the header with the plugin instead!

Oliver

Hey Oliver, thank you for the quick answer.

It is funny because now it is working.

Actually the only change I can think of that I did is that I changed to the parent theme in the customizer to see if it works and trying it in Internet Explorer instead of Chrome. But now all options are appearing…

Anyways I am grateful that it is working now and if it happens again I will investigate further, maybe there was some JScript action going on.

The plugin is great and offers lots of customization, but I am always adding some hacks and for me to do this is quicker adding it in a php file directly instead of using an UI and clicking around in it. But of course it would be better for maintenance if I would not do that I know… ??

Extremely glad that the issue resolved itself … could have been tricky to diagnose without seeing it!

Thanks for the update.

Always happy to take suggestions for new options so will monitor this thread and if anyone else wants a slider in the header we’ll get straight on to it ??

Oliver

I also had the settings disappear. It happened when I temporarily changed themes and then reactivated twenty twenty-one.

I was looking for where you are storing the settings for the plug-in, but could not find them. My guess would be that reactivating the plug-in created a new file that overwrote the settings.

It was no big deal.

OK, few things here … it would appear that when in the customizer, there is a bug that breaks the preview panel if you switch to a theme other than Twenty Twenty-One.

This will be resolved in the next update.

As for what happens to settings when you switch themes … nothing should happen at all. Settings are saved in the database for each theme; when you switch to a new theme, a new set of theme settings are used and saved in a different location of the database.

You can see all the sets of theme options if you use our Reset Customizer plugin. This plugin also lets you backup / restore / manually edit the theme settings.

So to re-iterate, activating or deactivating a theme will never over-write the previous theme’s settings.

What might be happening is if you make changes and save them as a draft set of customizer settings. But even in this instance I would imagine that they would re-appear if you re-activate the theme.

Nevertheless, this plugin uses all the built in features of the WordPress Customizer so there’s no reason that the default behaviour of WordPress wouldn’t be adhered to.

Finally, if you still believe that changing themes clears your settings, please provide exact steps as to how you achieved this so I can look into it further.

Thanks,

Oliver

Further to my last message above with regards to the bug whereby when the plugin is installed and activated and another theme is live previewed, this breaks the live preview panel.

We have fixed this issue on the latest update (v1.2.4).

Please let me know if this works for you.

Thank you,

Oliver

I don’t know if I can recreate the issue or not, but I’ll give it a try. As I said, it was not a very big deal to me.

Now that I know where these settings are stored (DOH!!!) I can look at them in my mySQL DB.

Hi Oliver, I have played with this quite a bit an now can recreate the problem.

I held off on updating to V1.2.6 to test the previous version as well as the current version of the plug-in and can recreate the issue on both versions.

Here is what I did:

• Create a Sidebar Everywhere
• Add 2 widgets to the Sidebar
• Change theme to Seedlet
• Change theme back to Twenty Twenty-One
• At this point it appears that the sidebar is gone. Actually it still exists, but there are no widgets on the sidebar any longer.

IF this is how it is supposed to work, I can certainly live with that, however, it seems a little funky to me.

• This reply was modified 3 years, 10 months ago by cprgolds.

Hi,

OK, this is a little less worrying as I believe the behaviour you describe is caused by WordPress Core by design.

What’s happening is that when you switch themes, the widgets that were used in the previous theme are moved to “Inactive Widgets” and can then be re-used if required by dragging them into a widget area again.

This is because, when a theme isn’t active it can’t keep track of what widgets exist and which are then deleted. So when the theme is then reactivated, the widgets that were being used in its widget areas could no longer exist.

So I’m almost certain that this behaviour is not being caused by the plugin.

I’ll keep an eye on this thread, however, in case anyone thinks otherwise!

Oliver

I’m afraid i’m having a simular issue. Everything with the ‘options for 20-21 theme’ plug-in worked great, however after upgrading it from 1.2.1 to 1.2.6 the top options like ‘general/header/nav’ show up for a second and then disppear. ;( When i switch back to the 20-21 theme itself everything is fine. When switching back to the child theme the same issue occurs. Upgrading the plug-in to 1.2.8 doesn’t help either. What can I do?

Thanks for your respnse,
Ronald

Hi Ronald,

Sorry to hear you’re having issues! The difficulty with child themes is that it’s always tricky to know what’s causing the fault!

Can you please share a .zip of your child theme so that we can attempt to replicate this problem?

In the meantime, try re-installing v1.2.1 from the bottom of the Advanced page of this plugin whilst we look into your issue.

Oliver

Thanks for your quick reply, Oliver. Here’s the zip. I’ll try re-installing V1.2.1

https://we.tl/t-PmSas9eyde

Ronald

…1.2.1 installed and the panel is the way it should be. Updating again however brings the issue back. So until 1.2.1 all’s fine.

Ronald

Thanks Ronald, I’m going to get straight on to look at the issue.

I suspect that you may be OK up to 1.2.4, maybe even 1.2.5.

If you so chose to install ??

Oliver

Quick question … can you please confirm that your child theme has …

/*
Template:     twentytwentyone
*/

… in the header of style.css?

This is what makes a child theme (as per the documentation on developer.www.remarpro.com)

I ask because the child theme you sent through doesn’t appear to specify the parent theme?

Please advise …

Many thanks,

Oliver