Export not exporting cms_class data.

Richard Coady asked on August 23, 2019 12:26

Hi,

I have an external dll to process scheduled task, which work ok. I setup a module to store the settings for my scheduled task.

I wanted to access the setting for the module in my external dll, so I copied my provider from app Kentico11\CMS\App_Code\CMSModules\SensorPro etc to my external dll.

I deleted the code from Kentico11\CMS\App_Code\CMSModules\SensorPro directory now that i hav eit in my external dll.

All works ok until I export my module, when I install my module it does not create the record in the cms_class table for my module, I have checked the database. The record does seem to be in the cms_class.xml.export file. When I look at the module config the classes tab is blank.

If I leave the code the Kentico11\CMS\App_Code\CMSModules\SensorPro directory, when installed we now have a clash or providers as it exists twice once in my dll and once in my code.

Is it possible to export a module without the code existing in \CMS\App_Code\CMSModules\SensorPro

Thanks for your help.

module export

Recent Answers

Brenden Kehren answered on August 23, 2019 13:58

Did you put the settings in the settings of the custom module? If so those aren't stored in the cms_class table. The only records stored in the cms_class table are the definition of objects like system, custom, forms, page types and classmodule tables. The actual record for the module is stored in the cms_resource table. The settings are stored in the cms_settingskey table.

Hopefully this will help with your development.

1 votesVote for this answer Mark as a Correct answer

Richard Coady answered on August 23, 2019 14:32

Thanks for the pointers, I think the issue is more fundamental after I install the module the list gives an error of [UniGrid]Error during reloading data. When I try to add a new record I get

Server Error in '/Kentico11' Application. [DataClassInfoProvider.GetClassStructureInfoFromDB]: Class information for class 'SensorPro.Configuration' not found.

It seems to work perfectly, if I just leave the provider code in the CMS\App_Code\CMSModules\SensorPro directory. Ehen I delete this and move to my external dll I start getting issues. The dll is installed in the bin directory.

0 votesVote for this answer Mark as a Correct answer