John O

Hi,

I have checked and the home_url() on the site is definitely returning the site URL not the subfolder where wordpress is installed, yet the link points to the subfolder. Any suggestion for where this might be coming from?

Thanks,

John

I have installed 5.9.11.3 which seems to have fixed things. Date and timepicker are back. Thank you for resolving this over a weeked. ??

I think the latest update 5.9.11 has caused javascript conflicts with a range of other plugins, including Divi and Advanced Custom Fields Pro. A site that I manage is having similar issues, related to a clash between the plugin update and Advanced Custom Fields Pro. The date/time pickers no longer work and it is impossible to save dates/times in events. If you can roll back to 5.9.10 safely as suggested above, that would be my advice too. Unfortunately the site I manage is on hosting that keeps plugins up to date, so if I roll back it just auto updates again. I hope the plugin developers resolve this soon as event booking is the core business on the site I manage. :-/

• This reply was modified 3 years, 8 months ago by John O.

Hi,

I think the latest update 5.9.11 has caused javascript conflicts with a range of other plugins, including Divi. A site that I manage is having similar issues, related to a clash between the plugin update and Advanced Custom Fields Pro. The date/time pickers no longer work and it is impossible to save dates/times in events. If you can roll back to 5.9.10 safely that would be my advice. Unfortunately the site I manage is on hosting that keeps plugins up to date, so if I roll back it’ll just auto update again. I hope the plugin developers resolve this soon as event booking is the core business on the site I manage.

• This reply was modified 3 years, 8 months ago by John O.

@voneff – let me know if you find out the cause. I tried but I couldn’t isolate what was causing the error – it even occurred when I deactivated ACF-PRO.

I wonder if it is a block editor issue with custom posts / taxonomies, and CPT-UI and ACF-PRO are red herrings?

Hi,

I had deleted the custom taxonomy so I could get the project ready for users to add content. I have just tried to recreate the error on my dev version and now it works? There have been several plugin updates over the past week. I can only assume there was some sort of conflict that has now resolved itself. Very bizarre. Thanks for your patience!

Hi – any updates on this issue? Thanks.

Hi,

I have been in touch with ACF, and they suggested I see whether the error only occurs with the block editor. I installed the Classic Editor, and as they suspected, there is no error when using the Classic Editor to edit and save the custom post with the custom taxonomy.

Looking into it a bit more, I discovered that the issue still occurs in the block editor when I deactivate ACF Pro but keep running CPT-UI and use it to add a custom taxonomy to the post type. With ACF Pro disabled I forced the error and got this error code:

TypeError: this.props.terms.join is not a function
    at t.value (https://websiteaddress.com/wp-includes/js/dist/editor.min.js?ver=9.0.7:55:215147)
    at zc (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:146:251)
    at wc (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:138:272)
    at fa (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:137:115)
    at gg (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:135:196)
    at Ca (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:133:365)
    at Object.enqueueSetState (https://websiteaddress.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.6.3:191:324)
    at r.q.setState (https://websiteaddress.com/wp-includes/js/dist/vendor/react.min.js?ver=16.6.3:20:304)
    at r.value (https://websiteaddress.com/wp-includes/js/dist/data.min.js?ver=4.2.0:1:13998)
    at https://websiteaddress.com/wp-includes/js/dist/data.min.js?ver=4.2.0:1:10357

To create the above error:

Using WP5.0.3 and CPT-UI I created a custom post type, then created a custom taxonomy for that custom post type. The error only occurs when trying to save a custom post type using the block editor. Everything works fine using Classic Editor.

When I remove the custom taxonomy, the error disappears.

When I switch to Classic Editor, the error disappears.

Any idea what could be causing this?

Thanks in advance.

Hi, thanks for the speedy reply. I’ve let the people over at ACF know too so hopefully they’ll fix things. ??

Yoast have said on Twitter that an update is being released tomorrow (Monday) that should fix this issue.

• This reply was modified 6 years, 2 months ago by John O.

I am experiencing the same issue. I have temporarily deactivated Yoast and hope they issue a fix soon.

Marking this as resolved.

Hi – yes I got the Yoast SEO plugin updated and the problem is resolved. ??

Thanks for this it is much appreciated – I guess it is a case of sit tight and they’ll hopefully fix it. ??

Thanks for this it is much appreciated – I guess it is a case of sit tight and they’ll hopefully fix it. ??