Category permissions have changed significantly in 1.10. Most notably, in order to edit content in categories, a user needs tiki_p_edit_categorized. This permission needs to me manually assigned to groups in Category Admin? and Groups Management? individually.
If you understand the impact of the following Category Perms MySQL queries, you may use them to facilitate your upgrade. However, note that these queries give users that previously had the ability to view content in categories to edit the content as well. This may not me what you intend. The safe way is to configure permissions manually.
INSERT INTO users_grouppermissions (groupName, permName, value) SELECT groupName, 'tiki_p_edit_categorized', '' FROM users_grouppermissions WHERE permName = 'tiki_p_view_categories'" ); INSERT INTO users_objectpermissions (groupName, permName, objectType, objectId) SELECT groupName, 'tiki_p_edit_categorized', objectType, objectId FROM users_objectpermissions WHERE permName = 'tiki_p_view_categories'" );
Also, if you had upgraded using the Tiki installer, then users that previously had the ability to view content that is categorized will continue to have them. If you however, upgraded by manually running 1.9to2.0.sql, there are some queries here that you may have to run Category Perms MySQL queries.
INSERT INTO users_grouppermissions (groupName, permName, value) SELECT groupName, 'tiki_p_view_categorized', '' FROM users_grouppermissions WHERE permName = 'tiki_p_view_categories'" ); INSERT INTO users_objectpermissions (groupName, permName, objectType, objectId) SELECT groupName, 'tiki_p_view_categorized', objectType, objectId FROM users_objectpermissions WHERE permName = 'tiki_p_view_categories'" );