Thank you for contacting us.
Can you please give me more info for the module you created (module fields, restrictions if have any) and how exactly you tried to update them so that i can reproduce the errors?
Also I want to ask you if the rest of Sitefinity is working properly after you received this errors on Module Buider and if you can, please send me the Logs located under App_Data -> Sitefinity -> Logs.
Thank you in advance.
Thank you for bringing up this topic. We are aware of this issue. The problem is when you have created a module and after that you try to edit the fields to add or remove classification or media fields. We are working on this problem and hope that we can resolve it as soon as possible.
As I said previously my advise is for now to start on a clean project, plan carefully what your module is going to look like and create it. When you are sure that this is the module that best fits your needs recreate it on the production environment. Also make sure that you make backups before major changes. For now we are focusing on fixing issues in the module builder and stabilizing it and we hope that you won't experience such problems in future. Please excuse us for the inconvenience caused.
I'm on version 5.1.3450.0 and getting the same issue.
Created a custom module for the project with 2 content types. Everything worked perfectly. Both content types have a custom classification field and one has an image field. Now 2 days before the project deadline I tried to add a 3rd content type and got the message "There has been an error updating module fields!".
The site and module continues to function properly, but the changes are not applied. Log files have not been modified - I can find no trace of the error.
One potential problem I suspect is that the files in Configuration folder had been checked into source control and I did not check them out prior to doing the update. I had since checked out all the files in the project and tried to re-create the custom content type but got the same error message.
Have there been any updates on this issue?
I would rather not have to re-create the module again as there is a lot of code referencing the module and we are 2 days from the deadline.
I have tested this on a clean project and it is not reproducible. It is possible the problem to come from the read only configuration files. If possible send us your project so we can make a deeper research.
Most probably the source of the problem is different and we will do our best to fix it.