So, I've had so many problems with koken in the past, until I decided to invest in a cloud server that I could configure entirely myself. So I made the big decision to switch to my own server with Ubuntu and nginx as base, so that I could check all error logs and install the particular services that would be required.
I transfered all my stuff from my old web host and finally got set up, everything worked smooth, all the errors of the past were gone with the wind, no issues whatsoever. My own photography site works like a charm.
So when it came to putting up a web site for our photography association, it was no doubt that we would turn to koken... except now when I installed koken in a different directory, on a different domain name, in a different database... koken started showing its bad side again. For no reason that I can figure out it behaves like this:
1) Front page (index.php) does not generate a page (it's pure white)
2) Switching themes is not possible, it just loads forever on a blank white page after trying to do so
3) It does not show any uploaded images, but the images do end up in the originals-folder, but after that koken just decides to ignore them, all folders in the koken-installation are 777, yet still the images don't show up
4) We have made a custom theme for koken, and when we switched to that it worked, except it loads data from some central koken-database and every thumbnail (that isn't on the server) shows as black, and it has loaded some of the posts we made on our previous web server from what we determined is some cloud storage from koken, because it's a completely clean install.
I can't even begin to wrap my head around this, because the very same koken is installed and runs my other photography website, with NO issues.
note: I am using nginx and fastCGI.
This question has received the maximum number of answers.