Version: 4.3.0 Checked out on 2011-11-20
Multimedia Directory: media/
Use Media Firewall: Yes
Media Firewall Root Directory: /usr/www/users/user/family_media_fw/
Protect Thumbnails of Protected Images: Yes
Who can view non-watermarked images: Only admin-users
Add watermarks to thumbnails: Yes
Store watermarked thumbnails on server: No
Store watermarked full size images on server: No
My Installation maintains two Gedcom files, which should share the same media secured by the Media-Firewall. For one gedcom, everything works fine - the requests are forwarded to the media firewall and the pictures are directly accessible through a "http://domain.tld/media/filename.ext" link if and only if one is logged in properly.
But whenever I switch over to the other gedcom file (via http://domain.tld/index.php?ctype=gedcom&ged=faulty-gedcom) none of the media objects is loadable anymore. Direct access (http://domain.tld/media/filename.ext) results in the following error message:
"Fatal error: Call to a member function getServerFilename() on a non-object in /usr/www/users/user/family/includes/controllers/media_ctrl.php on line 451"
Clicking on one of the text-links where normally the thumbnails should be visible results in a Clearbox Error. Whenever I place a picture in the unprotected media folder, the issue dissapears, both gedcoms can access the media.
I have checked that both gedcoms use the same media-firewall directories, that both use the media-fw at all and that the paths are valid. I have disabled/enabled the media-fw multiple times, moved the fw-directory and used the file-permission-restore button. I have read the following thread which describes a similar problem. However, the redirection to the firewall script should not be the problem since it get no 404-errors and everything works perfectly for the original gedcom: https://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/3341541/index/page/1
Goal: Allow both gedcoms toaccess the fw-protected media.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version: 4.3.0 Checked out on 2011-11-20
Multimedia Directory: media/
Use Media Firewall: Yes
Media Firewall Root Directory: /usr/www/users/user/family_media_fw/
Protect Thumbnails of Protected Images: Yes
Who can view non-watermarked images: Only admin-users
Add watermarks to thumbnails: Yes
Store watermarked thumbnails on server: No
Store watermarked full size images on server: No
My Installation maintains two Gedcom files, which should share the same media secured by the Media-Firewall. For one gedcom, everything works fine - the requests are forwarded to the media firewall and the pictures are directly accessible through a "http://domain.tld/media/filename.ext" link if and only if one is logged in properly.
But whenever I switch over to the other gedcom file (via http://domain.tld/index.php?ctype=gedcom&ged=faulty-gedcom) none of the media objects is loadable anymore. Direct access (http://domain.tld/media/filename.ext) results in the following error message:
"Fatal error: Call to a member function getServerFilename() on a non-object in /usr/www/users/user/family/includes/controllers/media_ctrl.php on line 451"
Clicking on one of the text-links where normally the thumbnails should be visible results in a Clearbox Error. Whenever I place a picture in the unprotected media folder, the issue dissapears, both gedcoms can access the media.
I have checked that both gedcoms use the same media-firewall directories, that both use the media-fw at all and that the paths are valid. I have disabled/enabled the media-fw multiple times, moved the fw-directory and used the file-permission-restore button. I have read the following thread which describes a similar problem. However, the redirection to the firewall script should not be the problem since it get no 404-errors and everything works perfectly for the original gedcom:
https://sourceforge.net/projects/phpgedview/forums/forum/185166/topic/3341541/index/page/1
Goal: Allow both gedcoms toaccess the fw-protected media.
Did this work prior to upgrading to 4.3.0?
@GG
Was your question for @grumb or in general? To the latter, yes it worked before and after.
-Stephen
Hmm, why didn't it work for me.. Maybe I did it wrong