NineChime forum

1) Copy all the files from the "oekaki" folder to a new folder on your server

Apache serves all its files from a folder called "htdocs".  If you browse to the folder with a Windows computer, the path should be something like C:\Program Files\Apache Group\Apache2\htdocs\.  That's where Apache stores files that are accessible from web browsers.  That's where you should put the oekaki folder, if you haven't specified another location for your files (on my computer, the "W:\" drive is my htdocs folder, so I don't have to go into "Program Files" all the time).

Sorry, but I'm not familiar with XAMPP (I installed everything individulally), so you might have to look for the htdocs folder.

Let's suppose that Joomla is in the base folder of the server, so if you visit "http://www.server.com", Joomla is what comes up.  If you were to log in via FTP, the first thing you should see is all the files used for Joomla.  Just create a new folder called "oekaki" and put the files in there.  If you see a folder called "public_html", "www", "home", or something similar when you log in, then the oekaki folder would go into that.

The URL would then end up being something like "http://www.server.com/oekaki/", and you would just have to link to the board from somewhere in Joomla.

3) View the folder on your server, and it will redirect you to the installer

What do you mean with view the folder from the server? I´m making a mess of things.... sad

Once the files have been copied, open up a web browser, and type in the path to the oekaki.  The installer will run automatically.  On the Internet, that would be "http://www.server.com/oekaki/", or from a local machine, it might be something like "http://local_server_name/oekaki/"

What exactly do you type in to view Joomla?  Knowing what path you are using now would tell me how your computer is set up.

Finally, I think I´ll have to make a web page with the Oekaki in it and call it from Joomla...am I right?

Yes.  The oekaki can't run within Joomla.  You have to link to it, as if you were linking to someone else's web site.

The oekaki should go into its own folder, and use its own database.  If you're using Apache (instead of a sitebuilder server), there should be no conflict between your CMS software and the oekaki.

I'm not familiar with Joomla, but I presume it would look something like this on your server:

./
   /database_layers
   /modules
   /other_stuff
   .htaccess
   index.php
   logo.png

You shouldn't have any trouble adding an "oekaki" folder in there somewhere.  The ".htaccess" file is what declares security rules for pages served by Apache, and it only applies to files and folders within that directory (so each directory would require its own ".htaccess" file).  Files in the oekaki folder should not be governed by the ".htaccess" file, if you have one.

If you want Joomla to share logins and memberlists with the oekaki, I'm afraid that isn't possible without a lot of custom programming.  Both Joomla and Wacintaki would have to be modified.

If you're having a strange problem with the Wacintaki installer, I'd need more information about the server or any messages you get from the installer.