16
An apology is in order.
The usage of group permissions has turned out to be more complex than I expected. I have successfully assigned permissions on a column basis, but I'm at a loss when defining the blocks, because they need to scan the whole repository of articles and take out of the list those articles whose column should not be seen by the present user. The logic behind my blocks is wrecked, and I'm waiting for some kind dev to enlighten my darkness...
It would be easier, perhaps, to take out the permissions stuff and just grant view rights using the system permissions, but now this has turned into a kind of challenge, and I intend to solve it.
When? As Shakespeare said: that is the question. For the moment, I don't want to wreck more functions, so my advice would be: Soapbox is quite usable as it is, but not its blocks. When you're the webmaster, or when you give all users all rights, everything is ok, but as soon as you begin to granularize rights, things break down.
Unfortunately, I don't have yet the wits to solve this in a flash of genius, so please bear with me.
To ease a bit, I'm now creating a Soapbox clone that will act as a glossary module and that won't have category rights. I hope this will make things a bit easier and could actually give me a module easier to explain in a handbook about module making.
Again, sorry for these delays. I'm learning in order to be able to teach, and it's not always easy when you have such a backlog against you...
Cheers.