[SOLVED] Form Customization not working when creating rules for more than 1 container...

I am in the process of creating a site for the MODX entire community to use for potential clients who first want to demo MODX. I often get the question when offering MODX as a solution to new clients: "What is it like to work in the CMS?". One of the things I'm trying to accomplish is to make the MODX manager really easy to use. I've been working on streamlining the Dashboard to help the clients move around and add/update resources quickly without having to work with the tree structure too much. The site is almost done and ready to launch, but I'm running into some big issues with form customization.

The site is using MODX 2.2.6-pl where I'm using form customization to control what template is inherited for a container when a user adds a new document in a container. I'm using form customization and the templates are inheriting correctly when adding a document into the container the way the rules are defined in form customization. Often the parent has one template and the child resources have different templates. This is important b/c often the parent and children have different T.V.'s and some fields are hidden on the parent document and not the child. The problem is T.V.'s are not showing up as they should for the child document added to the container. I have 4 containers in the tree where the I'm using form customization to control what template is inherited. If I disable some of the form customization rules for different child documents being created, then the T.V.'s show up on the document added to the container as it should. I've read through the forums and see that this has been a problem in the past, but I'm not seeing any solutions (did I miss something?). I've spent hours trying to find a pattern that explains this, but have come to the conclusion that there's something more involved I'm not seeing.

Please request more details and I'd be glad to provide them.

This is on a LAMP server. [ed. note: flinx777 last edited this post 13 years, 7 months ago.]

Hit me up and I can take a look...

Quick update on this posting...Everett has fixed the problem: http://tracker.modx.com/issues/9592 ... hopefully this patch will be integrated in all Revo installs newer than 2.2.6-pl