I'm getting the following error on the backend of WordPress. It's interfering with the WYSIWYG editor inside Gravity Forms. If I disable the LS plugin there's no problem. I also tried re-installed WordPress, deactivated all plugins except LS, reverted to older versions, still getting this error. Any ideas? The really weird thing is, this error is in the WP admin screen when working Gravity Form confirmation settings. Why would LS script load on the backend admin screen?
******************** ERROR ********************
Uncaught ReferenceError: LS_MCE_l10n is not definedat t.(/wp-admin/anonymous function).t.(anonymous function).init (http://(mysite).com/wp-content/plugins/LayerSlider/static/admin/js/ls-admin-tinymce.js?wp-mce-4800-20180716:43:13)at dx (wp-tinymce.php?c=1&ver=4800-20180716:3)at Array.<anonymous> (wp-tinymce.php?c=1&ver=4800-20180716:3)at Object.qt [as each] (wp-tinymce.php?c=1&ver=4800-20180716:3)at vx (wp-tinymce.php?c=1&ver=4800-20180716:3)at Hx.<anonymous> (wp-tinymce.php?c=1&ver=4800-20180716:3)at Array.<anonymous> (wp-tinymce.php?c=1&ver=4800-20180716:3)at qt (wp-tinymce.php?c=1&ver=4800-20180716:3)at s (wp-tinymce.php?c=1&ver=4800-20180716:3)at n (wp-tinymce.php?c=1&ver=4800-20180716:3)
******************** /ERROR ********************
For the moment we are just disabling the plugin when ever we need to work on the Gravity Forms. Your help will be much appreciated!
Attached files: error screen.jpg
Thank you for getting in touch with us. My name is Attila and I'm happy to assist you today.
I would like to confirm that we have received your message. Due to the nature of the issue you are experiencing, I will have to contact and consult with the development team first. I will get back to you as soon as I can.
We appreciate your patience while we're working towards your ticket.
Best Regards,Attila | Kreatura Support Team
Yeah i switched to the standard Twenty Seventeen theme and the problem persists.
Thank you for the feedback. We'll try to investigate this further and get back to you.
We've looked into this in detail and tried to reproduce the error, but we couldn't recreate it at our end. Everything worked perfectly for us and no other user reported any issue like this either.
We will try to investigate this further to see if we can find anything or if something can be done from our end, but it looks like an isolated edge case on your end, caused by an external factor.