[AndrewD]

Originally Posted by Tulsa

Why both of course.

This is only a partial solution - there are a couple of other changes which are needed to make it complete/clean.

Edit includes/local_links_admininclude.php. Scroll down until you find groups of lines which look like the following:

require_admin_row($seq++, 'title_data_entry', 'll_settings_title_entry', 'title_perms', 1, 1);
	require_admin_row($seq++, 'can_add_link', '6,-1', 'usergroup_check', 1);
	require_admin_row($seq++, 'can_link_files', '2,3,4,5,6,7,-1', 'usergroup_check', 1);
	require_admin_row($seq++, 'can_upload_files', '6,-1', 'usergroup_check', 1);
	require_admin_row($seq++, 'can_select_category', '2,3,4,5,6,7,-1', 'usergroup_check');
	require_admin_row($seq++, 'can_edit_link', '6,-1', 'usergroup_check');
	require_admin_row($seq++, 'can_delete_link', '6,-1', 'usergroup_check');
	require_admin_row($seq++, 'can_add_category', '6,-1', 'usergroup_check');
	require_admin_row($seq++, 'can_edit_category', '6,-1', 'usergroup_check');
...
require_admin_row($seq++, 'close_data_entry', '', 'close', 1);

Each line defines a parameter setting/permission. When there is a fifth parameter set to 1 (as on the can_add_link line), then the permission can be set at global level and at category level. Otherwise, it can only be set at global level.

So to make can_add_category and can_edit_category permissions avaiable on a per-category basis, simply add ", 1 at the end of the lines:

	require_admin_row($seq++, 'can_add_category', '6,-1', 'usergroup_check', 1);
	require_admin_row($seq++, 'can_edit_category', '6,-1', 'usergroup_check', 1);

Save, then (important) reinstall the LDM product installer via the vb admincp.

Then, these permissions become available on the Add/Edit Category forms, on the third tab (User Group Permissions). If you deny the permission globally and enable it in one of your categories, then the relevant user group can only create subcategories in that category.

As I said, this is not a complete patch - You will find that the 'add category' form always includes a parent category selection box, allowing people to place the new subcategory somewhere else in the category hierarchy. This is probably not what you want. For some reason, I had overlooked to apply the *can_select_category* permission to category creation. I will fix this in 2.2.8.

My answer about users always being able to edit their own categories was also not completely accurate. There's another bug so that the relevant Edit Category menu item does not get displayed even though the user actually has permission to do the edit. This will also be fixed in 2.2.8.

So you may prefer to wait.