Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
It seems that if a user doesn't have an account, or permission to edit the view, then they don't get to see any fields that are set to editable.
Comments
Comment #1
markfoodyburton CreditAttribution: markfoodyburton commentedI know, rubbish isn't it!
It's anoying me big time....
Ahhh --- time...
If/when I have time, I'll try to fix it, meantime - anybody else with good ideas?
Cheers
Mark.
Comment #2
PMatwyuk CreditAttribution: PMatwyuk commentedI'm going to assign myself to this as I think I know where the issue rests. If it's successful then I'll add the steps to which code to modify and if I have the time write a patch for it.
Comment #3
mdowsett CreditAttribution: mdowsett commentedI have the same issue. And it's for anon users and they just have permission to see the view (not edit). They can see non-editable fields but not editable fields.
For now, I just change the view from table to editable and back when I want to edit stuff....a pain, but it work.
Looking forward to a fix as this module is key to many of my views.
Comment #4
Island Usurper CreditAttribution: Island Usurper commentedWait a minute. What are users without edit access supposed to see? I would think it makes more sense to have two views: one for viewing and one for editing.
Comment #5
markfoodyburton CreditAttribution: markfoodyburton commentedMMm, I'm about to beat myself up more..
Yes, your right, you can get round this by having 2 views.....
But....
What a load of pain! - this is a bug and it should be fixed... the problem is time :-(
Comment #6
markfoodyburton CreditAttribution: markfoodyburton commentedFixed this
it's a one - liner...
just need to set the options to 'default' in the field....
(and that answers the question - you're going to get the default behaviour if you can't edit the field)
just add:
$field['options']='default';
around line 280
If you like the fix, I'll check in and release.
Comment #7
Vacilando CreditAttribution: Vacilando commentedWorks nicely; please apply the patch!
Comment #8
markfoodyburton CreditAttribution: markfoodyburton commentedDone
I've also added support for cck_field_perms - which is quite nice :-)
Hope it works :-)
Comment #9
Vacilando CreditAttribution: Vacilando commentedThanks for the patch, and for the perms handling - it really was missing. Cheers!
Comment #10
mdowsett CreditAttribution: mdowsett commentedgreat! It does seem to work...for the most part.
IF there is data in a field, the user can edit it. But if there is no data present in the editable field, you can't add new data.
Is there a fix for that? Will this be submitted as a proper patch? and into the next revision of the module?
MANY thanks.
Comment #11
markfoodyburton CreditAttribution: markfoodyburton commentedthe latest version has this patch in it.... but the 'no data' thing is different.
Could you add a separate bug for that - for what it's worth, I've noticed something similar, but if I add the data twice, it seems to work!!!!!!!
Cheers
Mark.
Comment #12
mdowsett CreditAttribution: mdowsett commentedthx - I just updated and it still works (for the anon users seeing the data).
I'll enter a new support request for the other.
Comment #13
mdowsett CreditAttribution: mdowsett commentedI found an issue with your fix above. I noticed that after I added that line my "Event: Start Time" field's custom date that I had set in my view changed to a strange format...I also had a "Node: View link" field in that view and it's optional title field reverted to read 'default' instead of the custom text I had been using prior to your fix.
I removed the line and it went back to functioning as it was before...the custom field data worked but the anon users can't see the data again.
Is there another fix that help with all of this?
Comment #14
mengi CreditAttribution: mengi commentedPer https://drupal.org/node/2148735, 5.x is longer maintained so issue is closed.
Comment #15
mengi CreditAttribution: mengi commented