Working on my email toolkit, I notice a discrepancy here between admin_users and admin_email:
- at setup, you define a single admin user and hir email address, and these go both into the database and the configuration file;
- a WikiMaster or WikiAdmin can (at some time(s) after installation) add more WikiNames of admins to admin_users.

This raises some questions:

What should happen when the system (or a user via the system) needs to send an email to the "admin" and there are multiple names in admin-users:
* send to a single email address (ignoring names)?
* send to all admins using email addresses from the database (using names as keys)?

What if all admins need to get an email:
* should we allow multiple email addresses in admin_email?
* should we then check there is an equal number of email addresses in admin_email as there are names in admin_users (how, when, what if they don't match)?
* or should we do away with the admin_email field in the configuration and instead pull the necessary email addresses from the database using the names in admin_users?

The latter (get all email addresses from the database) seems the most sensible approach to me so I tend to just ignore admin_email and send whatever to all admins using the database data, but I'm open to counter arguments.

I need a dummy wikka.config.php file to finish my installation. The installation routine doesn't dump the input in the file. Who can help and post the main structure of the wikka.config.php here? thanks,
pedro

@pD9F6FAF5.dip.t-dialin.net:
Try this (untested)
1. At the end of wikka.php is an array called $wakkaDefaultConfig which has the defaults; copy this to a file called wikka.config.php and rename the array $wakkaConfig
2. Update all the database access settings to those that apply in your setup
3. Fill in your WikiName and email address in admin_users and admin_email
4. Add an entry called wakka_version with content 1.1.5.3 (assuming that's what you installed)
Make the file read-only. Now test. You may have to tweak a few more things but this should cover the basics, I think.

thanks JavaWoman for helping! I've gone your way and changed the array items to variables as
$mysql_host = "...strato.de";
$mysql_database = "DB...";
$mysql_user = "...";
$table_prefix = "wikka_";
but wikka/index.php is still answering: "Since there is no existing Wikka configuration..." hmm. Guess my PHP expertise is not good enough. So I've to learn harder. cheers, PedroMiramis

@PedroMiramis,
No, it still *must* be an array - only rename as I've indicated; then extend with the extra items you need.
Then array elements look like this:
"mysql_host" => "...strato.de",
NOTE:
- no $ at the start, just a name (single or double quotes, your choice)
- => (not = )
- comma at the end (not a semicolon)
Wikka needs that array, not individual variables!

Pedro, my server uses SME Server (a variant of Redhat 7.3). My system does this on new installs too...such that even when the wikka.config.php file is set up properly it still gives the message "Since there is no existing Wikka configuration..." On my system it seems to have something to do with SME server not using .htaccess in the way implemented in most other linux servers (supposedly, I've read, to increase security). I had to do *substantial* fooling around (and use information at the old wakkawiki site that is no longer available) to figure out how to get .htaccess to work with my server software. I'm pretty sure how I ended up changing it results in poorer security (so I don't want to post the details here), but the first thing you might try to do is getting rid of .htaccess & see if that helps (in my case it leads, as I recall, to an "unformatted" version of the wiki showing up). You should know I'm not a programmer so I have no clue WHY my changes actually work or WHAT they do differently, I just know they allow me to run the wiki. If you email me at gmbowen _at_ yahoo _dot_ com I don't mind sending you the details of what I changed. Hope that helps some. Wikka is a great piece of software (I compared a whole pile of wiki's to decide on this one) but that aspect of configuring it was extremely frustrating to me. [I've just read JavaWoman's note....I'm unclear now whether you've set it up as an array, or whether in doing it as a separate file structured properly you still have the error.....her & my response addresses each possibility I guess.] cheers, MikeB

I wanted to change the name of the wiki. When I tried to upload an edited config file, my ftp software gave me a Permission Denied (Error -160) error. I've never received anything like this. Can someone please tell me what is Error -160 and how do I resolve this so that I can edit the config file. Thanks!

If you followed the guidelines on installing your Wikka, you would have changed the permissions of the configuration file to read-only. An FTP client can then download (read) the file but not upload it.
Thus, you need to change the permissions of the configuration file on the server first to allow writing (you can do this with most FTP programs), then upload your changed file, and then set permissions back to read-only.

Thanks for the reply Javawoman. Sorry I didn't mention that I did try to change the permissions already. And I got something called an Error -142 when I tried to change the permission to 777 or to any other permission for that matter. What can I do to overcome both these errors? Thanks!

I've changed the Wikka.config file...
"default_write_acl" =>
"UserName1
UserName2",
But still any visitor can write a page. What am I doing wrong? I want only specified people to be able to write and edit pages. Thanks!

David,
The default ACLs apply only to a page for which the ACLs were not changed; if you want the new default to apply to *any* page you should remove all records from the acls DB table. (See also the suggestion about resetting ACLs on the SuggestionBox.)
Does that help or am I misunderstanding the problem?

60.48.81.21,
Frankly, I'm stumped. Generally, in Internet protocols, response codes that start with a 1 (i.e. 1xy) are informative only and do not signify an error. I've been googling for these codes in relation to FTP and come up blank.
Did you have any problems installing Wikka to begin with? Did you change the permission for the config file to read-only after installation?

Ooops. Sorry to take up airtime. We've two installations with similar names, I'd changed the wrong wiki.config.php. Everything now working as advertised! Love the cloning feature. Many thanks.

Hi 60.48.81.21, I think I had the same problem when installing Wikka. The automatic installation creates the config file, so its owner is 'apache' instead of your ftp-username. Its permissions are rx,r,r. I have not been able to chown the config file to my ftp-user. But I have been able to change its permissions by creating and uploading (and executing) the following php code to my home directory:

%%(php)
<?php
chmod("wikka/wikka.config.php", 0777);
?>
%%

I don't know if this solves your problem, or if this is the best way to handle this. But at least it worked for me (don't forget to change the permissions again after editing the file).

Great stuff Wikka b.t.w. !

Last post was added by MichielWientjes (I just registered).

Two things:
- can't find "show_spaces" in the latest release
- "allow_doublequote_html" seems to be replaced by "double_doublequote_html "=> "safe",?

Nils,
"show_spaces" may be re-implemented (I think it was actually removed from earlier code); it would enable presenting links to Wikka pages with spaces inserted in the CamelCase words to make them more readable. Which would be nice to have and simple to implement

"allow_doublequote_html" does seem to be replaced - I'm not sure which values are allowed here (there should be a way to "turn off" embedding html so that it's shown as just code); that would require some code inspection.

The history of "show spaces":
A few people requested the ability to show spaces in wiki names. Wacko had this capability, so I pulled the necessary code into Wikka. It worked. But frankly I wasn't fond of the feature, or the code, so I removed it back in version 1.1.3.1.

I changed "allow_doublequote_html" to "double_doublequote_html" to allow for more possibilities in the future. "allow_doublequote_html" only makes sense as a boolean value -- you are either allowing it or not. Calling it "double_doublequote_html" doesn't have this limitation.

The possible values are:
"safe" -- the HTML is passed through SafeHTML (default)
"raw" -- the HTML is output as is
<anything else> -- the HTML is passed through htmlspecialchars[_ent]

This was added in Wikka 1.0.5.

Jsnx,
As to "show spaces" - it's something that seems to be cropping up repeatedly; I don't see why we couldn't put it back (as an option). Don't know what the code was, but two lines would do it (not counting the 'if').

For "double_doublequote_html" - yes I figured there would be multiple (as in >2) options.
I could imagine other options:
"ignore" -- completely drop HTML, and
"strip" -- apply strip_tags().
Both would enforce wiki markup only, but the latter would preserve the content (if not the markup).

Jsnx, JavaWoman,

My first version of Wikka was 1.1.5.3 so I just realize I may have reinvent the wheel when I proposed a code here: UrlBeautify that does exactly what you are talking about: add spaces in between CamelCase words if the user selects this option in his user settings.

I am not disturbed by CamelCase words but many people are. It is easier to "sell" a wiki when this possibility is there.
I had a very good feedback when I delivered this feature in our Wikka installation.

I was just wondering if it's possible to have more than one username for the default_write_acl? If so, how do I go about doing it?

ACL privileges have a specific syntax: you can either use comma-separated usernames (like "FirstUser,SecondUser") or wildcards ("+" gives access to registered users only). See http://wikka.jsnx.com/ACLInfo for more information.

DarTar, in the ACL form for a page, user names need to be listed one per line (which means they're separated by a newline, not commas) - as explained on ACLInfo.

The problem is that the syntax for listing multiple users (or expressions) in the configuration parameters is not described anywhere - ACLInfo does not provide any help in that respect.

Looking at LoadAllACLs() and in wikka.php it doesn't look like the content is parsed by commas as separators while HasAccess() which uses this function actually explodes the content on newlines ("\n"). So it looks like a comma-separated list won't work in the config, and that actually "\n" must be used as a separator.

The problem with this is that it's not only hard to edit and read, but also inconsistent with other configuration options (like admins) that *do* use a comma-separated list.

Hopefully a better configuration system can address this as well.

I can't find the file (wikka.config.php)!! Am I stupid? The installation went fine, the systems runs smoothly - except that I'd like to change the ACL default and can't find this f** file.

Any ideas what could be wrong? In which directory is it supposed to be?

OK, sorry. It's found. But don't know why my FTP-Software (Cyberduck) doesn't show it. The WebFTP-Interface does.

I also use Cyberduck and have some annoying issues like the one you're reporting. I think this has to do with the (buggy) way Cyberduck handles file permissions.

I realized twice with different ftp programmes that it seems to take a while for the file to show up - or I have done something that made it show up which I do not know. Anyhow - maybe wait for up to 10 minutes, possibly switching to and fro from directorys ? A. M.

Is there actually a way to add multiple ACL items to the config file (even with JavaWman's suggested "\n" addition)???? I have tried dozens of combinations of tagging, bracketing, escaping, etc., etc., etc. but can only seem to get a white screen result or the ACL 'box' ends up with a string of stuff (no 'new lines' at all, but including the variations of tags and \n configurations) ... I can do an SQL query and change the database, but this is a far cry from setting up the "default" ....

After a look at the code (I am not at home, so no real investigation) but it seems to me that HasAccess() which only checks for one privilege uses

921 else
922 {
923 $tag_ACLs = $this->LoadAllACLs($tag);
924 $acl = $tag_ACLs[$privilege."_acl"];
925 }

instead of

else
{
$acl = $this->LoadACL($tag, $privilege);
}

(why do load all acls if we only check one?)

I can't find the real source of the error but instead having HasAccess to explode the Acls, wouldn't it be more logical to have Load(All)Acl(s) do the job. Would result in a more complex array, though. (And using commas instead of "\n" [unless we want to allow commas in usernames]).

WazoO, please open a ticket for the issue so we won't forget.

Yes, this should be posted as a ticket with top priority for 1.1.6.3 - thanks for bringing this up.