Form Customization | Publishing 'Glitch'

I'm currently working on form customization and ACLs (woot) and having a good time with it. One issue I'm coming up against while testing:

I set the 'create' form to show 4 fields, one being the "Published" checkbox one would normally see. The user fills in pagetitle (required) + other fields and hits save to continue.

I set the 'update' form to have the rest of the TVs I want them (the user) to fill out.

The issue: once I hit save, the form reloads (as one would expect on save), but "Published" is now unchecked.

Thoughts?

I wonder if there is a way to have the default value of that field set to the current published status of the Resource on update. That should be done automatically, but it sounds like it isn't happening (unless you're setting the default value to 0 yourself in an FC rule).

Quote from: BobRay at Oct 28, 2013, 01:53 PM

I wonder if there is a way to have the default value of that field set to the current published status of the Resource on update. That should be done automatically, but it sounds like it isn't happening (unless you're setting the default value to 0 yourself in an FC rule).

What's interesting is that even if I check publish and save again, it stays unchecked :\

FIXED

It was the Access Control -> Access Policies. The template for that Policy the user is in doesn't allow publishing/unpublishing.

I'm hereby renaming ACLs, "Trail and Error"

:)

Good idea.

Sorry to resurrect an old thread but I seem to be having a problem with this as well using ver 2.2.14 when logged in as super admin. Interestingly though, another site for which the form customization was set up on an older version was working fine and still is since being upgraded to 2.2.14

Can anyone suggest a way of debugging this?

Do you have any Resource Group Access ACL entries affecting the resource? Make sure that the policy that affects the users gives them permission to publish a resource. Also check the Context Access ACL entry for the users for the same thing.

Hi Bob,
Thanks for chiming in. This was happening with not only an "editor" type user but also the default admin "SuperUser' role on a customization policy that had been modified over time. Part of that modification was to move a couple of TVs to a different region and give them a ranking, before ultimately deselecting them from use altogether. However, what was not deleted was the settings for their rank or the regions they were moved to.

I ended up testing this by deactivating the policy and testing the document form. That worked fine - when the resource came up, the "published" button was checked and when it was saved the display refreshed, showing the document as published. I then reactivated the policy and checked *everything* that was available, which I expected would have been equivalent to turning off the customization. That showed the problem - namely that when a document was created, it started out as "published" but when saved returned as unpublished (and showed that state in the resource menu on the left). At that point, I could not publish it from the form.

Not knowing at that juncture what could cause the problem, I created a new policy (I did not duplicate the policy) and only checked off what I wanted customized and what I wanted to be shown in various regions. *That* worked when I deactivated the old "bad" policy and activated the new one. When I exported the old policy and its new version, and did a file compare, I saw that the only differences were for some settings on TVs that were not being used.

So at this stage, I believe the problem is solved and that it is related to how the policy was modified over time, ie with some "leftover" values on some elements tripping up the publishing of the document. I don't know why this would be the case and I guess the issue could be something else that has been inadvertently fixed. Later this evening I can upload the two exported policies if anyone would care to see the differences firsthand.

Again, thanks for your help. And for the help of everyone else on these forums.

Matt

Leftover TVs can cause weird problems, especially when mixed with permissions and Form Customization. They might qualify as bugs, but they're very difficult to replicate. They shouldn't interfere with publication status, but it's possible.