lyceum-users AT lists.ibiblio.org
Subject: Lyceum-users mailing list
List archive
- From: John Joseph Bachir <jjb AT ibiblio.org>
- To: Fred Stutzman <fred AT metalab.unc.edu>
- Cc: lyceum-users AT lists.ibiblio.org, "David R. Woolley" <drwool AT thinkofit.com>
- Subject: Re: [Lyceum-users] User roles/levels
- Date: Mon, 6 Nov 2006 02:01:48 -0500 (EST)
For each blog on which a user has permissions, there is a permissions entry in the usermeta table.
The user_level field is, i believe, a legacy piece of the system that wordpress no longer utilizes and i believe is in there for the sake of plugin backward compatibility.
witness my lack of investigation, and general confusion, in this very old ticket:
<http://source.ibiblio.org/trac/lyceum/ticket/135>
But the bottom line is, there is no concept of per-blog user level. You can perhaps hack the plugin to store this information in the options table, or even better, to work with roles instead of levels.
let us know what you come up with, and/or document it on the wiki if you get the chance.
john
On Wed, 25 Oct 2006, Fred Stutzman wrote:
On Wed, 25 Oct 2006, David R. Woolley wrote:
At 10/25/2006 06:59 PM, Fred Stutzman wrote:
Hi David, and JJB or Jameson can correct me if I am wrong, but I don't
believe Lyceum creates a separate user record for each blog. The user
record is unary and maintains levels and blog_id's. Therefore, I think
that a viewlevel plugin would work, as it would be applied on a
blog-by-blog basis, interacting with the standard user table.
So then the Lyceum user record has a user level for each blog?
That's correct.
David R. Woolley
=======================================
http://thinkofit.com/drwool/
=======================================
--
John
----
aim/yim/msn/jabber.org: johnjosephbachir
713.494.2704
irc://irc.freenode.net/lyceum
http://lyceum.ibiblio.org/
http://blog.johnjosephbachir.org/
-
Re: [Lyceum-users] User roles/levels,
John Joseph Bachir, 11/06/2006
- Re: [Lyceum-users] User roles/levels, David R. Woolley, 11/06/2006
Archive powered by MHonArc 2.6.24.