Troubleshooting
Here you can find solutions to some issues that you might run into when using our plugins.
Divi
Importing layouts – the progress bar gets stuck at 100%
Problem: When importing a layout, the progress bar get stucks and Divi fails to complete the load.
Possible Cause: The WordFence plugin is preventing the file to be uploaded to the server.
Solution: Deactivate the WordFence plugin while you are importing the layout.
Styles are messed up when injecting a layout into a module
Problem: After injecting a layout into a module, all module styles are messed up.
Possible Cause: The layout that you have injected contains the same module.
Explanation: Imagine that you are working with a module called “Divi Module” and the module class is divi_module_1. Imagine that you want to display a layout inside that module and the layout contains another “Divi Module”.
Then, when injecting, both modules classes will be divi_module_2 (instead of divi_module_1 and divi_module_2). As a result, only the injected module styles will be applied.
You can try this by adding a blurb module and styling the blurb title and the blurb body. Then, in the blurb body, inject (for example, by pasting a module shortcode) another blurb with another styles. Save the changes and see the result in the front-end: The main blurb module styles are not being applied.
Sometimes the content is also affected , not only the styles, so injecting the same module can lead to unexpected results.
That’s why we recommend that you don’t use a module inside the same module whenever possible.
DiviPasswords
An error has occurred is appearing occasionally
Problem: The user is unable to unlock the content after one or two days of creating a password form. When entering the correct password the “An Error Has Ocurred” appears.
Possible Cause: The WordPress nonces are being cached. Nonces are used in form submisions for security reasons. If the the nonce verification fails when submitting the form, the content will not be retrieved and the above error will be thrown.
Solution: Go over your cache plugin and set a cache timeout so the page cache is cleared every 10-12 hours. This way, the nonce will be valid and the protected content will be retrieved.
Chances are that you are using WP Fastest Cache. If so, please read this:
https://www.wpfastestcache.com/tutorial/wordpress-nonce-cache/
In case you are using WP Rocket, please read this article instead:
https://docs.wp-rocket.me/article/975-nonces-and-cache-lifespan