disable specific sections of Articles??

I want to disable all the green options tabs for Articles such that only the Administrator user can see them, other manager users do not see them (template, advanced settings, comments, resource groups), only desired visible tab should be 'Articles.'

Thank you, Tom

I second this request. There should be a form customization hook to allow this.

-Mike

This is definitely a must for me too, having the 'Advanced Settings' tab there all of the time means my clients can meddle/break things.

Danny

Yes this is "must have" functionality. Someone has already added this on the official bug tracker (under a rather cryptic title). It might be worth adding your voices to that thread:

http://tracker.modx.com/issues/6652

Perhaps it is possible to do this with adding or removing certain access permissions for a particular user role. This system in ModX is very "mighty" but also very complex. I don't know if there needed to be some hooks in Articles to do this or if one can already add some restrictions that are releated to articles.

Actually that bug referred to a failure in Form Customization. That should have been able to hide the unwanted fields/tabs, but wasn't working as expected. If a setting in Articles is wanted to be able to perform this function, a new feature request should be submitted.

You can hide the tabs articles, templates, advanced settings and comments. Although there is a little thing with this.

In Form Customisation go to Regions, add a new tab and use the settings below to hide the tabs templates, advanced settings and comments:

Tab templates:
articles-tab-template

Tab advanced settings:
articles-tab-advanced-settings

Tab comments:
articles-tab-comments

When saving, leaving the form customisation and return back to it, all the added tabs in FC are gone. But no worries; the customisation does still work.


MODX 2.2.10 with Articles 1.7.5
[ed. note: michelle84 last edited this post 10 years, 4 months ago.]

If there's a bug in 2.2.4 that prevents FC from working correctly, has anyone submitted a bug report? 2.2.5 is coming out next week barring any unforeseen issues and we'd like to resolve it if it hasn't been already.

Hi Jay,

Thanks for your reply. Simmiliar bugs are reported earlier this year:

http://tracker.modx.com/issues/6652 and
http://tracker.modx.com/issues/7657

Should I file this bug again more specifically?

This technique worked for me in 2.2.6.