On Sun, Jun 27, 2010 at 6:14 AM, DrunkenMonk <[email protected]> wrote: > Ingroup is used to test other users as well. It's the biggest problem.
Not sure what you mean here. Ingroup can be remapped as desired. But I don't think it is necessary if you have set the session variables properly. > Not being able to define myLogin means I can't use default skins and > sites. It's really annoying. I just want to enable a plugin and have > it work. No, with toolmapping, you won't need to change the login forms. That's the beauty of it. > Also, I'm thinking detailed knowledeg of BoltWire shouldnt be needed > to extend it. Actually, it's pretty easy. Just takes one line like this in your config.php file: $BOLTtoolmap['x']['login'] = 'mylogin'; Use x for commands, f for functions and c for conditions. The 'login' is the name of the command in the system and the 'mylogin' is the name you want it mapped to. Then create your BOLTXmylogin function like any other command (function/condition). BoltWire will automatically substitute your mylogin function for the core function whenever it encounters a login command. This is so easy and effective, I hesitate to add another layer of customization unnecessarily. I just posted a tutorial on toolmapping. http://www.boltwire.com/index.php?p=docs.extend.toolmaps Cheers, Dan -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
