If you install perplex on a site containing existing forms, and these forms contain fields perplex hides by default, it causes a client dependency error.
This causes preview of fields not to be shown and fields being uneditable. Unhiding the fields types in the config files fixes the error, returns preview, and makes fields editable again.
Thanks for the bug report, good you already found a workaround for this issue. We "hide" the fieldtypes by altering an API call in Forms (getAllFieldTypesWithSettings) to simply not return any data anymore for the field types that should be hidden. I can imagine this leads to the error you are describing when hidden field types are already in use. We did not test this use case unfortunately.
Umbraco should be integrating most of the functionality in this package into Forms core soon in which case the Forms core team will take over support. I am not sure I'll get around to fixing this issue beforehand. I just updated the package to be compatible with Forms 6 today and this was about all the time I could spare for at least another week.
I suppose we could simply not hide any built-in Fieldtypes to begin with and leave it all to the user, but the idea was it might not be known to the user it is possible to hide field types at all, which is why by default we hide all Umbraco fields for which we made some alternatives.
Regardless, I will add this issue to the Known Issues list on the package page now. Thanks again for bringing this to our attention!
Hiding default field types causes error
If you install perplex on a site containing existing forms, and these forms contain fields perplex hides by default, it causes a client dependency error.
This causes preview of fields not to be shown and fields being uneditable. Unhiding the fields types in the config files fixes the error, returns preview, and makes fields editable again.
Hi Claus,
Thanks for the bug report, good you already found a workaround for this issue. We "hide" the fieldtypes by altering an API call in Forms (
getAllFieldTypesWithSettings) to simply not return any data anymore for the field types that should be hidden. I can imagine this leads to the error you are describing when hidden field types are already in use. We did not test this use case unfortunately.Umbraco should be integrating most of the functionality in this package into Forms core soon in which case the Forms core team will take over support. I am not sure I'll get around to fixing this issue beforehand. I just updated the package to be compatible with Forms 6 today and this was about all the time I could spare for at least another week.
I suppose we could simply not hide any built-in Fieldtypes to begin with and leave it all to the user, but the idea was it might not be known to the user it is possible to hide field types at all, which is why by default we hide all Umbraco fields for which we made some alternatives.
Regardless, I will add this issue to the Known Issues list on the package page now. Thanks again for bringing this to our attention!
Regards, Daniël
Cool. I can live with having all fields available. I just wanted a post here if others ran into the same problem.
is working on a reply...