› Rooms › Easy Demo Import [Plugin] › Presets do not import after Divi 4.19.3 update
Tagged: changelog, child theme, easy demo import, edi, presets
- This topic has 13 replies, 3 voices, and was last updated 4 weeks ago by Ania Romańska.
24 December 2022 at 6:06 am #3917::
We have a problem with the child theme import functionality, that I’m sure everyone will be able to replicate easily if their child theme is using Presets. None of the child theme presets are being imported correctly on Divi version 4.19.3 and 4.19.4. The import process works correctly on Divi 4.19.2.
I hope you’ll be able to investigate this further, Terry @mizagorn
- This topic was modified 5 months, 1 week ago by Ania Romańska.
1 January 2023 at 5:37 am #3923
12 January 2023 at 3:08 am #3924::
@divilover and @michelle, sorry for the delay and thanks for letting me know.
Can you explain a bit more about what types (or all?) presets are not importing? An example would be extremely helpful so I know where to look in the code. Screenshots, errors logs, anything at all. I can’t replicate all setups. 🙁
Also to confirm, any version of Divi *above* 4.19.2 is having this issue? I will scan the changelogs to see what updates were made in relevant places.
- This reply was modified 4 months, 2 weeks ago by Terry Hale. Reason: additional information suggested
12 January 2023 at 3:40 am #3926::
I appreciate your help.
So the problem is with all global presets. Very easy to replicate. If you add a new preset or change the default preset of any module inside a child theme – none of these design settings will import. In Divi 4.9.13, ET moved presets to a separate setting. It’s in the changelog under “Improved Presets storage and performance.” and the change is visible in the includes/builder/feature/global-presets/Settings.php file in Divi. So yes, any version of Divi above 4.19.2 is having this issue.
I managed to get this to work by including the et_divi_builder_global_presets_ng WP Option in the EDI settings. That imports all prestes correctly, but the problem is that it overwrites any of the existing presets a website would have before the demo import, so it isn’t an ideal solution.
Hopefully, this helps. Thank you again for taking the time to look into it.
- This reply was modified 4 months, 2 weeks ago by Ania Romańska.
16 January 2023 at 4:41 am #3943::
@divilover thanks so much for the amazing feedback. It has been a tremendous help.
I have been looking into the options slugs, which look like include builder_global_presets, builder_global_presets_ng and builder_global_presets_temp.
As I’m sure you’re aware, these are all used for backwards compatibility and current usage.
There is code within the plugin that is specific to Divi. My idea is to create an option (for Divi) titled something like “Merge or Replace Divi Global Settings”. This specifies if the global settings from the import will either replace or add to (merge) the already existing global settings.
Does this seem like a good idea to you? Also @michelle
16 January 2023 at 5:36 am #3944::
Thank you, Terry, for taking the time to look into it for us.
If the end user saw a checkbox to “Include Global Presets,” it would be perfect. If we only merged their current presets with the new ones from the demo – that would be a good enough solution, and offering a choice for replacing presets wouldn’t be necessary, as we don’t do it for other import “parts.”
I would vote for calling it what it is: “Presets” instead of “Settings”. “Global settings” could be a bit confusing, as other “global” options are included in our child themes in various places.
This approach would match other import settings very well (e.g., with “Include Posts,” we are only adding new posts without touching what’s already on the site, and we don’t have the option for replacing existing posts).
15 January 2023 at 5:36 am #3932::
Hey Terry @mizagorn
I just dealt with a support ticket and wanted to let you know in case this wasn’t obvious. I thought installing the child theme with a previous version of Divi and then updating Divi afterwards would be okay. Unfortunately not, if I update Divi, presets break.
16 January 2023 at 5:52 am #3945
17 January 2023 at 3:09 am #3946::
@divilover Ania okay that’s odd. I only tested with one theme, I’ll have to try the others.
@mizagorn Terry I agree with Ania, we need it called preset and merging is fine for me too.
Question? Will we need to repackage all themes with this fix? Cause that’s no fun 😉
12 February 2023 at 3:24 am #3953::
@divilover and @michelle
Apologies for the delay on getting your users some information as to what’s going on. If you have alternatives after waiting so long, that’s good! You should go ahead. I’m currently going through some negative stuff. 😉
Good, news, though…. I have the framework in place. What’s challenging is that Divi uses a single entry in the options table to set global values.
In other words, one entry in the “wp_options” table defines all global options!
I need to decipher what’s going on with that, how to parse it out, and then make sure merging or replacing is something that works.
13 February 2023 at 7:27 am #3954::
Hi Terry and thanks for the update.
I don’t currently have an alternative and I am getting regular support requests on this.
@divilover are you able to explain how you managed to get this to work, even with it overwriting existing presets please?
14 February 2023 at 4:25 am #3955::
Thank you, Terry, for taking the time to work on this. I appreciate it.
I have a temporary solution, but it is not 100% satisfactory.
@michelle I included the et_divi_builder_global_presets_ng WP Option in the EDI settings before exporting. Please see this screenshot: https://imgur.com/QWEA6SM
That replaces all global settings upon demo import, but it only works with Divi 4.19.3 and up. It will not import any presets when used with an older Divi version.
16 February 2023 at 3:43 am #3956::
Thanks so much Ania. Guess I better re-export all my themes!
4 May 2023 at 4:19 am #3964
- You must be logged in to reply to this topic.