-
AuthorPosts
-
September 6, 2018 at 10:39 pm #1006823
Hello.
I need your help with a compatibility issue between Enfold and Gravity forms. I can’t edit the confirmation and notifications of the form, the panels show no content and just a white window. I contacted Gravity forms, we did a serie of tests including turning on/off all the plugins, theme, etc, and the confirmation and the notifications editing panels worked. So after all of that I was told that the issue was with the theme.September 8, 2018 at 1:00 pm #1007409Hey DanielKG,
I took a look at your issue and added this css to your child theme styles.css:#wp-form_confirmation_message-editor-container.wp-editor-container .wp-editor-area { color: #000 !important; visibility: visible !important; }
it seems to be working correctly now, Please see the screenshot in Private Content area.
Please clear your browser cache and check.Best regards,
MikeSeptember 10, 2018 at 1:26 am #1007720This reply has been marked as private.September 11, 2018 at 7:32 pm #1008543Hi,
Please disable any cache and optimisation plugins and work on it afterwards.
It should be working just fine then.Best regards,
BasilisSeptember 11, 2018 at 7:51 pm #1008556Hi Basilis,
I don’t have any cache or optimization plugins. I did disable all plugins to test again but the error is still there. The only way the issue gets fixed is by changing the theme. Can you please look at it again? it is not a plugin issue.
Thanks.
September 12, 2018 at 2:26 am #1008674Hi,
I took another look and added this code to the end of your functions.php file in Appearance > Editor:add_action('admin_head', 'custom_admin_css'); function custom_admin_css() { echo '<style> .wp-editor-area { color: #000 !important; visibility: visible !important; } </style>'; }
this adds the css to the admin header, Please clear your browser cache and check.
Best regards,
MikeSeptember 12, 2018 at 5:12 pm #1009016This reply has been marked as private.September 13, 2018 at 3:07 am #1009151Hi,
This is the error you are getting:ls-admin-tinymce.js?wp-mce-4800-20180716:43 Uncaught ReferenceError: LS_MCE_l10n is not defined at t.(/wp-admin/anonymous function).t.(anonymous function).init (/wp-content/themes/tetra/config-layerslider/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) at HTMLScriptElement.u (wp-tinymce.php?c=1&ver=4800-20180716:3)
It looks like it is a tinymce.js conflict from layerslider, but errors can sometimes be misleading.
Try disabling your plugins. If that resolves the issue, reactivate each one individually until you find the cause.
I searched for this error and found this post
It also seems Gravity Forms has had many issuesBest regards,
MikeSeptember 13, 2018 at 11:09 pm #1009706Hi, I’m not using the layerslider in any of my pages on the site. I saw the same error that you published as well, but don’t know what to do wit it. I also did the test by disabling the plugins but that didn’t resolve the issue either.
I followed the different post regarding this issue and tried their suggestions but again it didn’t work either.
Could you take a look at it again?
Thanks.September 14, 2018 at 4:01 am #1009771Hi,
The ls-admin-tinymce.js is the editor within the layerslider, There must be a conflict with the Gravity Forms tinymce.js
Since you said you were not using any layerslider slides I disabled it at Enfold Theme Options > Layout Builder > Integrated (Bundled) LayerSlider Plugin
and then I tested your Gravity Forms again, and it seems to work now.
Please clear your browser cache and check.Best regards,
MikeSeptember 17, 2018 at 11:16 pm #1011029Hi Mike,
Thanks for looking into this. Hopefully this issue is solved in later updates and that all the features ca be used. There are a lot of post related to this issue, hopefully it gets fixed soon.
Thanks again. -
AuthorPosts
- You must be logged in to reply to this topic.