July 6, 2021 at 6:29 pm #40194Jade ShelleyGuest
I am getting a critical error on my website when trying to set up e signature for a form on my website. Problem happens with pavillion theme installed, but not with theme twenty twentyone.July 6, 2021 at 6:39 pm #40203Jesse OwensKeymaster
Thanks for reaching out, and thanks for using the BoldGrid WordPress website builder with Pavilion.
I tried to recreate the error that you’re getting, but I’m not sure if I’m using the same signature plugin that you are. I found WP eSignature by eSign Genie as the closest match to “wp-esignature,” is that the same one?
When you received the critical error, was there an error message along with it? If you can copy-and-paste that error message, it may also help to identify any problems. You may also have received an email to your main administrator email account with a copy of the error message as well.July 7, 2021 at 5:52 pm #40234Jade ShelleyGuest
That is the right plug in I believe you are using. The conflict doesn’t happen until you try to create the stand alone form . I believe this has to do with the add on plug in “business add-ons” for e signature. Here is the email error I got.
An error of type E_ERROR was caused in line 191 of the file /home/terryr6/terrybrothersonexcavating.com/wp-content/plugins/e-signature/add-ons/esig-signer-input-fields/admin/esig-sif-admin.php. Error message: Uncaught TypeError: Argument 1 passed to ESIG_SIF_Admin::sif_add_buttons() must be of the type array, null given, called in /home/terryr6/terrybrothersonexcavating.com/wp-includes/class-wp-hook.php on line 294 and defined in /home/terryr6/terrybrothersonexcavating.com/wp-content/plugins/e-signature/add-ons/esig-signer-input-fields/admin/esig-sif-admin.php:191
#0 /home/terryr6/terrybrothersonexcavating.com/wp-includes/class-wp-hook.php(294): ESIG_SIF_Admin->sif_add_buttons(NULL)
#1 /home/terryr6/terrybrothersonexcavating.com/wp-includes/plugin.php(212): WP_Hook->apply_filters(NULL, Array)
#2 /home/terryr6/terrybrothersonexcavating.com/wp-includes/class-wp-editor.php(416): apply_filters(‘mce_external_pl…’, Array, ‘document_conten…’)
#3 /home/terryr6/terrybrothersonexcavating.com/wp-includes/class-wp-editor.php(307): _WP_Editors::editor_settings(‘document_conten…’, Array)
#4 /home/terryr6/terrybrothersonexcavating.com/wp-includes/general-template.php(3498): _WP_Editors::editor(”, ‘document_co
Jade ShelleyJuly 7, 2021 at 5:52 pm #40236Jade ShelleyGuest
I also received this today from the developer of e signature
Happy Wednesday. ?
I was able to chat with my developer about the theme conflict you are seeing.
He mentioned that we aren’t able to solve it on our end, but he provided some great information that you can share with the theme developer so they can apply a fix. ?
We can see that this theme’s tinymce button is returning null for no WP posts or pages. This is breaking the eSignature editor screen and throwing the error you are seeing.
To solve this, we would suggest that this theme needs to support all types of post types or edit screens instead of only supporting selected post types.
1. Can you reach out to the theme developer with this feedback and see if they can resolve this conflict?July 7, 2021 at 6:26 pm #40240Jesse OwensKeymaster
Thanks so much for the additional info, I was trying the wrong plugin after all. However, the Plugin Developer’s feedback was very useful!
I’ve located the bug, and submitted a fix so that our developers can release an update as soon as possible for you.
If you need to resolve the issue immediately, you can make a small edit to your theme file
In that file, modify lines 163 and 169, that currently read
See the modified file here that you can copy and paste.July 8, 2021 at 10:27 am #40253Jade ShelleyGuest
You’re awesome. Thank you for helping me fix that!
- The topic ‘confilict with pavillion theme and wp-esignature plugin’ is closed to new replies.