Nicely presented Idea, I'd been thinking about doing this but you've just made it a lot easier! The Dutch connection example also has a side bar, might be worth adding a css / code stanza for that too. Cheers Ian

@DarTar,
when not logged in and double clicking the page to try editing I get the following error message
You don't have write access to this page. You might need to register an account to get write access.
I also get a link that says "View formatting code for this page".
Selecting this link allows me to see the page content. Can you tell me what I have done wrong?

James, that's the default message that, since 1.1.6.0 is displayed when you have read-access to a page but no write access. My default ACL settings, as explained in this page are !*-*-!*, with a couple of exceptions (some pages are also read-restricted), which means you can actually read the page (both formatted and as source). So nothing strange, you should get the same error message and source-view-link when you try to edit http://wikka.jsnx.com/HomePage. Hope this helps.

Thanks DarTar. Now that I know it is a default setting, I understand now.
To lock the site down completely, the acls should be !*-!*-!*
and only the HomePage or other insensitive pages amended to allow visitors read access.

Precisely. Of course, you shouldn't forget to let at least your login page read-accessible if you don't want to lock you out of your site!

I found that out too. Thanks --JamesMcl.

Hey there everybody
If you want to add comments on a single page, create this file:
actions/withcomments.php
--- content ---
<?php $this->config["hide_comments"] = 0; ?>
--- EOF ---
Just add {{withcomments}} on the page where you need comments.
Useful if you want to let user add comments on a tutorial that you inculded in a nocommented invisible wiki.

Also, bear in mind that for browsers without stylesheets (or with them disabled - eg view -> page style -> no style in Firefox), you can still see the history of a page. Depending on what it is you are trying to do, this might not be quite what you want!

Tim, Wikka will probably implement in the future a light templating system, which should actually enable Wiki Administrators to decide *what* links/elements are displayed *where* (see also: http://wikka.jsnx.com/WikkaMenus). Stay tuned...

I have done something like this for a site I run, but took a slightly different approach.

I've install the wiki engine twice on one server, once at www.server.org and then again at edit.server.org, then I wired them both to the same MySQL database. I changing the homepage configure path on edit to AdminHome and set up a page with all the admin links on it.

For www I've completely stripped down the wiki engine, by for example removing the edit handler and other stuff that is not need. I created a folder called UserSettings and put .htaccess file in there to block that page completely. On the edit box I've restriced updates to site admins listed in the configue file.

The most interest thing however, is that I replaced the header options in the config file with '{{include NavLinks}}, so that the site nav can also be edited as a wiki page.

Dave.

I also hacked out most of header.php and footer.php on the www instance and deleted most of the system pages as I don't need them for this application.

I only recently got aware that in the LicenseInfo the GnuPL says in the terms and contidions for copying and changing etc. that a respective note with certain information has to be added to the changed files. Maybe it could be not unimportant to mention that whenever modifications are suggested in the text here and on other pages, because I somehow doubt that many of the less frequent users are aware of it.

Only if you plan on redistributing the software. These provisions do not apply to end-users who modify files and do not publicly redistribute them.

It occurs to me that this would be a cool option in the installation process. Maybe a checkbox for "Configure Invisible Wiki" along with a short explanation of what an invisible wiki is.

Brian,

regarding licensing: it's true that we should add in the WelcomeRegisteredUser page a note saying that -- unless otherwise specified by the contributor -- all the code contributed on this website is copyright of the submitter and distributed under GPL.

regarding configuring invisible wiki, I think we should keep the install wizard as simple as possible. I've already written code (to be committed to trunk) that offers the wiki admin the possibility of preselecting default ACL styles from the installer. An 'invisible wiki' is more a template than a simple matter of configuration settings, the way I understand it.

Hmmm,j Brian I didn't realize that you were suggesting actual changes to the source. I'm not sure I'd like these changes to be hosted on this page: the InvisibleWiki page is presented as a modification that requires no code change. If you want to suggest a related hack, maybe it's good to open a stand-alone page.

I was just providing a utility, not a source code change. No problems; I'd be glad to move it to another page.