edmunds doug - dae

YACS has to get rights to files to modify them. This includes scripts for software update and configuration changes. For normal operations, YACS only has to save files and images in respective directories with the same names.

This allows for several permission shemes, depending of run-time constraints.

Most of the time YACS rights to the file system are those of the user/group assigned to the web daemon. A common setup in the case of Apache is to have YACS rights inherited from www-data.

To achieve maximum security levels, you could change ownership of all of the YACS directory to the user/group set for the web daemon (e.g., www-data/www-data is quite common), through the chown -R command to make it recursive.

Then use the chmod -R 770 to ensure that the world has no right on this part of the file system. To limit rights to the daemon user only you can even use chmod -R 700 which is the safest.

Yes, associates are allowed to post any HTML in any form. Every submission from members is filtered, and allowed HTML tags are defined in the configuration panel for users.

Also, YACS has a small but efficient Flash player, so you may prefer to attach a Flash file or movie to a page, and to add the following code in your page

[flash=file_id, width, height]

where file_id is the id of the posted file.

Bernard:

Based on schema I've worked on, correct backward referencing is always hard.

Recently, I've been using the commercial wiki product from Atlassian called Confluence.

Confluence has 2 features that really set it apart, and justify real $s for the product. First is the backward link consistency, as mentioned previously.

The other is edit journaling. As you type in the wiki page form, Confluence is journaling your edits up to the server (xmlhttprequest, aka, ajax, I'm assuming). Have you ever started a form and switched to email, broke for dinner, and accidentally closed the window when you didn't mean to?

Well, with Confluence the next time you visit or edit that page, you're alerted that there's an unfinished edit on the page and would you like to resume those edits or discard them. I've come back to pages I forgot I was editing 6 months ago and had it remember!

Cool beans, IMHO.

On the other hand, Confluence does not have any forum or maillist features, and those turn out to be really valuable when collaborating, to created a permanently logged multi threaded discussion. (Page comments don't have the threaded structure and don't cut it for, say, collaborative design docs on a wiki.)