Skip Navigation

[Resolved] Uncaught type error: cannot read

This thread is resolved. Here is a description of the problem and solution.

Problem:

There are suddenly a lot of errors on the registration form page where I am using the toolset CRED form.

Solution:

Please check the compatibility issues, for example:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate all other plugins, and switch to WordPress default theme 2021, deactivate all custom PHP/JS code snippets, and test again

Relevant Documentation:

This support ticket is created 3 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by himanshuS 3 years, 8 months ago.

Assisted by: Luo Yang.

Author
Posts
#2000051

There are suddenly a lot of errors on the registration form page where I am using the toolset CRED form.

Sometimes, I can't even submit the form due to these JS errors.

Link: hidden link

#2000211

Hello,

Which theme/plugin are those error messages com from?

Have you checked the compatibility issues? for example:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate all other plugins, and switch to WordPress default theme 2021, deactivate all custom PHP/JS code snippets, and test again

#2002003

My issue is resolved now. Thank you!