Just make sure that in the manager configuration settings the paths are defined in the correct way. The image is called directly throuhg it’s unix path. These paths are different on different servers most of the time, so be sure to change them.
-
MODX Staff
- 10,725 Posts
Sounds like you don’t have the proper file permissions or ownership on the file at /var/www/vhosts/issenman.ca/httpdocs/assets/galleries/2/smureport2006.jpg
Likely, all of your images will need to have their permissions or ownership changed so they can be written to by the system user executing the PHP process (which varies widely, depending on your host server and configuration).
Hey OpenGeek,
I did change /galleries/2/ and all the files to 777. Is this what you mean? I’m new to this so please excuse the silly question. Thanks for the help.
Cheers.
Is there such file under /galleries/2?
this url didn’t return anything at least, what version of maxigallery are you using? I have made some modification with recent versions that it doesn’t choke if the database table contains pictures that are not anymore in file system.. that seems to be the case here. You can edit the maxigallery database table straight with phpmyadmin or similar to remove the pictures that are not valid anymore.
"He can have a lollipop any time he wants to. That's what it means to be a programmer."
Doze, I was using version .51 and upgraded to .52. Seemed to solve the problem. Resynching the gallery caused some issues but I think I can fix that by re-uploading the effected images in manage pictures.
Thanks very much for the replies. Keep up the good work. It’s much appreciated.