This page has moved

This page can now be found on the Wikka Documentation Server.
Thanks for updating your bookmarks!

An archive of old revisions of this page is still available for reference.


Comments [Hide comments]
Comment by WvanElDeRen
2004-10-22 09:30:38
I have MSAS running on my pc. I copied all the files to www\wikka. When I use http://localhost/wikka I get a 403 error. What did I overlook?
Comment by NilsLindenberg
2004-10-25 19:45:19
You mean with MSAS?
Comment by
2004-11-11 10:58:43
I'm having troubles with the installer. Calls to array_merge are falling over and blanking the $config array. Why exactly is it trying to merge an array from the config script when it doesn't exist?
Obviously the wiki must install fine for others, so why this problem. My php install seems to be fine...

Comment by
2004-11-11 11:27:47
To follow up, the problem I was having was solved by the following change in wikka.php, line 899:

if (file_exists("wakka.config.php"))
rename("wakka.config.php", "wikka.config.php");
} else {
$wakkaConfig = array();
Comment by NilsLindenberg
2004-11-11 12:40:06
Which version of php do you use?
Comment by ScumBle
2004-11-11 22:42:57
php 5.0.2 on my local machine. The actual error I got was the following:

"Warning: array_merge() [function.array-merge]: Argument #2 is not an array in E:\apachefriends\xampp\htdocs\wikka_test\wikka.php on line 910"
Comment by NilsLindenberg
2004-11-12 11:52:46
That is the problem. The people who don't have a problem to install, run php 4.x
Looks like you are the test person for php5 :-). Btw, welcome on this webpage.
Comment by JavaWoman
2004-11-12 16:20:41
I'm not sure this is a PHP5 issue; a warning like this would be caused when the configuration file was not found (and hence $wakkaConfig isn't initialized - that should be solved!) - and that in its turn could be the result of the installation process not being able to create the configuration file (no write access to the directory?).

In other words, more likely an "environmental" problem than a PHP5 problem - but the (installation) code should pobably be fixed to handle such situations better.
Comment by
2004-11-13 16:52:30
In Wikka.php the config file is loaded, before a install process is started.
Well, I would say that it is an PHP5 problem:

