UPDATE `cms_databases` `cms_databases`  SET `database_use_categories`='1',`database_allow_club_categories`='1',`database_template_categories`=NULL,`database_template_listing`=NULL,`database_template_display`=NULL,`database_template_form`=NULL,`database_cat_index_type`='0',`database_use_as_page_title`='1',`database_comment_bump`='0',`database_record_approve`=false,`database_tags_noprefixes`=false,`database_featured_settings`='{"featured":0,"perpage":10,"pagination":null,"sort":"record_publish_date","direction":"desc","categories":0}',`database_field_sort`='primary_id_field',`database_fixed_field_settings`='{"record_image":{"image_dims":[0,0],"thumb_dims":[200,200]}}',`database_fixed_field_perms`='{"record_image":{"visible":false,"perm_view":"*","perm_2":"*","perm_3":"*"}}' WHERE database_id=1 
IPS\Db\Exception: Column 'database_template_categories' cannot be null (1048)
#0 /Applications/AMPPS/www/system/Db/Db.php(1159): IPS\_Db->preparedQuery('/*invision::roo...', Array)
#1 /Applications/AMPPS/www/system/Patterns/ActiveRecord.php(520): IPS\_Db->update('`cms_databases`...', '`database_use_c...', 'WHERE database_...')
#2 /Applications/AMPPS/www/system/Node/Model.php(2530): IPS\Patterns\_ActiveRecord->save()
#3 /Applications/AMPPS/www/applications/cms/sources/Databases/Databases.php(945): IPS\Node\_Model->save()
#4 /Applications/AMPPS/www/applications/cms/modules/admin/databases/databases.php(1492): IPS\cms\_Databases->save()
#5 /Applications/AMPPS/www/system/Dispatcher/Controller.php(107): IPS\cms\modules\admin\databases\_databases->form()
#6 /Applications/AMPPS/www/system/Node/Controller.php(69): IPS\Dispatcher\_Controller->execute()
#7 /Applications/AMPPS/www/applications/cms/modules/admin/databases/databases.php(44): IPS\Node\_Controller->execute()
#8 /Applications/AMPPS/www/system/Dispatcher/Dispatcher.php(153): IPS\cms\modules\admin\databases\_databases->execute()
#9 /Applications/AMPPS/www/admin/index.php(13): IPS\_Dispatcher->run()
#10 {main}

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

This issue was resolved in our latest release of the platform. Please upgrade to resolve this, and if you see any further issues, please let us know.