We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On setting value to an integer or numeric-only string, I receive the following JS error when viewing the fields:
value
Uncaught TypeError: $(...).data(...).split is not a function in fieldmanager.js L171 in my version
Uncaught TypeError: $(...).data(...).split is not a function
If I add non-numeric characters to the value, the error does not occur (but then of course I'm unable to check for the correct value).
It looks like #418 might address this in 170f09e.
In my specific case, I'm using the term datasource, so term IDs are stored in the field. If anyone has a workaround for this case, I'd appreciate it.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
On setting
value
to an integer or numeric-only string, I receive the following JS error when viewing the fields:Uncaught TypeError: $(...).data(...).split is not a function
in fieldmanager.js L171 in my versionIf I add non-numeric characters to the value, the error does not occur (but then of course I'm unable to check for the correct value).
It looks like #418 might address this in 170f09e.
In my specific case, I'm using the term datasource, so term IDs are stored in the field. If anyone has a workaround for this case, I'd appreciate it.
The text was updated successfully, but these errors were encountered: