Unable to View or Edit Gravity Form Field Settings

Hi,

This sounds like a JavaScript error.

I’ll have a closer look on my test environment and see if I reproduce the issue and find the cause.

In the meanwhile, if you go into the Gravity Forms settings page, then open the CKEditor WYSIWYG settings. Un-ticking ‘Enable in form editor’ and saving the changes should get you back on track.

Do you know how to edit your plugin PHP files? (usually done using an FTP tool, but you should also be able to use the ‘edit’ option on the plugin page — just make sure you’re editing the right file!).

I want you to try this version

gf_wysiwyg_ckeditor_plugin.php: https://pastebin.com/5xwYm4uX

Sorry for the delay getting back to you. I unchecked ‘enable in form editor’ and all is good.

I also tried to download the version you put on Pastebin, but see that it was removed before I got a chance to get it.

I have the same issue as above.

Any ideas how to resolve?

Hey,

Are you able to try replacing one of the plugin files with this patch, test and report back?

gf_wysiwyg_ckeditor_plugin.php

https://pastebin.com/c7Kx72pY

Hi ovann86,

I’ve replaced gf_wysiwyg_ckeditor_plugin.php with the one you have on pastebin.

The green active icon on the forms list page is now the brighter green “active” color.

However, it’s still not possible to edit any fields on the form when “Enable in form editor” is checked.

I had the same issue. Unchecking the ‘enable in form editor’ worked for me also.

Thanks for letting me know trik_sea.

There’s deffinately an issue out there and I’m not sure why I’m not seeing it in my test environments.

Hopefully I can get to the cause of it, because having the WYSIWYG in the form builder is really helpful when you have to make complicated forms.

Hey,

I’ve been unable to reproduce this issue in my test environment but can see a number of you have the exact same problem.

To help me work out what’s going on, could someone please re-enable the CKeditor in the form editor, load up a form that is breaking and save the page HTML into a pastbin? Im hoping I’ll see a clue such as the order things are loading.

https://pastebin.com/

You can send the saved pastebin link to [email protected]

Any other error messages you have would also help, such as the JavaScript errors in the browser debug tool.

Hi,

A user has kindly sent me through what I needed to look into the issue.

I found something that wasn’t right – there are two scripts that needed to load in the wp-admin footer but was not.

I’ve tried to resolve it in version 1.6.6 but need someone to confirm that it has been fixed.

Could you please update to version 1.6.6 and report back?

Thanks

Hi ovann86 – I updated to version 1.6.6

• Checked and saved “Enable in form editor” in CKEditor WYSIWYG settings
• I was able to add a field to the form and save it ( which I don’t believe was possible before).
• Tried to edit a few fields, but the options will still not open when you click on the arrow.

UPDATE on ckeditor not loading in form editor:

After testing an various environments, I’ve now discovered that this issue happens only when the Gravity Forms ‘No-Conflict Mode’ option is turned on.

As described with the option, this will disable third party scripts – such as the ones required to run this plugin. Which then breaks the functionality of the form editor.

I will try to work around this or present a warning message if the ‘No-Conflict Mode’ option is enabled. But realisicly, I’m wondering why someone would ever turn this on — it seems that it would only create more issues than it could solve.

PLEASE UPDATE to version 1.7.1 – this version should resolve the issue by displaying a warning message when the editor cannot load. Realistically though, You’ll need to turn off the ‘No-Conflict Mode’ option if you want to run third party plugins like this along side Gravity Forms.

Closing due to non-response.

If the issue is still happening with the latest version of this plugin please let me know.

I’m 99% sure this issue was happening because you had Gravity Forms in no-conflict mode, which by design will stop plugins like this from working. In version 1.7.1 I added a prompt to alert users that have no-conflict mode enabled.