gravityseeker

@anevins @cutu234 My bad, I should have expanded a little further than I did so there was no confusion. As far as minor updates, I don’t allow them as even minor updates can have unintended consequences and can cause / have caused headaches for users in the past. I was definitely not advocating for “not upgrading,” rather, performing the update /testing process manually in a sandbox environment before production environments to avoid any “potential issues.”

@cutu234 I apologize, I thought you were singing the praises as well ??

@juliet-sallette The WP people don’t make money on WP, yet graciously gave us a phenomenal CMS so that 99.9999999% of the population didn’t have to learn to be developers/designers and allowed developer/designers a less painful way to make $$. Please be grateful to them for what they have done to help online experiences. Yes, forcing Gutenburg was not a good decision, but as you have found out, there are plugins so that you are not impacted. Whether updating the WP Core or individual plugins, I highly advise you disable the core autoupdate [ just ad this -> define( ‘WP_AUTO_UPDATE_CORE’, false ); <- ] in the wp-config file and run your updates manually after thoroughly testing any updates in a sandbox environment before rolling out into production, especially since you are running 12 sites.

Yes, we can. But isn’t this a strange idea to disable one of the most important core features of a CMS? Let alone, that Gutenberg was the most praised new feature in WP 5.

@cutu234 I am not really sure who is praising this misfire. Certainly not the user base: https://www.ads-software.com/support/plugin/gutenberg/reviews/. As a developer that works with nearly every major free & premium CMS, builds plugins, themes, and middleware, Gutenberg is a miss, and not a close miss by any means. Thankfully, plugins leave a way to have the classic editor instead.

Always grateful to the @wordpress team for all they do.

• This reply was modified 6 years, 2 months ago by gravityseeker.

I figured it out. Having the lightbox plugin enabled was conflicting with the Next Gen Plugin. I disabled the Lightbox and everything works perfect.