Content api is not compatible with custom repositories.
So when the custom repo is created (com.enonic.formbuilder) we can not use the content api on it.
This started to fail in 7.3 as /contet folder is treated differently.
Will have to create a seperate handling of the custom repo when saving form reports etc.
Content api is not compatible with custom repositories. So when the custom repo is created (com.enonic.formbuilder) we can not use the content api on it. This started to fail in 7.3 as /contet folder is treated differently.
Will have to create a seperate handling of the custom repo when saving form reports etc.