Update to v3.0.2 from v1.8.0 still switches theme to Minimalist

Hey @endymion00

If you have an old installation with LoginPress 1.8.0 and try to update to the latest version 3.0.2, The default theme selected will stay in place.

If you install this on a new environment for the first time, The “Minimalist” theme will be selected.

You can always select the default theme. ??

Have a nice day!

I’ve repeatedly said this and other people have reported the same. This is just not correct. Updating from 1.8 to 3.0.1/2 selects Minimalist every time and not the previously selected Default theme.

Ok, here’s the problem.

loginpress/css/style-presets.php checks the database option “customize_presets_settings”

The problem is that option doesn’t exist in v1.8. It only gets created after updating to 3.x.

So, you need to handle the case where the option doesn’t exist and then set the default to default1 during the update process, but set it to minimalist when it’s a clean install and not the update process.

If “customize_presets_settings” does exist in some cases in 1.8, it’s likely a difference between free users and paid, since free users can’t change the theme, so the setting doesn’t get written is my guess. Either way, checking for the option’s existence and update first and setting it to default1 should still resolve.

Hey @endymion00 and @angelsrock

Do note: This has been fixed in the latest release.

I have created a short video demonstration for you in which I installed the 1.8.0 version and then I updated it to 3.0.2.

Here is a screencast for you.

If you are having any issue/s do let us know at our support forum so we can debug and fix this for you.

Have a nice day!

So, 3.0.3 will fix this?

Hey @endymion00

This has been fixed in the 3.0.2 version as I have shown you in the above screencast as well, however, if you are having any issue/s do let us know at our?support forum?so we can debug and fix this for you.

Looking forward.

If it’s not related to “customize_presets_settings” then there must be some other setting doing it, some other option that’s making it think it’s a new install on update, since regardless of your video of which I don’t know if the database is clean of all loginpress data before installing. This would likely be an essential part of the test.

It also may be that installing 1.8 first sets things up differently than the older versions (whatever I started with) did and wasn’t corrected over updates getting me to 1.8

I just know that 3.0.2 does not set it correctly for me. I reviewed any databse option containing loginpress and didn’t see anything assigning the default theme. I expect that it only appears in Pro when another is selected. I don’t see “customize_presets_settings” and it looks like that is not immediately created on updating to 3.0.2 either. It only appears after I fix the theme back to Default. Since this is the first time there’s 2 choices in the free version, it’s the first time “customize_presets_settings” is being created when the theme is changed. Again the lack of this setting may still be what causes it to default to Minimalist since it is your new “default” on new installs and with no existing “customize_presets_settings”, it switches it to Minimalist.

With all this information should be able to add the case of updating from a pre-3.0 version, checking for the existence of “customize_presets_settings” and if not found, set it to the Default theme rather than Minimalist, because if it does exist, then that would mean they’re running Pro and are using a different theme than the defaults already and should be carried over accordingly.

Otherwise I’ll just have to manually fix each site’s theme selection on updating which is around 140 sites, which is why I’ve been pushing to resolve this.

Hey, @endymion00

Yes, there can be an issue but we can’t replicate it in any environment. I’ve updated it over the 50 sites and everywhere a smooth update happens and LoginPress installed over them for 5+ years.

We really want to help you in fixing this issue (if exists) but here we need your collaboration to debug and fix it in one of your environments. Could you please contact us at the support forum so a dedicated developer can help you?

Truly appreciated.

I’ve provided more than enough specific detail for a developer to easily check and fix. I’m done.

And one last thing to confirm that it is the missing customize_presets_settings that’s the issue.

If I add the following to the wp_options table in the database before updating, the plugin then keeps it set to default as one would expect when updated.

option_name = customize_presets_settings
option_value = default1

Anyone missing this (installs with the free version with no prior loginpress data in the database or no other selectable theme options) will get switched to Minimalist on update and won’t generate the customize_presets_settings options until Default is selected and saved.

Pro users already having selected another theme should also not have an issue I would expect.

@endymion00

Thank you for your input. It helps a lot. We’re working on it and get back to you ASAP.

Hey, @endymion00

We’ve overcome the issue you highlighted and truly appreciated on you explained. Do you want to try a beta version?

If you want, I can take a look on a site or if you’re close to releasing the next version I can wait for that one as well.

Let’s try it once. Please do contact us for the beta version.

Thank you.