How to make some categories not selectable?

Hi all,

I am using FLEXIcontent version 2.0.0 RC9 (r1514) on J2.5.7.

I want any front-end users to create items only for last level of categories.
Thus, They will not be able to select categories except last level on item submission/edit form.
In the form, category drop-down shows all of specified category tree but top and middle level of categories will be grey out and only last level will be selectable.
Which file do I have to override?

Regards

in menu option of submission you can override categorie selectable

Micker, Thanks for your reply.

I know that there is an option to select categories to show on Item submission form. If category is with 2 levels then no problem.

For example, 3 level category:
Used
|_ car
|_ BMW ->selectable
|_ Toyota ->selectable
|_ Other ->selectable
|_ bike
|_ BMW ->selectable
|_ Honda ->selectable
|_ Other ->selectable

Result will be:

BMW -> user don't know parent category
Toyota
Other -> user don't know parent category
BMW -> user don't know parent category
Honda
Other -> user don't know parent category

There are categories has same name.
That' why I want to show all of category tree and disable top and second categories not to selectable.

Any other way to achieve this please?

you cant, I have requested this feature in the past, but it is very hard to do.

How do you think this should be done?
Per user? per type of content? per category? per configuration?

I was thinking per type of content but This is not implemented in FC

I think giving disable option to category is easy for us and there are a lot of extensions covering category than type. Do you know which file to edit? I want to try it by myself.

algardata wrote: you cant, I have requested this feature in the past, but it is very hard to do.

How do you think this should be done?
Per user? per type of content? per category? per configuration?

I was thinking per type of content but This is not implemented in FC

It is possible to do for the item edit form,

the category tree is generated by a common helper function, which would only need only a couple of lines to do it, since the needed information is already available ...

You think it is worth it? we would do it by a Global Parameter overridden per Content Type?