Last post Nov 15, 2005 05:28 AM by Daws
Jun 21, 2005 11:32 AM|toddhd|LINK
Jun 21, 2005 12:56 PM|toddhd|LINK
Ok, I figured it out, but I'm still not sure why DNN is working this way - is this a bug, or am I simply misunderstanding the way permissions work?
What I had to do was going into the PAGE settings (for the page the module is on) as opposed to the Module settings, and give registered users Edit rights to the
entire page. Then the module options showed up properly when I viewed the module menu.
Of course, what this basically means is that you can't set individual module rights, even though it appears that you should be able to.
Am I correct? Is everyone else getting the same thing?
Jun 21, 2005 02:22 PM|toddhd|LINK
Ok, here's the deal - maybe it will save somebody else some hair - I'm half bald as it is now...
The problem was that, with the new 3.1 model, when you add a new module, you are forced to add a cache time. I just took a stab at it, and put in a default cache time of 10 seconds.
According to the issue listed above, adding a cache time to the module negates the editing rights. And then Blammo! That's when the proverbial cream pie hits you in the face.
What I needed to do was set the cache time of the module to 0, and then all worked as expected.
Nov 15, 2005 05:09 AM|Daws|LINK
Nov 15, 2005 05:28 AM|Daws|LINK