Does 3.5x Support Disabling the Shortcode Manager?

I work on a multisite that uses NextGEN and several custom blocks created with Advanced Custom Fields PRO. Previously we had a conflict where pages using our custom blocks would generate an Invalid JSON error upon saving. Disabling NextGEN’s shortcode manager fixed the issue.

We have disabled NextGEN’s shortcode manager via the following snippet in wp-config:

define('NGG_DISABLE_SHORTCODE_MANAGER', TRUE);

Upgrading to NextGEN 3.54 seems to ignore this snippet, however. The Invalid JSON error came back. Reverting to 3.41 got things working again.

I just wanted to report this in case something was missed in the update.

• This topic was modified 2 years, 5 months ago by Eric Karkovack.