I'm completely new to BoltWire. One of the first things I want to do
is completely lock down the site. This may seem like an odd thing to
do for a wiki, but while I'm learning how to use and administer the
wiki, I want to make sure that nobody else goes for a joy ride on the
completely wide open site.

First off, I want to say how incredibly easy the actual installation
was. It was "up and running" in a matter of almost seconds. The
additional tweaking (moving the barn and farm out of web readable
territory) took only a few extra minutes.

So, now I want to:
1) prevent anyone from registering new accounts
2) prevent anyone from viewing or editing any pages

Next, I want to:
3) Add email verification to the registration process.

I think I accomplished step 1 by editing the "site.auth.view" and
changing one line:
"action.register: @guest" to "action.register: @member"

I think I accomplished step 2 by editing the "site.auth.view" and
changing one line:
"*: @guest" to "*: @member"

Can someone please confirm that the above changes will prevent anyone
(other than me) from doing anything on the site (at least for the time
being)?

Now, on to step 3. The email verification plugin says that I need to
"Make sure you have the email plugin enabled". However, I can't seem
to actually *find* the email plugin. All the links point to "http://
www.boltwire.com/index.php?p=solutions.email", which is a list of
email plugins, not a plugin itself. The email "Concepts" page (http://
www.boltwire.com/index.php?p=docs.concepts.mail) also has links to the
email plugin that point to the list of plugins. Based on the email
concepts page, it is unclear if I still need the email plugin in order
to use the email verification plugin.

Can anyone post simplified step-by-step instructions of how to get
email verification going?

I'm currently trying a couple different wikis, trying to find the best
fit. BoltWire looks like a really cool wiki engine, but the
documentation wiki seems to be a mess of outdated documentation and
broken links. Is this because:
a) BoltWire is in such a state of flux the documentation can't keep up
b) BoltWire just underwent a huge change and the documentation is
still being revamped
c) The documentation itself is being reorganized, or
d) Some other reason?

- Ben
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to