On 23/03/07 13:12 -0400, Keith A. Carangelo wrote:
> Hello,
> I'm new to Kwiki, but it looks very promising and I'd like to help in some
> way.
>
> Right now, I'm trying to get the Kwiki::Users::Remote plugin to work, but
> I get "Error: Kwiki::Users::Remote is not a plugin class."
>
> I think this is because Kwiki::Users::Remote is a descendant of
> Kwiki::Users,
> but Kwiki::Users isn't a plugin. Is there an easy way around this?
Keith,
In a the better Kwiki World of the Future, all classes are plugins.
But for now, some of the classes are *core* classes.
Luckily it's equally trivial to switch out a core module as it is for a
plugin. You just do it differently. Just add this line to config.yaml:
users_class: Kwiki::Users::Remote
Every class, core or plugin has a class type. And there can only be one
class of any particular type at a time. That's how Kwiki works.
These are the classes that are currently core:
* cgi
* command
* cookie
* css
* formatter
* headers
* hooks
* javascript
* pages
* paths
* preferences
* registry
* template
* users
This is easy to see in:
http://svn.kwiki.org/kwiki/trunk/src/core/Kwiki/lib/Kwiki/Boot/V1.pm
Cheers, Ingy
PS. You /are/ using Kwiki from svn and /not/ from CPAN, right? :)
