Closed (fixed)
Project:
Acidfree Albums
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2005 at 08:19 UTC
Updated:
21 Nov 2005 at 04:58 UTC
Jump to comment: Most recent file
Comments
Comment #1
vhmauery commentedwe are still working on node_access stuff. But there is a possibility that node_privacy_byrole is not playing well with acidfree.... It does work fine with some other node_access modules.
Comment #2
vhmauery commentedWhen the album contents view generates its form, it passes a prefix to the nodeapi 'form pre' call. Some modules seem to honor this when generating form controls, others don't. Can you load up your album contents view and check the source. Or it is possible that it puts its form item in 'form post'. Hmmm.
Does the control show up at all? I suppose if it doesn't show up, I might have to call 'form post' and paste that into the form too.
Comment #3
vhmauery commentedOkay, it shows up and I think that is about as much as we can expect Acidfree to do.
I looked into the problem and it is caused by the fact that node_privacy_byrole never expects to be used with more than one node on the form. Some other node_access modules use a $prefix when drawing the nodeapi 'form pre' form items. I have attached a patch that makes node_privacy_byrole do the same thing. If you apply this patch to the node_privacy_byrole module, it will work correctly for you. You might even consider opening a bug against that module and submitting this patch.
And I am closing this bug since it is no longer an Acidfree problem.
Comment #4
vhmauery commentedComment #5
inspiredbylife commentedAh, thanks for all your effort! I'll report a bug against node_privacy_byrole module and point them to the patch you have provided here. :)