Custom Module sealed at creation

L B asked on April 23, 2018 09:29

Hi team,

We encountered a bug with custom modules being not in development state when we create them.

You click new module
Fill the form
Set the sites to the one you want
Blocked when we try to change the permissions/add classes as it said the module it is sealed.

We investigate and figure that in the CMS_Resources database the 'ResourceIsInDevelopment' field is set to 'NULL' instead of 'True'.

So the only way to actually create new modules is to update this field in the database each time, for now we will do that, but if we can fix it. It would be great.

We are not sure if it is a bug or if there is a setting somewhere, we did try to find something about it but we end in 'Create new module' or 'How to unseal modules' tutorials.

Anyone encounter this issue before ?

Cheers.

Recent Answers

Michal Samuhel answered on April 23, 2018 12:20

Hello,

If you could clarify your process, especially after creation would be helpful, but in general modules are sealed once they are installed on another machine or instance. Custom module development should be taking place in one instance (code base) and only finished module should be transferred further. This is mentioned in custom module documentation although more briefly.

You already mentioned you are using scripts to unseal module which is a valid workaround and was already discussed in here.

0 votesVote for this answer Mark as a Correct answer

L B answered on April 23, 2018 13:28

Hi Michal,

Thanks for your help but I speak about a new module, not finished, I almost want to say not even started yet.

I don't know how I can make it more clear about the process, when I say step 1 Click on create new module. I literally go to the module page and click create new module and then do the other steps.

The unseal process we used is only because the module creation does not perform the job properly and lock it directly at creation (not export, not transfer).

0 votesVote for this answer Mark as a Correct answer

David te Kloese answered on April 23, 2018 13:38

Is it clean installation and what hotfix version are you on?

0 votesVote for this answer Mark as a Correct answer

Vukasin Andjelic answered on April 23, 2018 13:41

Hi L B,

try to clear the cache and restart application in System app, maybe that helps.

Best regards

0 votesVote for this answer Mark as a Correct answer

L B answered on April 24, 2018 01:14

Hi,

Restart the application was not helpful (I already tried that before posting a request...)

Yes it is a clean installation of Kentico 11. For the hotfix I suppose there is no applied yet as the CMS.Core dll display version 11.0.0

It seems to be a bug, hopefully it will be fixed in the hotfixes.

If Kentico team need more information don't hesitate to ask.

Cheers.

0 votesVote for this answer Mark as a Correct answer

Trevor Fayas answered on April 24, 2018 13:59

I would first hot fix to the latest hot fix, if it still doesn't work then report as a bug. I personally haven't had any problems with creating modules in version 11 but I haven't tried on hot fix 0

0 votesVote for this answer Mark as a Correct answer