'Unseal' your custom installed modules

David te Kloese

Creating your own modules in Kentico is a great way to create that extra custom view or functionality. If you follow the Kentico guidelines in your setup, your clients will most likely think its part of the CMS itself. Since Kentico 8 you might find out the hard way that your custom modules are being sealed for edit after moving them to an other instance. How can you 'fix' this?

First of all: in Kentico 9 their will be an easy way to make sure your custom module can be adjusted in other instances. But until then you'll have to dive into the Database.

What does the message look like? When you'll navigate in you Kentico Admin interface towards your custom module via Modules > [Your module name]. You can see the following messages in the different elements of the module:

General "Properties on the General tab cannot be modified in installed modules. The other tabs remain customizable."

sealed module

Permission names "Permissions cannot be created or deleted in installed modules."

sealed module permission

Settings "Editing settings in installed modules isn't allowed."

sealed module setting

and so on.


If you want to edit this module you'll have to access the database. Be careful in editing the database directly. If you have no experience you might want to make sure you'll have a backup first. When in your Kentico database find the "CMS_Resource" table. Here you'll have to update the "ResourceIsInDevelopment" setting (boolean) of your custom module to 1.

Unseal SQL script
Make sure you update the correct module! Best to use the unique code name.

You might need to hit the "clear cache" button to see your changes. And your done!

As mentioned above, in Kentico 9 you'll be able to export modules including the "ResourceIsInDevelopment" flag.