Thanks everyone for some great answers. I'll extent some a bit.
> 2) I'm using Swiki for my personal site and I'm a bit worried about
> some malicious surfer coming along and screwing it up. However, I
> don't want to click "lock" on every new page I create and I'd
> rather not be inserting passwords all the time. Is there a way to
> lock all my pages so that only if someone goes to
> http://server/swikiname/admin and then logs in then they can
> add/change pages but no one else can?
As Mark said, this is easy to do with the admin tool. Just do this:
1. Go to the admin tool.
2. Click on the swiki you want protected in the left-hand column.
This gives you the setup for that swiki.
3. Press the security button.
This gives you the security for that swiki (default is none).
4. Click 'create security profile'.
This creates a security profile.
5. Select 'Append' for default privilege.
This allows users without a username:password to be able to read
the site and use append areas.
6. Put in a username:password pair in the Allow Anything field.
Thus, when users want to edit a page, etc., they will be asked
for a username:password.
7. Click 'update security' to update these features.
> b) I do like the idea of people being able to add stuff to the site
> though, so, say some malicious person does come along and they
> delete all the pages, how long would it take me to fix? Is there
> an unlimited number of "roll-backs" so even if they changed it say
> 50 times I'd still not lose the content from presentversion - 50?
There is an unlimited number of versions allowed. There is no rollback
function since we have not needed one.
> 3) Is there a document about making new themes?
Nope. But it should be fairly easy to do. Since I just recently finalized
the themes format, I haven't had time to document it yet. Basically, it's
easy. Do this:
1. Go to the /swiki/default/files/ directory. There, you will find the
color schemes.
2. Duplicate the color scheme you like and label that directory with
the new color scheme name.
3. Open the index.html file in that new directory in your browser.
That will show you all the image files that need to be replaced.
This can be quite daunting (50+ files).
a) The simple icons (view.gif, edit.gif, etc.) are the ones that
show up when they are a link to that page.
b) The ones ending in ie (viewie.gif, editie.gif, etc.) are the
ones that are "in effect". For instance, the front page is also
the top page, so the top button is "in effect" as is the view
button.
c) The ones ending in bw (viewbw.gif, editbw.gif, etc.) are the
ones that show up for page icons (view, edit, etc.) when a
book function is in effect. Click on the search or help button
to see them.
d) The ones ending in help (viewhelp.gif, edithelp.gif, etc.) are
the ones that show up on the help page.
e) The ones ending in act (viewact.gif, editact.gif, etc.) are only
used in roll-over situations. Thus, only the roll-over schemes
have them.
4. After replacing the images, you may want to replace the alternate
tags. Edit the tags.xml file. Each icon file has an associated
alternate tag.
5. If you are familiar with HTML, you can edit the files ending in .sm
(Swiki Markup). These are the files you can edit:
afterHead.sm inserts itself into the header.
colorScheme.sm inserts itself into the body tag to specify the
colors (background, etc.)
beforeButtons.sm inserts itself in the body before the buttons.
divider.sm inserts itself between page and book buttons.
afterButtons.sm inserts itself into the body after the buttons.
endBody.sm inserts itself at the end of the body.
bar.sm is used as a horizontal-line separator.
After restarting the server, your new scheme will appear next to the
others in the colorScheme settings of each Swiki.
> 4) When I upload an image to a site is there a way to make the default
> option "don't put a reference on the bottom of the page"?
Yes. Use the Swiki Browser. Edit the uploadLocked and uploadUnlocked page
templates of the refs swiki.
Peace and Luck!
Je77
