Contact Form: Failed to load plugin url: tinymce-plugin-form-button.min.js

[richardmtl]

This issue was reported in two different tickets. I see no similarity in site setups between them, other than WordPress 4.9.8. They do not have the same plugins installed.

Site 1:

1619547-zen (debug link in the ticket)
PHP: 7.1.14
WordPress: 4.9.8
Jetpack: 6.8.1

Site 2:

1619931-zen (debug link in the ticket)
PHP: 5.6.30
WordPress: 4.9.8
Jetpack: 6.8

Error message:

Failed to load plugin url: http://DOMAIN.com/wp-content/plugins/jetpack/_inc/build/contact-form/js/tinymce-plugin-form-button.min.js

This message pops up when trying to edit a page or post. Since I don't think we've seen this issue before, it feels like a 6.8-related issue.

EDIT to say that I can load the js file directly in the browser, but since it's a generated file, I don't know how relevant that is.

[jeherve]

This is most likely happening because of a conflict between Jetpack's Contact Form TinyMCE plugin and another TinyMCE plugin added by another plugin on their site. TinyMCE plugins are used to add new buttons to the editor toolbar, and they usually work well with each other, unless one of them cannot register itself properly.

It would be useful to run plugin dances on both sites to figure out what plugins are causing that conflict, so we can dig into it some more. No need to deactivate all plugins though; I would recommend to only look at plugins that add buttons to the post editor.

[richardmtl]

I've asked both site owners to do the plugin dance, since I can't spot which plugin(s) are likely causing this, they both have an eclectic collection of active plugins.

[MuhammadAbubakarbaloch]

It is the problem of Jetpack's Contact Form. When I have activated Jetpack's Contact Form the problem got started...

[jeherve]

@MuhammadAbubakarbaloch Could you try to deactivate any other plugin that may add buttons to the classic editor on your site, and let us know if you find a specific plugin that seems to be conflicting with Jetpack?

Thank you.

[htdat]

Another case - it seems this is a conflict between Jetpack and WPBakery Page Builder:

2026884-zen
Blog ID: 113788967

I am asking more into to verify the issue.

[htdat]

2026884-zen
Blog ID: 113788967

For the case above, it was resolved by using the latest versions of both Jetpack and WP Bakery Page Builder.

[abcxyz-m]

2050881-zen

Asked them to try deactivating any plugins that add functionality to the Classic Editor.

[csonnek]

2135878-zen

Asked them to deactivate all plugins and turn them back on one by one to determine the plugin causing the error

[snowmads]

2153043-zen

Asked them to try deactivating any plugins that add functionality to the Classic Editor.

[jenhooks]

2443109-zen -- recommended they stop using the Classic Editor plugin.

2445196-zen -- on this one, the user is using the retired Big Brother theme. I recommended they either switch to a theme that the Classic Editor plugin will work with, or deactivate it and use Gutenberg.

[chaselivingston]

Another report in 2509349-zen. Also has Classic Editor installed.

[coder-karen]

Also reported in 2504924-zen - Classic Editor plugin installed.

[RalpManis]

No classic editor plugins but WooCommerce uses classic and the only way I could get back to working status is to disable Jetpack.

[jeherve]

the only way I could get back to working status is to disable Jetpack.

If you're willing to give this another try, do you think you could try to reactivate Jetpack, and then deactivate each one of your plugins, one at a time, and let us know if you find a conflicting plugin?

If all else fails, another option would be to go to this page on your site and deactivate Jetpack's Contact Form feature:
yoursite.com/wp-admin/admin.php?page=jetpack_modules

[RalpManis]

Hmm, " Sorry, you are not allowed to access this page."

…

On Mon, Mar 9, 2020 at 7:18 AM Jeremy Herve ***@***.***> wrote: the only way I could get back to working status is to disable Jetpack. If you're willing to give this another try, do you think you could try to reactivate Jetpack, and then deactivate each one of your plugins, one at a time, and let us know if you find a conflicting plugin? If all else fails, another option would be to go to this page on your site and deactivate Jetpack's Contact Form feature: yoursite.com/wp-admin/admin.php?page=jetpack_modules — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#10919?email_source=notifications&email_token=AL3BE562M4OTGKNOBGFDINTRGTF5VA5CNFSM4GJQACC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOGV3GY#issuecomment-596467099>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL3BE5Z3A7VTQYS3GL24RNDRGTF5VANCNFSM4GJQACCQ> .

-- *Infinitee Designs* Ralph Manis 10 Ocean Drive Rehoboth Beach. DE 19971 USA *1 **(302) 396-8558* *Infinitee Designs * https://www.infinitee-designs.com <http://www.infinitee-designs.com/> *Infinitee T-shirts * https://www.infinitee-designs.com/t-shirts *Infinitee Web Design * *https://infinitee-designs.com/webdesign <https://infinitee-designs.com/webdesign>*

[jeherve]

@RalpManis You'll only have access to this page if Jetpack is installed and connected to WordPress.com on your site.

[htdat]

@RalpManis - it seems that you're contacting us via our support ticket too. Please follow up our instruction in tickets/emails.

Internal ref: 2774593-zen

[RalpManis]

Got it... All good now.

…

