Critical Error after Update to the latest version

Received a critical error as soon as I updated to the latest version. The website is down. Is there a way to go back to the older version and where can I d/l the old version The page I need help with: [ log in to see the link] following is the error received from the Debug: Fatal error: Uncaught Error: Undefined constant “DSM_PRO_VERSION” in /wp-content/plugins/supreme-modules-for-divi/public/class-dsm-supreme-modules-for-divi-public.php:199 Stack trace: #0 /wp-includes/class-wp-hook.php(324): Dsm_Supreme_Modules_For_Divi_Public->enqueue_scripts() #1 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #2 /wp-includes/plugin.php(517): WP_Hook->do_action() #3 /wp-includes/script-loader.php(2265): do_action() #4 /wp-includes/class-wp-hook.php(324): wp_enqueue_scripts() #5 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #6 /wp-includes/plugin.php(517): WP_Hook->do_action() #7 /wp-includes/general-template.php(3050): do_action() #8 /wp-content/themes/Divi/includes/builder/frontend-builder/theme-builder/frontend-header-template.php(11): wp_head() #9 /wp-content/themes/Divi/includes/builder/frontend-builder/theme-builder/frontend.php(216): require_once(‘…’) #10 /wp-content/themes/Divi/includes/builder/frontend-builder/theme-builder/frontend.php(247): et_theme_builder_frontend_override_partial() #11 /wp-includes/class-wp-hook.php(326): et_theme_builder_frontend_override_header() #12 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #13 /wp-includes/plugin.php(517): WP_Hook->do_action() #14 /wp-includes/general-template.php(38): do_action() #15 /wp-content/themes/Divi/page.php(3): get_header() #16 /wp-includes/template-loader.php(106): include(‘…’) #17 /wp-blog-header.php(19): require_once(‘…’) #18 /var/www/vhosts/tidesacademy.com/httpdocs/index.php(17): require(‘…’) #19 {main} thrown in /wp-content/plugins/supreme-modules-for-divi/public/class-dsm-supreme-modules-for-divi-public.php on line 199 Please note I have removed the server path from above. same error ! 🙁 I temporary desactivate the plugin (the backoffice was again available) This reply was modified 1 year, 11 months ago by cgri . Same here. Error persist even on pages that don’t use the plugin… running around to disable Supreme Modules Lite on all the websites giving issues – luckily I can still log into wp-admin… switching to Divi Torque Lite for clients that can’t wait for a bug fix. This reply was modified 1 year, 11 months ago by OutBoxed . This reply was modified 1 year, 11 months ago by OutBoxed . Same here on 3 websites. Luckily the backoffice was accessible so I managed to disable the plugin, but still. It looks like they copied the code from their Pro version without editing the constant. I was able to fix the error by changing line 199 of the file supreme-modules-for-divi/public/class-dsm-supreme-modules-for-divi-public.php : wp_register_script( 'dsm-magnific-popup', plugin_dir_url( __FILE__ ) . 'js/jquery.magnific-popup.js', array( 'jquery' ), DSM_PRO_VERSION, true ); to: wp_register_script( 'dsm-magnific-popup', plugin_dir_url( __FILE__ ) . 'js/jquery.magnific-popup.js', array( 'jquery' ), DSM_VERSION, true ); For the rest we’ll have to wait for the official fix. Thanks Jos – You’re a star ⭐⭐⭐⭐⭐. I ended up downloading the previous version from a site that hadn’t updated yet, and also disabled auto-updates on all sites still on a previous version. Only 3 websites had gone critical, yet. Thank goodness for https://uptimerobot.com/ that notifies me of sites that went down. Same here. Issues with version 2.5.5.3. Only Divi + Divi Supreme. I tried what @josklever said above and it worked! Thank you! I’m still having some minor issues of one of the supreme lists not displaying, but at least the rest of the website is working as usual. I was also getting the fatal error before. Thanks @josklever , it worked ! Ha Jos Klever @josklever Na de update kreeg ook ik de melding van een kritieke fout. Op 5 websites. Heel erg bedankt voor het delen van de oplossing. Het werkt! Same issue here … Thankfully I had backups and rolled back to a previous version. had same issue, thank you @josklever changing that line worked!! Install WP Rollback plugin and roll back to Version 2.5.52. Same here. had to roll back my site to this morning’s backup. Thanks for the tip, Jos! Will try that in hopes they catch this bug and fix the shipment! I just wanted to jump back on and thank the Supreme Modules Lite team for the quick update/revision. Make sure you update your plugins now!