10

[Quick fix] Divi not updating on WordPress multisite network

Are  you  experiencing licensing issues when trying to use the WordPress Updater to update ElegantThemes plugins and themes on your WordPress multisite network? Here’s a quick tip that may fix it for you.

The issue

When updating the Extra theme on our WordPress Multisite network, we ran into the following error:

An error occurred while updating Extra: Before you can receive product updates, you must first authenticate your Elegant Themes subscription. To do this, you need to enter both your Elegant Themes Username and your Elegant Themes API Key into the Updates Tab in your theme and plugin settings. To locate your API Key, log in to your Elegant Themes account and navigate to the Account > API Key page. Learn more here. If you still get this message, please make sure that your Username and API Key have been entered correctly

The ElegantThemes support forum wasn’t very helpful in this case, in every case the support team remotely logged in to the customer’s website and fixed it, without telling us afterwards what the cause of the issue was.

Despite entering the licensing info on multiple locations within the multisite network, automatic updates still didn’t work.

The fix

Try this: Enable one of the ElegantThemes plugins or themes (not a child theme) on the multisite network’s MAIN site, and enter the licensing info for it there. Afterwards try updating the plugins from the network manager. For us, all ElegantThemes products now updated without any problems. Afterwards you can disable the plugin or theme on the main site again. Automatic updates should still be working.

You only need to enter the licensing info on one of the plugins, and they should all be able to automatically update through the WordPress Updater. This should work for Divi, Extra, Bloom, Monarch or any other ElegantThemes product.

Rhytz

Tech-enthusiast since birth. Web developer and professional coffee drinker by day, programming fun stuff for online games or tinkering with my pinball machines by night. Not shy of drinking some (craft) beers during the weekend.

10 Comments

  1. Mate you’re a genius!
    Was starting to doubt my decision of building a MultiSite with Divi, when I couldn’t even auto-update the theme.
    I had entered the license info on one of the main sites, still no luck.
    Installed Bloom as you said, and Bingo! Theme would update!

    • Glad it was helpful! This thing was driving me nuts, since I was pretty sure the automatic updates used to work before, and just suddenly stopped working.

      We used to have a 20-some standalone WordPress websites and now most of them are transferred to the multisite network. There are more obstacles to overcome (SSL, imports failing, and multi-domain single sign on to name a few), but once you’re set, it’s worth the effort.

      • Yeah, looking forward to getting it all sorted. Just going to have 6 child sites to start with. But single sign-on is going to be a big bonus for the staff.

  2. Thank you for this! I wasn’t getting an error message like in the post, but still wasn’t seeing the option to update from the main network updates screen. Installing Bloom on the main site and validating did the trick to let me do an auto update. Thank you! Been fiddling with manual updates for almost 9 months now…

  3. I have this issue I am working in a Multisite, I have already entered the API and username in the Parent site, the issue is when I change to the Child Site where I have made some customizing, the Divi Customizing options will not show. Shows a blank page beside the WP dashboard bar. How can I see the DIVI Theme Options in Child theme? Or it is not compatible? https://uploads.disquscdn.com/images/c7ba2c901a4f2a9c55ab3f7c5b6e24a11056138e3e798dab062377b288bff8f6.jpg

    Thank you .

  4. I was able to update the plugins (Monarch, basically) by entering the API key on each separate site. I have not been able to update DIVI, though, even using the solution presented here.

Leave a Reply

Your email address will not be published. Required fields are marked *