Update to 1.5.0 has created JavaScript errors on page editing
-
This plugin on our website was updated to version 1.5.0 today.
This has created cascading JavaScript errors in the WordPress backend when adding/editing a post/page.The problem was brought to us by our client who reported that the “Set Featured Image” link suddenly stopped working.
We then observed JavaScript errors from load-scripts.php
e.g.
Uncaught TypeError: _.pluck is not a function
Uncaught TypeError: Cannot read property ‘hasClass’ of undefined at HTMLDocument.
etc
etcDisabling the plugin and these errors go away.
Can you please advise of a fix to this.
many thanks
Ian
-
What browser are you using? Chrome? In the page editor, right clicking somewhere and choosing “Inspect” should bring up a developer panel that will provide some extra information, once you click on the “Console” tab.
https://cloudup.com/ck4Aa2whLBR
Any occurring errors will appear there and if you could paste them or at least screenshot them for us, we’d appreciate it.
Alternatively, if needed, we can take ongoing support for your current situation to private, and continue on there.
We are getting the same sort of error both with the beta and the live plugin. When we for to edit a page or a post, we get an overlay with modal dialog box that can’t be closed. Deleting the modal window via inspecting leaves an error message dialog that can be closed:
Failed to load plugin url: /srv/htdocs/wp-content/plugins/constant-contact-forms/vendor/jtsternberg/shortcode-button/js/shortcode-button.js
Hosted on WordPress.com, WordPress 5.1.1 running Salient theme. All other plugins at most recent version.
Thanks. I don’t have a lot of time but I understand that you need more information. I will have to ask the client whether they want me to spend any more billable time on investigating this defect.
Interesting. I just checked and the repo should be shipping that file still, but that doesn’t necessarily mean that things are succeeding in loading it like needed.
Is that from your browser dev tools console? If yes, anything else stand out potentially?
@tcolling Understood and noted.
So far these are the only two javascript based issues we’ve seen since the 1.5.2 release.
Browser: Chrome Version 73.0.3683.103 (Official Build) (64-bit)
Extension: All have been disabled for testing purposesWordPress: 5.1.1 with classic editor option installed
Plugins: All are up-to-date
Note: I also have the latest version of Yoast installedHere’s a screenshot of what my console is reporting from the admin area:
https://stage.resaleworld.com/shop/skin/light_responsive/images/cc_plugin_console.pngAdditional notes: I also have the following plugins installed which appear to add an option in the classic editor – Active Campaign Forms, WP Avatar, PopMaker Shortcodes…
Here’s a screenshot that shows WPBakery button options missing when the constant contact plugin is enabled.
https://stage.resaleworld.com/shop/skin/light_responsive/images/cc_plugin_no_buttons.png
Here’s a screenshot that shows them reappear when I disable the constant constant plugin.
https://stage.resaleworld.com/shop/skin/light_responsive/images/cc_plugin_deactivated.png
While troubleshooting I noticed that when I turn off my Yoast plugin – while leaving the constant contact plugin enabled – it would work fine again.
I manually checked to see if there was a newer plugin available for Yoast – there is which is version 10.1.3. The reason I thought to look at Yoast was because of the console error I sent you earlier that pointed to the wordpress-seo-premium script. For some reason, I never received a prompt from Yoast or WP to run the latest Yoast update. After manually installing the latest update and clearing the cache – it seems that everything is working fine again as expected.
Sorry for the confusion. Hopefully this will help anyone else that ran into the same issue.
Deactivated all other plugins to no effect.
@constantcontact would you like admin access to investigate?
@avazquez26 No worries on the confusion, glad to hear things are working for you again.
@guruscotty can you contact [email protected] and cc [email protected] with the email? Please refer to this support thread for organization sake and we know what the email is in reference to. Thanks.
@constantcontact I just noticed that the Yoast (ver 11) meta box on the page editor screen is blanked out. It only reappears when I disable the Constant Contact plugin. I’ve gone through each of my plugins – disabling all and enabling each one until I tracked down which plugin was causing the issue and it leads me back to the latest Constant Contact plugin ver 1.5.2.
I checked to make sure I had the latest version of the ACF Integrator and Advanced Custom Fields plugin as well. There seems to be some conflict with these plugins. It’s my understanding that these work with the Yoast plugin – they come up as recommended plugins to use in conjunction with Yoast.
Here’s a screenshot of the script errors in console:
https://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/cc-issue-script-errors.pngScreenshot of where Yoast has broken when the Constant Contact plugin is enabled.
https://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/yoast-blanked-out.pngHere’s a screenshot showing how the Yoast meta box should appear. It comes up fine when I disabled the Constant Contact plugin.
https://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/when-cc-is-disabled.png-
This reply was modified 5 years, 6 months ago by
avazquez26.
-
This reply was modified 5 years, 6 months ago by
avazquez26.
-
This reply was modified 5 years, 6 months ago by
avazquez26.
@avazquez26 definitely agree that something is up with your install, but at the moment, we are unable to recreate the issue.
We have the 1.5.2 version active for our plugin, and then also these versions for Yoast and ACF:
Yoast Premium version 11.0
ACF(free) version 5.7.12yoast’s panels are showing up just fine for us. However, we do also realize that parts of these probably also come from configuration and field setup, etc. We also don’t have ACF Integrator. Is that a premium plugin from somewhere? Or should it be available on www.remarpro.com here?
Also, are you using the Gutenberg editor or the classic editor
I’m using WpBakery (formerly known as visual composer) as my content editor. I have the classic editor ver 1.4 plugin installed.
The ACF Integrator was a recommended plugin by the WpBakery plugin. It adds a few custom form fields that allows me to hide the page titles from the page and post editor screen.
In other words…
-I’m using WPBakery as my content editor. I can’t really change this because the entire site was built using this plugin. If I deactivate it all of my pages get messed up.
-The WPBakery plugin recommended installing the ACF plugin when the installation completed. Then it recommends installing the ACF Integrator to import a few custom fields that work specifically with the WPBakery plugin. For example, it adds a custom form field on the page editor screen that allows you to toggle show/hide the page title.
I did try to deactivate the VCF Integrator – but the the meta box still won’t appear as long as the Constant Contact plugin is enabled. I’ve also uninstalled and reinstalled the Constant Contact plugin, VCF Integrator, the ACF plugin and the Yoast plugin.
Here’s what I have my Yoast settings set to:
https://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/ypast-settings.pngHere’s a screenshot of all the plugins I’m currently using.
https://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/plugins1.pnghttps://www.resaleworld.com/shop/skin/light_responsive/images/rsw_images/plugins2.png
Note: The Yoast meta box does show up on page load – but after about a minute, the box disappears. Another way to trigger it is to try and enter a focus keyword or meta desc. It won’t allow me to enter any text in those fields – then after several seconds or so, the entire box just clears and appears blank.
@avazquez26 can you contact us at [email protected] and cc [email protected] so we can discuss your situation away from the public forum here.
@avazquez26 ever reach resolutions with this issue?
-
This reply was modified 5 years, 6 months ago by
- The topic ‘Update to 1.5.0 has created JavaScript errors on page editing’ is closed to new replies.