Allen Gilliland wrote:
i also like that you've redone the permission table, which seems to
simplify things as well, but can we carry that on from my suggestion
above and just store all permission data in that table, including
roles and weblog permissions? would that work?
this way if you add
Dave wrote:
Yes, when Roller is used with an externalized perms system the
existing Roller permssions UI should be disabled, do we also need
links to the external perms management UI?
Hi Dave,
It'd be nice to have the option, yes. I think the permissions UI stuff
might be a little more complic
Hi Dave and others,
Looks like an interesting start. Here are some comments :)
On externalizing user management...
Abstracting the directory of user profiles: In 2.1.2 (Possible
solutions), possible solution #1, you state that the user object is
needed because it's used in joins and queries.
Hi,
I'm a software engineer at Lulu.com. As part of the community features
on our site, we allow users to maintain blogs there. However, the system
that is currently implemented is very old/slow/ugly/hated. We have a
relatively large user base, but only 6k have ever posted to their blog,
and