On Tue, Mar 10, 2020 at 2:48 AM Dat Hoang ***@***.***> wrote: @RalpManis <https://github.com/RalpManis> - it seems that you're contacting us via our support ticket too. Please follow up our instruction in tickets/emails. Internal ref: 2774593-zen — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10919?email_source=notifications&email_token=AL3BE5347OYGMKFP2J2B53LRGXPALA5CNFSM4GJQACC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOKG5EI#issuecomment-596930193>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AL3BE5Z44VVWW2LS4FL5M2TRGXPALANCNFSM4GJQACCQ> .

-- *Infinitee Designs* Ralph Manis 10 Ocean Drive Rehoboth Beach. DE 19971 USA *1 **(302) 396-8558* *Infinitee Designs * https://www.infinitee-designs.com <http://www.infinitee-designs.com/> *Infinitee T-shirts * https://www.infinitee-designs.com/t-shirts *Infinitee Web Design * *https://infinitee-designs.com/webdesign <https://infinitee-designs.com/webdesign>*

[jeherve]

Also in #16021

[rakibrg1971]

i have not WP Bakery Page Builder why this problem?

[jeherve]

@rakibrg1971 Could you try deactivating any plugins that add functionality to the Classic Editor, one at a time, and let us know if you find a specific plugin that seems to conflict here?

[rakibrg1971]

@jeherve i am solve this problem if i deactivate (Accelerated Mobile Pages) its no error. Rangpur city news .
Thank You

[jeherve]

@jeherve i am solve this problem if i deactivate (Accelerated Mobile Pages) its no error.
Do you experience the same issue when using this AMP plugin instead?
https://wordpress.org/plugins/amp/

[jenhooks]

Reported in 3082646-zen.

[coder-karen]

Reported in 3162263-zen

[jeherve]

Also reported in https://wordpress.org/support/topic/error-message-in-post-2/

[abcxyz-m]

Reported in: https://wordpress.org/support/topic/jetpack-error-message-on-add-new-product-page/

[danjjohnson]

Also in 3663700-zen

[APerusso]

Hi
This issue "Failed to load plugin url: https://mywebsite/wp-content/plugins/jetpack/_inc/build/contact-form/js/tinymce-plugin-form-button.min.js" appeared in product page editor after i used the plugin Malcare Security Plugin to scan a site, I deleted it but the problem did not desapear.
I tried to deactivate others plugins, including delete Jetpack and reinstall, but the issue stay there.

[ctdealba]

Another one: 3894949-zen

[bobmatyas]

Also in: 3941810-zen

[danjjohnson]

Also in https://wordpress.org/support/topic/jetpack-slowdown-the-website-speed-and-increase-core-web-vitals-score/#post-14432500

[ChasMHS]

Any resolution for someone running Jetpack forms and classic editor? Only two plugins installed.

[christianguerrag]

A similar problem with the same message when they create a new page, here 5647127-zen
They are using the Classic Editor with a retired theme Chateau, it is a simple site so there are no plugin or jetpack issues.

[github-actions]

Support References

This comment is automatically generated. Please do not edit it.

• 1619547-zen
• 1619931-zen
• 2026884-zen
• 2050881-zen
• 2135878-zen
• 2153043-zen
• 2443109-zen
• 2445196-zen
• 2509349-zen
• 2504924-zen
• 2774593-zen
• 3082646-zen
• 3076671-zen
• 3162263-zen
• 3663700-zen
• 3894949-zen
• 3941810-zen
• 5647127-zen
• 5648037-zen
• 5647668-zen
• 8145205-zen
• 8158251-zen
• 8158467-zen
• 8158753-zen
• p9o2xV-4ew-p2#comment-9290
• 8158379-zen
• 8154930-zen
• 8158755-zen
• 8158534-zen

[SiR-DanieL]

One more report in 5648037-zen

[christianguerrag]

One more in 5647668-zen

[ariel-maidana]

Another one here: 8145205-zen (simple site)

[upwardmomentum84]

Another case here: 8158251-zd-a8c

Site is Atomic. Deactivated all plugins and changed to a default theme but issue persists. The error shows on posts when you open them for editing.

[lizkarkoski]

Two more reports of this from the past hour.

• 8158467-zen
• 8158753-zen

These are atomic sites. Error still shows with non-default plugins deactivated and a default theme. Does not show in Block Editor if you deactivate Classic Editor.

[card1concepts]

Hi All, same issue. I tried deactivating the classic editor in conjustion with the Divi Builder I use, but need it for my workflow. However what did work for me was to deactivate the jetpack contact form module and I found instructions here ( https://www.winwar.co.uk/2017/08/disable-jetpacks-contact-form-module/ ) just go to the Jetpack dashboard and scroll all the way to the bottom and click "modules" then find the contact form and disable it... assuming it is not a feature you need.

[jeherve]

@coder-karen Since this is popping up in the past few hours, and since we've just released a new version of Jetpack to WordPress.com (see p9o2xV-4ew-p2#comment-9290 ), I'm wondering if this may be caused by #37157. It may be worth testing on an Atomic site with the Classic editor plugin active, see what happens.

[lizkarkoski]

8158379-zen

[adelineyaw]

8154930-zd-a8c
8158755-zd-a8c

[coder-karen]

Sorry folks. All newly reported issues (from today) will be resolved as of now (on Atomic sites) with the recent revert.

[sanjeev00733]

The issue persists in Simple sites, reported in 8158534-zd-a8c

[coder-karen]

Simple now resolved with the latest deploy there too. Should be all good on all sites now.