[Resolved] Date picker trowing an error in console

[Author]

Posts

[enricoC-2]

Hi, after the last toolset update, I'm having some problems with datepickers in cred forms.

When I click on the date field the datepicker do not show up, and I get this error in console

Uncaught ReferenceError: Unable to process binding "with: function (){return cred_form_context_a999 }"
Message: Unable to process binding "with: function (){return cred_form_context_3441 }"
Message: cred_form_context_3441 is not defined
    at with (eval at parseBindingsString (knockout-3.4.0.js?ver=3.4.0:68), <anonymous>:3:57)
    at a.m.i (knockout-3.4.0.js?ver=3.4.0:8)
    at Function.Pc (knockout-3.4.0.js?ver=3.4.0:51)
    at Function.Qc (knockout-3.4.0.js?ver=3.4.0:51)
    at Function.aa (knockout-3.4.0.js?ver=3.4.0:50)
    at Object.a.m.a.B (knockout-3.4.0.js?ver=3.4.0:49)
    at init (knockout-3.4.0.js?ver=3.4.0:8)
    at knockout-3.4.0.js?ver=3.4.0:72
    at Object.w (knockout-3.4.0.js?ver=3.4.0:39)
    at knockout-3.4.0.js?ver=3.4.0:71
with @ VM1312:3
a.m.i @ knockout-3.4.0.js?ver=3.4.0:8
Pc @ knockout-3.4.0.js?ver=3.4.0:51
Qc @ knockout-3.4.0.js?ver=3.4.0:51
aa @ knockout-3.4.0.js?ver=3.4.0:50
a.m.a.B @ knockout-3.4.0.js?ver=3.4.0:49
init @ knockout-3.4.0.js?ver=3.4.0:8
(anonymous) @ knockout-3.4.0.js?ver=3.4.0:72
w @ knockout-3.4.0.js?ver=3.4.0:39
(anonymous) @ knockout-3.4.0.js?ver=3.4.0:71
q @ knockout-3.4.0.js?ver=3.4.0:11
m @ knockout-3.4.0.js?ver=3.4.0:71
k @ knockout-3.4.0.js?ver=3.4.0:69
g @ knockout-3.4.0.js?ver=3.4.0:69
a.eb @ knockout-3.4.0.js?ver=3.4.0:75
a.m.i @ knockout-3.4.0.js?ver=3.4.0:8
Pc @ knockout-3.4.0.js?ver=3.4.0:51
Qc @ knockout-3.4.0.js?ver=3.4.0:51
aa @ knockout-3.4.0.js?ver=3.4.0:50
a.m.a.B @ knockout-3.4.0.js?ver=3.4.0:49
init @ knockout-3.4.0.js?ver=3.4.0:8
(anonymous) @ knockout-3.4.0.js?ver=3.4.0:72
w @ knockout-3.4.0.js?ver=3.4.0:39
(anonymous) @ knockout-3.4.0.js?ver=3.4.0:71
q @ knockout-3.4.0.js?ver=3.4.0:11
m @ knockout-3.4.0.js?ver=3.4.0:71
k @ knockout-3.4.0.js?ver=3.4.0:69
a.Rb @ knockout-3.4.0.js?ver=3.4.0:75
applyViewModelBindings @ frontend.js?ver=1.9:249
(anonymous) @ frontend.js?ver=1.9:290

Any Idea on how to fix this?

thanks 🙂

[Shane]

Hi Enrico,

Thank you for contacting our support forum.

I suspect that this is the case due to plugin conflicts, what I recommend that you do is to temporarily disable all your non-toolset plugins and try again.

Once you have done this please let me know if you are still experiencing issues with the datepicker.

Thanks,
Shane

[enricoC-2]

Hi Shane,
thanks I'll try that.

In the meanwhile, I have a question related to this issue:

We've run this update on our test enviroment, and the only problem we had was with CRED.

Do you think it's OK to update the other toolset plugins (TYPES, VIEWS, ACCESS) in production and keep for now the old CRED version, or there are going to be compat problems within the suite?

thanks

Best

[Shane]

Hi Enrico,

Thank you for testing.

It is always recommended to update all our plugins to maintain full compatibility, however you can try leaving the CRED on an older version because from our changelogs here
https://toolset.com/download/toolset-cred/#changelog

I see that most of the fixes were made to the CRED plugin itself and not any compatibility fixes.

Please let me know if this helps.

Thanks,
Shane

[enricoC-2]

Hi Shane,
apparently it's TYPES that's creating the error.

I've tried on the standard WP theme with no plugins active and I'm still getting the error:
in this file

wp-content/plugins/types/library/toolset/toolset-common/res/lib/knockout/knockout-3.4.0.js?ver=3.4.0

Any idea on how we can fix it?

[enricoC-2]

Just FYI

the date picker field is formed by two <input> field. The first one is named wpcf-lge-stdate[display-only].

Is the [display-only] supposed to be there?

[Shane]

Hi Enrico,

Yes this is actually normal.

Would mind providing me with admin access to the website so that I can have a further look at this ?

The private fields will be enabled for your next response.

Thanks,
Shane

[Christian Cox]

Hi, I'm checking in to let you know that Shane is out today and will return tomorrow to continue assisting you. Thanks for your patience.

[Shane]

Hi Enrico,

Thank you for the credentials, however trying to log in with them proved to be unsuccessful.

Could you check on the credentials and let me know.

Thanks,
Shane

[enricoC-2]

Hi Shane,
I've checked the credentials and they work...

have you read the part where I wrote *PLEASE READ*? It's kind of important that you read that

[Shane]

Hi Enrico,

I was able to log in and access the page but i'm not seeing any form on the page, see screenshot.

I'm getting a page as if i'm still logged out .

Could you setup a test page for me with the form?

Thanks,
Shane

[enricoC-2]

It's a MU network (you have superadmin capabilities), but you were not added specifically on this site, so you were logged in but without a role.

You should be able to see it now.

[Shane]

Hi Enrico,

Thanks for adjusting the settings.

I took a look at it and export the forms and types and tested it on my local test site and found that re-creating the form resolves the issue.

Could you try this and let me know if it helps.

Thanks,
Shane

[enricoC-2]

Yes, recreating the form resolves the issue...
what do you think it could be the cause?

[Shane]

Hi Enrico,

I cannot say exactly what the issue was but I suspect that the form might have been corrupted.

Thanks,
Shane