(arry_merge [(])
In all PHP 4 versions the above function deals gracefully with paramaters which are NOT arrays(). So if you pass a string or number it will be automagically converted to an one-element array as described in the manual section about Types and "implicit typecasting". So if you ever happen to put an empty/unset variable (NULL value) as parameter, array_merge() will still collapse the other arrays as intended.
PHP4 does not carry if both strings are arrays, but php5 seem to do ("From PHP5beta2 on this behaviour changed, and PHP will correctly issue a E_WARNING message, whenever one of the paramters isn't an array.")

So actually wikka.php hat to handle missing config files before, but PHP5 is more strict and does not tolerate this behavior anymore.
Comment by JavaWoman
2004-11-14 06:27:25
Ah, good catch!

One of the things about PHP I *don't* like is this automatic type conversion (would be nice if I could just turn it off!); the PHP documentation is extremely sloppy about that, too (for instance claiming a function returns a boolean when in fact it returns 0 or 1). In my experience counting on this behavior this will _always_ lead to bugs down the road, as nicely illustrated here. So I code pretty much as if it doesn't exist.

Anyway, this should be reported as a BUG on the WikkaBugs page; the fix should be easy enough.
Comment by
2004-12-01 02:33:10
As a temporary fix, I added this prior to the line causing the trouble

$wakkaConfig = array();
Comment by
2004-12-29 18:09:56
with Debian GNU/Linux 3.0 (woody) are installed PHP 4.1.2 and this version don't support "mysql_real_escape_string" function.
temporary fix on wikka.php head:

if ( ! function_exists("mysql_real_escape_string") ) {

function mysql_real_escape_string($string){
return mysql_escape_string($string);

IMPORTANT: installer user TOO MUCH "@" before all mysql call...
Comment by
2005-01-21 02:56:17
The install instructions are missing some important details.

First, after you unzip the tar file, you should chown, and chgrp the entire Wikka directory to your web user (www-data in debian, apache on redhat).

Next how to make mysql database.

>>mysql -l root -p
Enter Password>XXX

create database wikka;
GRANT ALL PRIVILEGES ON wiklka.* TO wikka@localhost IDENTIFIED BY 'password';
flush priviliges;

Will create a new database called wikka, and a local only user called wikka with password 'password';

Next the php that is shipped with some linux's (such as debian sarge) may not have mysql enabled. You will need to enable mysql support by adding in the php.ini file.

Also, the extension may need to be installed as a seperate package. On debain the package is called php4_mysql.

Errors are not logged by default in php default debain install, so you should also enable syslog logging in the php.ini.

With these added steps I was able to get successfull install on debain sarge.

Lastly, I would suggest that the installer script first print what it is about to do, then do another print whan the operation works. The database call was failing, and it took me a bit of time to figure out what the problem way because of the lack of logging and the script only printing out status after a call has worked.
Comment by NilsLindenberg
2005-01-21 14:20:42
@ip: yes, the installer could do better. Note the comment before yours :)

Would you like to write a Howto for the installation on debian (or on linux, don't know how much that differs)? This would only mean bringing your notes already posted here into a little bit more layout and perhaps add something like how you accesed the mysql-prompt. I tried to complete the instructions above a little bit, but some of your things seem to be to specific for the generell page.
Comment by
2005-01-25 13:29:27
I had some trouble getting access to the pages after I uploaded them to the webserver. I was constantly getting a 404.

However, deleting the ".htaccess"-file solved my problem. Rewrite-rules aren't possible with my host anyway.
Comment by
2005-01-26 02:54:05
There are a number of .htaccess files in the whole package of Wikka. What to do if my web host does not allow me to use the .htaccess file? What will be happening if I delete all of the .htaccess files?
Comment by JsnX
2005-01-26 04:00:29
Wikka can work fine without the .htaccess files. They are primarily used for people who want the functionality of mod_rewrite.

Go ahead and delete them.

Just make sure to edit the wikka.config.php file to turn of rewrite_mode:

"base_url" => "",
"rewrite_mode" => "0",
Comment by KarmaTester
2005-01-26 06:52:07
Devs: Congrats on the new release!

Since I installed wikka in a subdirectory under the domain root I needed to add the following to the .htaccess file just under "RewriteEngine on":

RewriteBase /subdirectory/

Devs, how about writing the .htaccess rules at the same time you write out the wikka.config.php file since you automatically pickup the wiki base location at that point?

Comment by JavaWoman
2005-01-27 06:04:45
Thanks for the suggestion. I've copied it to the SuggestionBox to give it a better home. :)
Comment by ChristopherAllen
2005-02-04 19:58:15
This page says the the version will have a solution to the PHP5 problem, but looking at the [[ What new in Wikka]] and [[WikkaReleaseNotes Release Notes]] doesn't appear to mention it.
Comment by NilsLindenberg
2005-02-04 20:10:51
Hi Christopher! The bug mentioned above is solved. But yes, it isn't mentioned very clearly in the release-notes ("Added scumble's suggestion for fixing array_merge problem as detailed on WikkaBugsResolved"). I'll look after that tomorrow.
We are still at updating the documentation and things like that. Thank you for the hint :)
Comment by DarTar
2005-02-05 00:11:03
Agreed: PHP5 support in Wikka is actually an important enhancement that should be clearly announced in WikkaReleaseNotes, in WhatsNew and in WikkaFeatures. This page should be updated accordingly.
Comment by RyanKnoll
2005-02-05 08:09:24
Should be fixed: On the install page, there should be a trailing "/" at the end of the base URL. Without it, css and other stuff won't work. It happened on two separate shared hosts running red hat/cpanel setup.
Comment by JavaWoman
2005-02-07 14:32:18
@DarTar: we *don't* have PHP5 support - all we did was fix a bug that only _showed up_ when installing with PHP 5; it was a bug already (and we have many more like this to squash).

Fixing a bug is not an "important enhancement". Once we have real PHP5 support, that will be. :)
Comment by JavaWoman
2005-02-08 17:44:04
@RyanKnoll: From what path did you install? I just did a (re)install on my development machine and it picked up the path just fine, trailing slash and all. So if this doesn't *always* happen we'd like some info on just when it does (and when not).

Anyway, this actually belongs on the WikkaBugs page!
Comment by RubenVerlinden
2005-02-15 10:08:33
I am trying to install Wikka, but after accessing wikka.php, filling in the forms and pressing continue I always get the following message :

Warning: preg_match: internal pcre_fullinfo() error -3 in /var/www/Wikka/wikka.php on line 1061

Warning: preg_match: internal pcre_fullinfo() error -3 in /var/www/Wikka/wikka.php on line 1062
Testing Configuration

- No wikka.config.php file is written in my Wikka directory, which is world writable.
- The database (didn't create any tables manually) is accessible by Wikka.
- I didn't do any extra configuration for apache2

Can anybody give me any hints where to start looking?
Comment by NilsLindenberg
2005-02-17 12:24:01
Hi Ruben!
Could you please give more infos about your php-version? did you look at WikkaTroubleshooting?
Comment by
2005-02-18 11:21:27
Software versions :
apache 1.3.33 (also tried apache 2 2.0.53)
mysql 4.0.23
php 4.3.10

I hope this can help.
I did look for the different problem descriptions and solutions proposed, but none matched.
Comment by
2005-02-20 00:12:46
twice I tried installing, New database both times. config file and database are written to and fine. url to wikka=FILE NOT FOUND!!!!
DAMN The time that is wasted for the lack of complete instructions. I am a webdeveloper, install Movable Type, TWiki, Drupal, wordpress and a dozen other ones no problem. Followed install to the letter. what a waste of time.
Searched this whole site also...nothing
Comment by JavaWoman
2005-02-20 10:09:44
Can you give some more details so we can actually try to help?
Such as - what OS and webserver are you using, what path did you install to, are you using mod_rewrite... ?
You may also want to have a look at WikkaWorkarounds for specific platform-related problems and solutions.
Comment by JavaWoman
2005-02-20 10:17:10
If you do a Google search for "Warning: preg_match: internal pcre_fullinfo() error -3" (with the quotes!) you'll find numerous other sites that have/had this problem - as well as suggestions of the probable cause. Not a bug in Wikka, but a problem with PHP itself which may need to be recompiled with the "proper" (newer?) PCRE library - at least that's what it looks like to me. (It seems to have turned up suddenly with the upgrade to PHP 4.3.10 on a lot of sites.)

After checking the Google results ... do a recompile or bug your hoster :)
Comment by RubenVerlinden
2005-02-20 22:30:25
With apache 1.3.33, mysql 4.0.23 & php 4.3.10 I din't get the prematch error anymore. But no config file is written to the world wrtiteable Wikka directory.

The only thing that comes on the screen after committing the online config is : `Testing configuration'
Comment by JavaWoman
2005-02-21 07:37:55
Hmmm - after "Testing configuration" you should at least get "Testing MySQL connection settings..." (there seems to be a minor bug here in the install procedure?).
Still, if you don't get past that point it seems to indicate Wikka cannot connect to your MySQL database - because trying to connect to the database is the first thing the installer does after "Testing configuration".

First, check that that the MySQL server is running and that PHP can indeed connect to MySQL (for instance with phpMyAdmin); next, make sure that the database connection parameters (database name, username and password) match with what you have set up for MySQL - see point 4 in the "Longer description" on this page.
Comment by RubenVerlinden
2005-02-21 10:01:54
I didn't have the php module to access MySQL installed. When installing phpMyAdmin it also installed this module (all hail to apt-get).
So it seems to be working fine now. Thx, for the help.
Comment by RubenVerlinden
2005-02-21 10:06:48
One little commment : the url for the wikka wiki proposed should by default include an ending / . Otherwise the links don't work.
Comment by JavaWoman
2005-02-21 18:26:35
Don't be ashamed. We should be looking into why the installer "hangs" without further feedback when it cannot connect to the database. If it had given you an appropriate error message you wouldn't have had the problem...
We'll look into that - and the ending slash (which has been reported before but I didn't encounter that problem); did you install in a subdirectory?
Comment by JavaWoman
2005-02-21 18:43:56
Added an item to WikkaBugs so we don't forget to fix these installer problems. Thanks for your patience, Ruben!
Comment by
2005-04-27 13:31:49
Hello, Installation first step I failed:
"404 Not Found"
"The requested URL /home/.../htdocs/test/Wikka/wikka.php was not found on this server."

I am trying to solve this by directly typing it seems to carry on. but I don't if there is anything bad?
Comment by JavaWoman
2005-04-27 17:49:24 : gives me a 404 - In fact I cannot find any other file that should be accessible by the browser, such as the stylesheets, either. How did you install the software on the server? Are you sure the base path should be ?
Comment by MattSelznick
2005-04-28 02:31:20
Hi -- just installed, apparently successfully, but when I try to go to the normal home page of my site for the first time, I get this:

Fatal error: session_start(): Failed to initialize storage module: user (path: /tmp) in /home/mwsmedi/public_html/diywiki/wikka.php on line 1150

I'm not very saavy with PHP and all that, but I suspect it may actually be a permissions issues. Any ideas?
Comment by
2005-04-28 09:42:58
Hi JavaWoman,
Sorry for that. it is just a mock name that actual address is:

Which is our project on it seems alringht now, even it failed get url by "index.php".

Could you please help me to check that, Thank you very much.
Comment by JavaWoman
2005-04-28 14:08:03 :
- This does not work:
(resulting in a 404 error for wikka.php)
- But this works:
(resulting in - so wikka.php does actually exist)
- But then this does not work:
(resulting in a 404 error for wikka.php again)

I suspect there is an error with your mod-rewrite configuration. It looks as if the server is *trying* to rewrite but coming up with an incorrect result. Please have a look at and see if that helps. Also check (linked to from there).

Please report back! I'm just now working on the pages about mod_rewrite hoping to make things somewhat clearer...
Comment by JavaWoman
2005-04-28 14:42:03
Yes, this is indeed a permissions issue. Wikka needs to store sessions; the default is to store them in files in the directory /tmp (this can be configured in php.ini). This implies that this directory *must* exist and *must* have write access for Wikka (PHP). You could also use php.ini to point session.save_path to a different directory, as long as it exists and can be written to (if you have permission to edit php.ini).

(See also and (linked to from there) - although your error message is similar but not exactly the same.)

Please let us know if this helps.
Comment by FaiF
2005-04-28 15:18:48
Thank you JavaWoman,

I missed the point on

and I modified .htaccess and add:
"RewriteBase /test/Wikka"

Now it seems work fine, Please help me check:

I ingnored it because it says "Future versions of Wikka (> may handle the workaround outlined below automatically." I presume it works on

Thank you for your help.
Comment by JavaWoman
2005-04-28 16:45:52
I looked at your site again - it does seem to work fine now!

No the workaround (adding RewriteBase) is not included in so for that version (and lower) it has to be added manually if Wikka is in a subdirectory. I hope we can do that automatically as of the next version (probably, intended as a bug fix and problem-solving release).
Comment by
2005-06-29 19:04:57
I tried to install this on our Windows machine where we're running IIS (sigh) and PHP.

Everything installed fine but when I run, I'm getting the error "Redirection limit exceeded". Looking more closely at the pages, it seems that index.php redirects to wikka.php which, at some point, redirects right back to index.php

Any ideas?
Comment by JavaWoman
2005-07-04 18:41:27

Indeed index.php (meta-)redirects to wikka.php; the intention here is that you could go to just the directory, the server will retrieve index.php, which will tell the browser to pull up wikka.php instead - so you end up at the home page (once you've gone through the installation procedure).

At least, the latter step *should* happen. It's not clear from your comment whether you've run the installation procedure yet, or don't get farther than trying to do so. Did you do the setup (creating databases and defining configuration) yet or not?
If you did, please check what you have in wikka.config.php for base_url (should point to /your/path/wikka.php?wakka=) and rewrite_mode (should be 0 for IIS). See also the ModRewrite page.

Please report back, or join us in the #wikka channel on (see TheLounge)
Comment by
2006-02-06 18:52:54
The following solution will allow Wikka to work for a site that can be reached by multiple domain names (for example, a server that has one address when accessed via an intranet and a different address when accessed from the Internet):

Edit wikka.php. After line 1113 (which reads $wakkaConfig = array_merge($wakkaDefaultConfig, $wakkaConfig);) add the following line:

$wakkaConfig[base_url] = "http://".$_SERVER["SERVER_NAME"].($_SERVER["SERVER_PORT"] != 80 ? ":".$_SERVER["SERVER_PORT"] : "").$wakkaConfig[base_url];

Then, edit wikka.config.php and set base_url to contain just the path of your Wikki (i.e. "/wikka/") instead of the full URL.

I may be reinventing the whell here. It would be good if Wikka actually had a config option to autodetect the domain or require it in base_url.

Comment by DarTar
2006-02-07 03:24:10
Hi Vincent and thanks for suggesting this idea. As a matter of fact the current solution for determining the base_url during the installation as well as the way it is configured is not optimal. I see Wacko adopts something similar to what you are suggesting, so maybe we should switch to a dynamically generated base_url instead of hardcoding it in the config file.
Comment by KraaK
2006-03-30 09:58:46
hello, i installed succesfully wikka in a subdirectory (for testing etc), lets' say
now, i'd like to move the whole wiki up one directory, to made it available directly whe pointing at
how this should be done correctly? can i simply copy the contents of the /wikka directory?
thanks, kraak
Comment by DarTar
2006-04-01 07:25:58
You should copy/move the folder and change the base_url value in wikka.config.php
Comment by
2006-04-23 16:39:23
OK - I'm doing something stupid. Install ran fine but going to the base url - - gives me "The requested URL /wikkaHomePage was not found on this server."
What have I missed?
Thanks - Steve
Comment by WazoO
2006-04-23 17:46:18
Possibly a mod_rewrite issue / .htaccess ..???
Fetching ...
GET / HTTP/1.1
HTTP/1.1 403 Forbidden
Additionally, a 404 Not Found error was encountered
Fetching ...
GET /wikka/ HTTP/1.1
HTTP/1.1 302
Comment by WazoO
2006-04-23 17:47:05
And the successes ... split out to defeat the anti-spamming flag ....
Fetching ...
GET /wikka/wikkaHomePage HTTP/1.1
HTTP/1.1 200 OK
<base href="" />
Fetching ...
GET /wikka/wikka.php/ HTTP/1.1
HTTP/1.1 200 OK
<base href="" />
Comment by DarTar
2006-04-23 18:36:36
It looks like you need to add a trailing slash to the base_url in your config file (wikka.config.php). If you are still seeing no stylesheet or images, take a look at: -
Comment by
2006-04-24 15:14:57
Thanks - the trailing slash did it!
Comment by
2006-04-25 13:16:39
Another problem....
Got the wiki working fine at mysite/wikka. I want a second wiki so I upload a new set of the install files to mysite/da-wiki1. I create a new d/b for the new site.
When I point my browser to mysite/da-wiki1, instead of getting the setup screens, it just runs the wiki at mysite/wikka!!
What gives???
NB I did upload a fresh set of files, not copy across the working installation!
Comment by WazoO
2006-04-25 18:53:13
04/25/06 17:48:15 Browsing
Fetching ...
GET /da-wiki1/wikka.php HTTP/1.1
Connection: close
HTTP/1.1 200 OK
Date: Tue, 25 Apr 2006 22:48:17 GMT
Server: Apache
X-Powered-By: PHP/4.3.11
<title>Wikka Installation</title>
<style type="text/css">
looks fine from here .....
I made no changes ....
Comment by
2006-04-26 04:40:14
Interesting. It worked fine with, but not with
Turned out it had created a .htaccess file with a RewriteBase of 'wikka' which was the folder of the OTHER installation!
Comment by
2006-05-24 14:56:11
When I install wikkawiki it asks if I would like to change the password for a previous username I had with a previous install. This happens even though I start out fresh (i.e. deleted all previous files and database tables). Any ideas?
Comment by DarTar
2006-05-24 15:30:43
Try to clear your cookies from your browser.
Comment by
2006-05-24 16:23:31
Thanks, clearing the cookies worked. But now when I attempt to logout, I get this error:

WikiLab : UserSettings?action=logout
HomePage :: Categories :: PageIndex :: RecentChanges :: RecentlyCommented :: Change settings/Logout :: You are WikiAdmin

This page doesn't exist yet. Maybe you want to create it?

Any ideas?
Thanks again!
Comment by DarTar
2006-05-25 03:18:37
This looks like a wrong configuration of your base_url / rewrite_mode settings, take a look at:
Comment by LarryR
2006-08-07 16:16:04
I have been trying to get Wikka installed on an XP SP2 machine for a couple of days now. I have been following the instructions on the page Wikka : NickDamoulakis. I believe the problems I am having are with PHP. I first tried to follow instructions on that page ABSOLUTELY word for word. I even hunted down the exact versions that are reffered to on that page. When trying to run after installing to these instructions I received 2 errors whenever I restarted IIS or rebooted the machine. They are PHP Startup: unable to find dll PHP_mbstring.dll and PHP_MySQL.dll. These are 2 dlls that you're told to enable in php.ini. Also, when I ran the web configuration tool after deleting the '@' in all @MySQL statements in I have been trying to get Wikka installed on an XP SP2 machine for a couple of days now. I have been following the instructions on the page Wikka : NickDamoulakis. I believe the problems I am having are with PHP. I first tried to follow instructions on that page ABSOLUTELY word for word. I even hunted down the exact versions that are reffered to on that page. When trying to run after installing to these instructions I received 2 errors whenever I restarted IIS or rebooted the machine. They are PHP Startup: unable to find dll PHP_mbstring.dll and PHP_MySQL.dll. These are 2 dlls that you're told to enable in php.ini. Also, when I ran the web configuration tool after deleting the '@' in all @MySQL statements in phpinstall.iniI have been trying to get Wikka installed on an XP SP2 machine for a couple of days now. I have been following the instructions on the page Wikka : NickDamoulakis. I believe the problems I am having are with PHP. I first tried to follow instructions on that page ABSOLUTELY word for word. I even hunted down the exact versions that are reffered to on that page. When trying to run after installing to these instructions I received 2 errors whenever I restarted IIS or rebooted the machine. They are PHP Startup: unable to find dll PHP_mbstring.dll and PHP_MySQL.dll. These are 2 dlls that you're told to enable in php.ini. Also, when I ran the web configuration tool after deleting the '@' in all @MySQL statements in I have been trying to get Wikka installed on an XP SP2 machine for a couple of days now. I have been following the instructions on the page Wikka : NickDamoulakis. I believe the problems I am having are with PHP. I first tried to follow instructions on that page ABSOLUTELY word for word. I even hunted down the exact versions that are reffered to on that page. When trying to run after installing to these instructions I received 2 errors whenever I restarted IIS or rebooted the machine. They are PHP Startup: unable to find dll PHP_mbstring.dll and PHP_MySQL.dll. These are 2 dlls that you're told to enable in php.ini. Also, when I ran the web configuration tool after deleting the '@' in all @MySQL statements in ./setup/install.php I get an error on line 16 indicating I can't connect to the database. I have tried re-installing EVERYTHING several times and even using different versions of PHP and MySQL. I get different errors at different times (too many to remember). I chatted briefly with JavaWoman a few times and thought I was on the right track but end up with the same errors (dll not found). Unfortunatly my employer blocks ports so that I cannot chat from work (in the U.S.) and JavaWoman is on Amsterdam time. The version of PHP specified on Nick's page does not contain an installer for windows, is that the problem. Can anybody help?
Comment by LarryR
2006-08-07 17:08:53
Well, I don't think that was it. One thing I just noticed; when I look at my PHP config I do not see a section called MySQL. Help?
Comment by LarryR
2006-08-07 17:27:59
OK, I found the problem in the PHP 5 docs. In PHP5 libmysql.dll MUST be in the Windows dir.
Comment by LarryR
2006-08-08 11:26:21
I just finished installing Wikka successfully. Now the problem is that I can't seem to login or register. The HomePage that's displayed has my Admin name in the Owner field but I can't even login as admin!!
Comment by JavaWoman
2006-08-08 13:02:41
Thanks for all the info - one day we should try to pull all this IIS+MySQL+PHP together; there's bits and pieces of info all over the place but nothing seems to be _quite_ *complete*.

As to logging in as Admin - you would have chosen an admin WikiName and a password when you set up Wikka. Did you write those down? What exactly is the problem when you try to log in? If you have forgotten the password you defined during installation you could try the "password forgotten" trick, have a temp password sent by email to you, and use that to log in - and immediately change the password after that.

If that isn't the problem, please elaborate on what happens when you try to log in.

And what happens when you try to register (as another user)?
Comment by LarryR
2006-08-08 15:29:30
Sorry JavaWoman - had some IT issues that have been resolved. BTW LarryR = ljre (irc). Thanks for all your help.
Comment by BrianKoontz
2006-08-08 16:39:49

Check your wikka.config.php file. It appears the installer is incorrectly populating the 'base_url' field. It should look like this (if there's something after "wakka=", delete it!):

'base_url' => '',
Comment by LarryR
2006-08-10 12:07:43
Here's the line as it stands in wikka.config.php:

'base_url' => 'http://localhost/wikka/wikka.php?wakka=',

The page I am getting when I go to my Wikka site on the system it's running on is "Thanks for Installing Wikkawiki...". Is that correct? The problem now is in order to get to the site from a different computer I need to delete 'localhost' and insert the IP of the machine it is running on into the url in my browser. This brings up the same page. However, images are not being displayed. When I look at the properties for say, the Wikka logo or any link for that matter I see a url like this:
http://localhost/wikka/wikka.php?wakka=UserSettings (clicked on Logon)

I'm sure this is a basic Web admin configuration issue and I am sorry for posting it here, but I really need to get this up and running as soon as I can. I'd appreciate any help you could offer - thanks
Comment by BrianKoontz
2006-08-10 12:57:12
If you are changing the 'base_url' parameter in wikka.config.php, then all of your links should reference the new changes. For instance, if you replace 'localhost' with '', all of your links will reference

I don't see how a web admin issue would affect this; base_url is set well after any configuration changes to the web server are made effective.
Comment by DarTar
2006-08-10 13:11:30
when changing settings, make sure your base_url and rewrite_mode match (see Brian is right in pointing out that the base_url should not affect the way links are built. Also this may help: (check that the content of the .htaccess for the images folder is correct or just try removing it).
Comment by LarryR
2006-08-10 13:37:03
Hi - I've already tried both of these suggestions but will have another look at them.
Comment by AcidPhil
2006-11-20 17:32:44
In case you're interested in hearing super-newbie type problems:
1. When installing, I had no clue that the name for the homepage should be rather concise; so I made a title packed with keywords. Yuck! And the site title lacked esthetics too. But I find no way to back up and revise - rather afraid to rename or delete the homepage. Quandary.
2. When asked for Admin's name, I complied literally - not really expecting my real name to be displayed on every page. Here too - don't know how to back up.

My question - can I revise these fields and if so how?

I'm happy to work with any manual being written to add comments and warnings for The Compleat Idiot and first time user.
Comment by MasinAlDujaili
2006-11-21 03:25:38
AcidPhil, have a look at wikka.config.php in your Wikka root. There you'll find wakka_name. As for your other matter: All I can suggest is to change the owner via 'Edit ACLs' at the bottom of each page if your problem is that you are the owner of all those pages. You'd have to create another account with admin privileges, of course. In wikka.config.php you'll find a line where admin_users are defined. You can put multiple users in there seperated by commas. Another solution would be to use something like phpMyAdmin and change the owner fields in the page table. Nonetheless, the new user should exist.
Comment by WillyPs
2007-02-03 16:29:19
Howdy, I just installed my first wikki. The installation went without a hitch, Thanks for all the hard work you all have put into this... but I do have one question:
How do I write protect the config file?

Edit: I figured out how to remove write permission from a file, fyi, I connected via ftp and rightclicked on 'writeconfig.php' and removed a check.
Comment by DonnaM
2007-04-03 18:36:34
I do not have wikka.config.php in my root for Wikka, does this happen after you install it? I am not able to install, it says it fails every time it tries to access MYSQL --- I have the database, the username/password, all to no avail.
Comment by BrianKoontz
2007-04-03 19:03:57
Donna, is this a hosted MySQL server, or is it on a machine that you own? The reason I ask is that oftentimes, hosted MySQL servers require an explicit hostname. Are you able to connect to the server from the command line? Something like

mysql -h -u username -p

should work. If you can connect like this, then just transfer those values to the install page. Let us know how you fare!
Comment by UnDisclosed
2007-05-17 01:31:43
The .htaccess file in the root folder of the currnet release (1163) is not
valid for Apache web servers.
That is to say: The formatting of the stanzas are invalid.
is not correct and will cause your (httpd) to complain with something to the
following: .htaccess: Invalid command 'SetEnvIfNoCase', perhaps mis-spelled...
Meaning that the syntax is incorrect, that it is improperly located, that it
was not declared correctly, or was misplaced. The best solution to this would
be to inform the Author(s) that they need to study the Apache server closer --
more specifically; mod_env.
So to ensure that you receive REFERRER SPAM and get SEO/SearchEngine friendly
URI's you will need to comment out (add a hash mark # at the beginning of each
line) all the lines in the htaccess file __except__ those pertaining to mod_rewrite.
Your pages will then work as you would ultimately wish them to, and your server
won't give you anymore grief.
Comment by DarTar
2007-05-17 04:53:59
Hi, UnDisclosed - thanks for posting a ticket in our tracker:
Comment by UnDisclosed
2007-05-17 07:39:47
You are /quite/ welcome. :)
I wasn't able to get the editor to provide a toolbar /until/ I renamed
.htacces to _htaccess.
Why? Because Apache doesn't accept the statement in it:
<IfModule mod_rewrite.c>
RewriteEngine off
While this stanza is /quite/ acceptable in the httpd.conf file within the
<Directory stanza.
It (Apache) complained about it being in the .htaccess file. Seems
like it should have worked. But I had to move it into the conf file. I'll look into
it further and report back if I find the cause for it not working in the .htconf file.
Note: mod_rewrite is enabled in the wikkiroot and provides clean URI's.
This might be of additional help should others be having difficulties seeing a
toolbar in their editor. :)

On that note. Any experiences with swapping out the current editor for
one of the "fancier" versions? Much involved?

Comment by DarTar
2007-05-17 08:48:37
Here's a preview of the new edit toolbar that will be included in the next release:
Comment by UnDisclosed
2007-05-17 18:14:57
Greetings, and thank you for taking the time to reply.
The new version is quite a bit nicer. Thanks for the
pointer! I see there's still no "color" option(s) provided.
That seems like all that's missing. I would otherwise
consider the new version /quite/ complete.

Thank you again for the response.
Comment by SbWoodside
2007-05-19 15:17:43
It seems to me somewhat unsafe to leave wikka.config.php as 644. If possible, the installer should chown the file to www-data or whatever user the server is running under and set it to 600. After all, this file contains passwords in plain text!!!
Comment by BrianKoontz
2007-05-20 02:28:34
SbWoodside: Where do you draw the line? I mean, if you *really* wanted to lock things down, you'd be running in a chroot jail. And wouldn't that be fun to explain to everyone!

I think the author might have been trying to avoid having to go into a lot of detail about file and directory permissions and ownership (might as well just start a Unix tutorial page at that point).

Why don't you reword it the way you think it should be? I'm sure it will be a security improvement over the current wording...(I also find it strange that changing dir perms is mentioned, but no example is given of that. IMO, that would be the more logical choice, as the wikka.config.php file would then be created with the correct user/group owners.)
Comment by UliLeh
2007-10-08 20:31:53
I try to install WikkaWiki, but there is always a 500 server error, except I delet the .htaccess file, everything else results in a 500...
During the installation there is only text in the uper-left corner, no image und later, after the installation there is no skin activ and no WikiEdit and so on. Only "absoult minimum"...
I don't know what's wrong, I even don't know, if that has anything to do with the .htaccess.
This is my first try to install a wiki.
Could anybody please help me?
Comment by BrianKoontz
2007-10-10 07:31:13
500 errors are somewhat generic, so it's hard to say. Are your file permissions set so that they're accessible by the web server? What platform are you running on? You should at least see the first installation page when you point your browser to your install directory. I'd check permissions first...

If you're still stuck, check out the troubleshooting page (

Valid XHTML :: Valid CSS: :: Powered by WikkaWiki