WackoWiki

Not much to it (as long as it works, ahem).

1.1. Example

If your website, say, https://www.mysite.com, is mapped to the directory /home/jdoe/www/, and you place the Wacko distribution files into /home/jdoe/www/wacko/, you should go to https://www.mysite.com/wacko/.

Note that Wacko distributions normally unpack into directories that include the version in their name; you'll probably want to rename those to just “wakka” — or, if you're on a unixoid system, set up a symbolic link.

If you are upgrading or installing over a previously installed wacko wiki:

• you'll probably want to make wakka.config.php (not wacko.config.php...) writable by the web server, at least temporarily.

If you are installing to a clean directory

• you need to create a empty file named “wakka.config.php” in this example the file would be located here: «/home/jdoe/www/wacko/wakka.config.php”
• make “wakka.config.php” writable by the web server
• Once you run wacko wiki for the first time, it will overwrite wakka.config.php with real settings.

Wacko can export the Recent Changes list as RSS. Please make sure the xml/ subdirectory is writable, since this is where the files are stored.

IMPORTANT: for installing or upgrading Wakka/Wacko, do NOT modify any of the files contained in the setup/ subdirectory. They're used by the web-based installer/updater, but you should really just access the Wakka directory itself, and it will (or at least should) work perfectly.

(adapted slightly from Hendrik Mans original)

2. Wacko Update

1. Backup all your important files including the files in the Wacko folder and in the database as well. You never know. Need a simple Backuptool?
2. Extract the updated version of WackoWiki on to your hard disk.
3. If you want to keep your layout, you have to use a program like WinMerge to merge your *.css and other theme files with the new files in the folder wacko/themes/default.
4. (optional) You can create a file named locked in the wacko folder. This file should contain one line – this word will be the password. When Wacko finds this file, it will ask every visitor for a login/password, because of the upgrade process. The login name is “admin”, the password is the content of locked file.
5. Now, upload the complete folder to your WackoWiki place. Let it replace the old files, if necessary.
   • However: wakka.config.php MUST be re-used from the old installation if you want to upgrade. Otherwise you will get database problems.
   • And: You MUST upload new files into the same directory if you want to upgrade.
6. Navigate with your browser to the WackoWiki folder as you wanted to visit your page.
7. If the data base needs updating, the installer will start automatically. It is self explanatory.
8. Go to page and check the result! If you have any problems, you may have to adjust some *.css files.
9. (see step 4) Do not forget to remove locked file.

If you see the blank page on any step,

1. Open wakka.php and comment the line 8, «ob_start («ob_gzhandler»);", with an //.
2. Then see DB error and report it to the bugtracker along with the steps to reproduce the problem.

Any problems with the install (that you want answered in English), paste below or in comments to this page.

Installing is very straightforward overall, however there are two things to look out for:
1. general: the unzipped directory and all contained files and subdirectories have (secure but not web-readable) permissions set so that the web-based installer is not found. The fastest way to get things running, but which also makes the install less secure is to go into the folder that contains the 'wacko' directory and run 'chmod -R 755 wacko'. Alternatively, go through all the directories and adjust permissions as necessary.
2. perhaps a problem on some webhosts: the .htaccess file gave my web host's configuration trouble, i.e. it couldn't find anything within the wacko folders. deleting .htaccess solved the problem.

3. What should my .htaccess file look like in order to allow for “nice-looking” URL's? I attempted to use the same rules as I previously used (successfully) on WakkaWiki, but no luck. The way I attempted it, my .htaccess file looked like this:

RewriteEngine on
RewriteRule ^style/logo/r=(.*)/g=(.*)/b=(.*)/(.*)$ style/betapilogo.php?r=$1&g;=$2&b;=$3 [QSA,L]
RewriteRule ^style/logo/grey=(.*)/(.*)$ style/betapilogo.php?grey=$1 [QSA,L]
RewriteRule ^style/(.*)$ style/$1 [L]
RewriteRule ^style$ wakka.php?wakka= [L]
RewriteRule ^(.*)$ wakka.php?wakka=$1 [QSA,L]

Anyone see what I'm doing wrong?

3. RomanIvanov: Please, take .htaccess from Wacko distro.

3. Questions

• (From an anonymous user: This file, wakka.config.php, needs to be created!, and placed in the root of your wiki install. It took me some time to realise that it's not part of the tarball – you have to create it yourself! Wacko Guys – update your documentation to reflect this, as you've forgotten to tell users they need to make this file. I hate to think how many people have given up their Wacko installation because this bit didn't make sense!)
  • What's wrong? WackoWiki creates this file during the installation process. You don't need to create it yourself, except there is something wrong with your server permissions. Pls. give us more details to figure out what's wrong
• I too had to create an empty text file called wakka.config.php. very surprising, I searched the install directory and couldn't find the file, had to read the documentation. good apps shouldn't need documentation for something as simple as a setup :) no, this is a very nice app, i just think the programmer should create one blank text file instead of asking many users to create their own blank text files hundreds of times all over the world...
  • Could you describe your problem in more details, environment, rights on server, php-info etc. ...
• I disagree with the above. I presume the logic is to avoid an update mistakenly overwriting the original wakka.config.php settings file?

• Wacko Wiki can't create the file if you install it in the root directory of a server where you can't change the file permissions and scripts are not allowed to create files. If this is the case creating an empty file yourself and setting permissions to 777 during installation is the only way to go. — JeckPixelbrei
• Regarding xml: I didn't find a path-setting in the config-file. Is it somehow possible to set another directory for creating the RSS-Feeds? — JeckPixelbrei

3.1. How can access to all files be limited to known wacko users?

It would be great not to have to restrict but the problem is that some fool keep publishing links to porn on our wiki!!!
Thanks for a great job otherwise! Phil

The answer is in the wiki already See Access Control Lists found it myself after a little more reading

3.2. 404 Not Found – Wiki cannot be found

after installation without errors -> wrong settings for rewrite_mode

I've tried an install on localhost — no problem — then tried two on an ISP (Win) and have no success; after installation which says all was OK; when I click on the homepage — I get an error page — The page cannot be found — and .net/wacko/index.phpHomePage...??? Thanks for your help.

you set your Base URL without /wakka.php?wakka=

I was having the same problem and changed my Apache configuration so the directory declaration looks like this:

<Directory /base/dir/for/wacko/> Options FollowSymLinks AllowOverride all Order allow,deny Allow from all </Directory>

Rewrite seems to work fine now.

3.3. Strange Add Page Behaviour

On one of my sites, the Wiki can't seem to stop adding pages — after you click Maybe you want to create it? , and add text — then SAVE, it adds another page — with... Racing/Argentina/editadd1?v=1ekf after the entry — it also forgets the entries it has already made. I'm confused because my other sites work very well. Also, it wont allow you to logout....or register?

Solution: in config file do: rewrite_mode => 0

3.4. Email problem

i do not have an smtp server running on my website, and no mail is being sent. how can i change the used smtp server? and do you know of any open smtp servers which i could use?
I have the same problem, where do I define what server to send mail through for watchlists? –

mail() function

3.5. Login problem

I can't logi or logout. Noting happened whe I push logout.
Firefox 1.0.6 Konqueror Opera etc. Linux Mandriva.