We have several Webform Components that are set to Private (and Disabled) with default values, which do not appear for Anonymous users when they are creating their submission, nor editing their submission, but DO appear when they are viewing their submission, which is not good.

There seems to be a similar thread open for the D7 version of Webform (https://www.drupal.org/node/1698438) but no notes on this for D6.

I've made sure Anonymous users only have the two following permissions in Webform:

X edit own webform submissions
X access own webform submissions

Both of which are required for Anonymous users to be able to view and change their submissions.

I also have Webform Conditional installed, and the Private Fields we have are set to be conditional to a non-private field, BUT I tested the form without any conditional values at all and Anonymous users could STILL see the Private Fields (with or without conditionals on them).

Could anyone help?

Comments

amaisano’s picture

Issue summary: View changes
DanChadwick’s picture

Priority: Major » Normal
Status: Active » Closed (won't fix)

As I said in the other thread, someone would have to port the patch and post it for others to use. The D6 branch is only receiving critical fixes, unless another maintainer cares enough to come forward and take responsibility for that branch.

The obvious alternative would be to just not use private field, or upgrade your site to D7, which I realize may be a big undertaking. Support for D6 is pretty sparse these days.

amaisano’s picture

Sorry I missed that note about back-porting. I understand the waning support for D6, but the private fields concept means fields that users w/o 'Access Results' cannot see them (which just doesn't work). If this feature is in the stable release, but does not achieve the concept at all, shouldn't it be at least a major bug? It is essential to hide certain information from anonymous users, so it's at least major to us, but again I will just hold out and hope someone patches, since I can't do anything about it besides your suggestions at the moment.

DanChadwick’s picture

Issue tags: -permissions

I think normal fits best because the bug only affects certain combinations of settings, not any overall major area of functionality. But if you want to set it to major, I won't object.

Since this bug affects you, and since there is no maintainer willing to put effort into this branch, I'm sorry to say that the onus to fix it will probably on you. That implies either that you fix it yourself (if you have that ability) or that you hire, sponsor or induce someone to do so. This isn't a nice situation, but it is the situation nonetheless.