Architecture / Installation

Posted by Torsten Fabricius 26 May 2014 01:26 GMT-0000 posts: 1563

Hello Phi,

do you store images in the database - which is not recommended? If yes, I would guess a possible permission issue - BUT when you upgraded you did mostlikely not change permissions. So unlikely permissions.

Do you store in the file directory of your Tiki?

If yes, I guess one of the following issues:

A) You store in a directory in the Tiki root in /files, which I do NOT recommend for security (because files should not be accessible via the domain which points to the Tiki root).

If you upgraded by loading (unpack FTP or SVN UP) a new fresh installation into a new directory on your webserver, you maybe did forget to change the file permission of the folder /files to allow the webserver / the Tiki to write into the directory (a serverside setting, you can make in the control panel of your server account or via SSH if available) -> set to 755 or 777 or better less, if your webservers configuration allows.

B) You store in a directory "outside" of the Tiki root

1.) the relative path to the files directory might have changed, depending on how you organise your installations.

Path must be similar like
../../somedirectory/otherdirectory/files/gallery
../../somedirectory/otherdirectory/files/wiki
../../somedirectory/otherdirectory/files/tracker
etc.

I usually have ../files/somename

../ means one directory level up (up or out of the Tiki root)

2.) you might have forgotten to copy or to move the files directory to a place "near" the new installation, if you wanted to keep the same relative path to the files. => move or copy the files directory to the appropriate relative place "near" the Tiki root to get the same relative path as before. If that is not enough, see the next point ( 3.) ).

3.) you might have copied the files directory, but the file permissions (chmod, webserver) or the user (chown, webserver) have changed. => Check permissions on the server.

Please check and report,

Cheers,
Torsten