|
|
File you requested does not exist error
This is generally the result of a few things. It is most likey because you do not have
Jinzora set for the proper directory structure. Make sure that you are using either (Genre/Artist/Album/Tracks -
Artist/Album/Tracks - or /Album/Tracks. This needs to be set at install time (or by re-entering
the installer per the upgrade/install documentation. Currently these different directory structures
are not optional. You also can not mix and match directory structures, Jinzora expects all folders/files
to adhere to the correct format (NOTE: This is on the list to be changed as of Jinzora 2.0)
|
|
|
You can't access this file directly
This almost always means that you've set Jinzora for PostNuke mode and you're trying to view it in standalone
mode. Please re-enter setup and make sure that you have Jinzora set in the right mode. If you do make sure
that if you are accessing it in Standalone mode that you see only "index.php" at the page name,
(not modules.php?op=modload.....)
|
|
|
Cannot open settings file for writing
For some reason Jinzora can not write to the settings file. This generally means that you forgot to run
"sh configure.sh" (on *NIX boxes). That script will give EVERYONE write access to the settings file.
There could be other reasons that Jinzora can't write to the settings file (settings.php), there are just
too many possibilites to cover here, but basically make sure that the webserver user has write permissions to the
file (which configure.sh should do easily)
Don't forget to run "sh secure.sh" when you're finished!
|
|
|
Why can't the installer write the settings file?
There are a few possible reasons for this. The first of which is that you forgot to run "sh configure.sh" for a new
install, which creates the empty settings file. Or on Windows you didn't create the blank file settings.php.
Another reason for this is that for some reason even though you ran "sh configure.sh" (or verified the permissions of the
file on Windows) that the webserver can't write to it. Check all the permissions and make sure that the file is
world writeable, that isn't the most secure way, but you can always change it later with "sh secure.sh"
|
|
|
How do I secure Jinzora without terminal access (via FTP)?
By simpling removing write permissions to the webserver user, chmod 444 should do nicely...
|