Bug in support of Multi-Cascading Select custom fields

[Fidel Castro Armario]

Version 2.1.22 has introduced a bug relative to the Multi-Cascading field support.

Problem:

When referencing a concrete level of a Multi-Cascading Select custom field, if you use only 1 digit for index part, the plugin will return an error in the configuration screen, indicating that its an invalid field code.

Anyway, the plugin will work correctly, i.e., you won't have any problem in your current configurations that reference Multi-Cascading Select fields.

Workaround:

Use 2 digits for index part when referencing level in Multi-Cascading Select fields, i.e., use %{nnnnn.ii} instead of %{nnnnn.i}. Example: use %{10001.04} instead of %{10001.4}

This bug will be solved in version 2.1.23.

[Fidel Castro Armario]

Fixed in version 2.1.23.