[OPEN][Revo RC3] Manager Form Customization

Hi guys,

The warning above "Form Customization" in Revo RC3 kinda put me off, so I thought I’d take this nice and easy, and ask you guys for help. My client is a retard (let’s hope they don’t read this ), and I want to make things as easy as possible for them. So I don’t want to confront them with all sorts of fields an tabs that they’re never going to need (and might accidentally fill with something that shouldn’t be there). I want to do the following:

- If they select template "Project" when creating a document, hide the tab "Page Settings" and the tab "Template Variables", and show 3 TV’s in the main tab. I’d also like to hide several fields such as "Long title", "Menu index" and "Menu title".

Can you guys help me with this? Much appreciated!

Thanks!

I think everything you need is here: http://svn.modxcms.com/docs/display/revolution/Form+Customization.

Form Customization can be tricky to get working, but it’s harmless because you can always delete any and all FC rules and be back where you were.

Well I got started, but the documentation is rather wonky. For example, modx-page-settings is the name for hiding the "Page Settings" tab, but modx-access-permissions is not the name for the Access Permissions tab... Is this documentation available elsewhere?

I’ve been playing with the new MODx 2.0.0-pl Revolution release and can’t get the Form Customization feature to work. I’ve followed the docs and illustrations hoping to course some effect but nothing seems to happen

I think the docs are a little out of date. Can you say what you’re trying to do?

same problem here, tried to moved a tv to modx-resource-settings tab with no success, following the docs.
I can make it works for hiding fields, changing title, but no way to move tvs. (while editing resource)

action : resource/update
name : tv1 (id is ok)
rule : déplacer la variable dans l’onglet ("move tv in tab")
value : modx-resource-settings (id seem to be ok since it match id in css/html i saw with firebug)

the rule is activate...

what’s wrong

I think this is what you want:

I will try thaht, thanks