Hi all,
i have recently purchased and installed the gallery and i am very satisfied with it.
But now I have a few questions / suggestions.
1.) I get two errors: suhosin and open basedir, but everything works fine, especialy also upload because my hoster uses suPHP extension which is quite commen with webhosters these days. Safe mode is mostly only used to restrict certain functions these days. Maybe there could be a more granular check integrated if these two options really generate problems or not.
2.) Is there any possibility to hide the path name/image name in the adress field (URL)? For instance I disabled all download features, disabled the html gallery but the user sees the following in the address bar when looking at photos: "https://www.photo.gallery/soda/#/content ... K2cd2s.jpg".
So it is just to easy to navigate to "https://www.photo.gallery/soda/content/b ... K2cd2s.jpg and download the photo.
3.) When "hiding" a folder it is hidden in the menu, great, but if I know the location (from a search engine maybe? ) i could still view it by typing it in the address bar directly after the #
Is there a way to "disable" a folder. Maybe something that could be implemented in the next version.
4.) Is it possible to directly implement something like a disclaimer which the user has to acknowledge before he can enter the site. For example if the gallery contains adult material. Just a thought for the next version maybe.
regards
X3Photo Gallery Forums
X3 Photo Gallery Support Forums
Allow me to answer your questions except the first one, where maybe Nick can contribute:
#2 - You can hide the path in the URL. Go to the admin -> settings -> useswfaddress ... Set this to false. Keep in mind, you will loose your deep-linking possibilities if this is disabled.
#3 - Yes, a hidden folder is simply a "hidden" folder. It is not disabled or protected in any way. However, the only way you could find it, would be to know it existed. Google would not find it if it is hidden (unless you have had it public for some time previously). There will be a password function in the next release of Imagevue.
#4 - If you want something relatively abstract, I suggest you create your own html splash page with a disclaimer. That would certainly be the easiest and best way to do it. Simply have an index.html with disclaimer, that for example goes to gallery.html ...
#2 - You can hide the path in the URL. Go to the admin -> settings -> useswfaddress ... Set this to false. Keep in mind, you will loose your deep-linking possibilities if this is disabled.
#3 - Yes, a hidden folder is simply a "hidden" folder. It is not disabled or protected in any way. However, the only way you could find it, would be to know it existed. Google would not find it if it is hidden (unless you have had it public for some time previously). There will be a password function in the next release of Imagevue.
#4 - If you want something relatively abstract, I suggest you create your own html splash page with a disclaimer. That would certainly be the easiest and best way to do it. Simply have an index.html with disclaimer, that for example goes to gallery.html ...
#2 your suggestions did exactly the trick, many thanks, thats what i was looking for
#3 a password function would be nice, though a "disable" function as well. It is as I said just a suggestion for the next release maybe.
#4 creating a web page in front of the gallery would certainly do the trick I agree. Would just be a "nice to have" function if imagevuex could do it.
#3 a password function would be nice, though a "disable" function as well. It is as I said just a suggestion for the next release maybe.
#4 creating a web page in front of the gallery would certainly do the trick I agree. Would just be a "nice to have" function if imagevuex could do it.
Re: several questins / suggestions
The truth is, neither of those is actually killing imagevue. It's about how they configure it on hosting. Your case is maybe the single example of everything properly configured.alex1977 wrote:1.) I get two errors: suhosin and open basedir, but everything works fine, especialy also upload because my hoster uses suPHP extension which is quite commen with webhosters these days. Safe mode is mostly only used to restrict certain functions these days. Maybe there could be a more granular check integrated if these two options really generate problems or not.
At first we thought that suhosin just kills it until I found out that we have it on our own test server. Same with open_basedir and safe_mode this is just a warning that problem might emerge.
Actually safe_mode is little bit more complex than you describe, it doesn't allow php to access files which wasn't created from php which might interfere with images/folders uploaded by ftp. Thanks god it's deprecated in future php versions.
So if everything works fine, just never mind those notices.
firedev.com