Form Customization Rules not working in 2.0.2

I have recently installed 2.0.2 and cannot get form customization rules to work. They work fine on my 2.0.0 site but on a stock install of 2.0.2 they don’t work. I’ve tried everything: stripping it down to just one "test" rule, clearing site cache, browser cache, flushing permissions, restarting browser, logging out/in, deactivating/activating the rule, re-creating the rule from scratch, etc. For whatever reason a Form Rule works in 2.0.0 but not in 2.0.2.

Anyone else having this problem? Any ideas?

They work for me; what browser are you using? What are some of the rules?

Tried it in Chrome, Safari and Firefox.

I’ve tried Field Label, Field Visible, Tab Title and Tab Visible.

At this point my only action left is to completely wipe the site and try re-installing it from scratch... maybe the form customization code got mangled in the upload or something?

Maybe, was this a traditional or advanced download?

Traditional, no packages installed. I did however enable friendly url’s and a couple other system settings before doing the form rules so I’m thinking I’ll re-install and do form rules right away first before touching anything else.

Thanks for your attention and help on this.

Quote from: entica at Sep 20, 2010, 07:20 PM

Tried it in Chrome, Safari and Firefox.

I’ve tried Field Label, Field Visible, Tab Title and Tab Visible.

At this point my only action left is to completely wipe the site and try re-installing it from scratch... maybe the form customization code got mangled in the upload or something?

Or some files didn’t get overwritten when you transferred the new version. It definitely happens (I’ve had the problem with FileZilla) and it does sound like a bum install.

FC rules may be a bit broken in 2.0.2; we’re working on resolving the issue. As soon as github lets me push to it today, I’ll post a patch.

Great! Thanks for the quick response to the issue(s) and thanks in advance for the patch later today.

Here’s something else I’m noticing with FC Rules in 2.0.2. If a user is a member of multiple user groups, where one of those groups has a rule that denies access (say, field visible) then that user is denied access even though he is a member of other user groups that do have access.

I thought the general approach in MODx was to grant a permission if a user has access through any means. FC Rules certainly seem to work this way in 2.0. For example, if there is another user group named Editors and a user is a member of both the Administrators and Editors user groups, if I then create a FC Rule that turns off longtitle for the Editors then it will also be turned off for that user in 2.0.2. In 2.0 he would still see the field, which is the behavior I expect.

I doubt this is related at all, but let me pass on something slightly similar. I had created a few custom permissions on the administrator policy to turn off certain menu items using Actions & Menus. When I upgraded to 2.0.2 it was as though those permissions were missing in the policy. What finally seems to have corrected it was when I created yet another custom permission on that policy. Once that was saved, suddenly the other custom permissions started getting properly applied.

Any update on this Splittingred? Any luck with Git? Where will I need to go in order to download a patched version?

Thanks!