Help getting my IPS working... - Page 2

Chuck S · April 11th, 2006, 06:02 PM

If someone is not allowed to view the image they can not view it thats just how permissions work.

If they have permissions to view it then they will view it if they make a direct link to the image. If you prevent anyone and everybody to view your images which is something most people who are trying to protect there images would never do it works as noted. If you post the link you cant see anything.

Johnny Doomo · April 11th, 2006, 07:10 PM

So if a PP owner wants to keep their images viewable to all on their site without registering, but wants to prevent hotlinking it's impossible without doing all image sizes with a htaccess? (IE: I want to prevent hotlinking on full and med while keeping thumbs hotlinkable)

Chuck S · April 12th, 2006, 06:51 AM

You can drop an htaccess in the storage path area sure.

Johnny Doomo · April 12th, 2006, 10:14 AM

Quote:

Originally Posted by Chuck S

You can drop an htaccess in the storage path area sure.

uh? That didn't really answer the question. Where do I put it to only block full and medium and not thumbnails?

Chuck S · April 12th, 2006, 10:42 AM

In Admin => Image Protection => Edit Fullsized htaccess

This places an htaccess file in your special storage directory not the regular data directory

Johnny Doomo · April 12th, 2006, 12:36 PM

OK looking at this site: http://altlab.com/htaccess_tutorial.html

I used this in the fullsize htaccess:

Code:

Content visible to verified customers only.

and changed the mysite to my domain and changed the "/images/nohotlink.jpe" to http://www.domain.com/images/banners/nolink.gif

but when I test the image in their hotlink checker it still shows the image. Any ideas?

Does it have anything to do with using the watermark.php to call the file, hence there is no image file extension called for the htaccess to block? Or if you have a better suggestion for an htaccess I can try that and see if it works any better.

Chuck S · April 12th, 2006, 01:12 PM

Code:

Content visible to verified customers only.

Not an htaccess guy here but you can try that also try the htaccess serving the files normally with no watermark.php script

Johnny Doomo · April 12th, 2006, 01:34 PM

I can't turn off watermark.php because I'm using the IPS.

IPS doesn't work unless watermark.php is used.

So if I turn off the watermark.php processing all fullsize images are dead on my site.

Adding the php into the htaccess did not fix the problem.

Chuck S · April 12th, 2006, 01:45 PM

If your using the optional storage path to point to some directory below your webroot for medium and large images you do not have to use watermark.php to serve the images.

http://www.reeftalk.com/gallery/show...4/limit/recent

Now place your htaccess file in place for the fullsized and test. My images are below the webroot and can not be accessed

Johnny Doomo · April 12th, 2006, 02:24 PM

Quote:

Originally Posted by Chuck S

If your using the optional storage path to point to some directory below your webroot for medium and large images you do not have to use watermark.php to serve the images.

http://www.reeftalk.com/gallery/show...4/limit/recent

Now place your htaccess file in place for the fullsized and test. My images are below the webroot and can not be accessed

You really should read all of a post. Most of the time there's important information below the first sentence.

"So if I turn off the watermark.php processing all fullsize images are dead on my site."

I had mentioned this before how I learned that you have to use watermark.php if you use IPS and that I was mad that it wasn't mentioned anywhere that you had to use watermark.php if you wanted to use IPS. I assumed since you never said anything different that that was infact the case. If large images are suppose to show up when using IPS and with watermark.php turned off, what's wrong with my site? Settings or something?

Chuck S · April 12th, 2006, 02:46 PM

Johnny

I read your post and please read my response. I use the optional storage options just like you on my site and I gave you a link to my site. I am not using watermark.php to serve the image and my images are not dead. Therefore there would be something wrong somewhere in a setting maybe if you have to use watermark.php to serve the images when you use an optional storage path.

You can post a url here and email me an admin login

Johnny Doomo · April 12th, 2006, 06:31 PM

Well I don't mind that watermark.php is being used. The question is, can it interfer with the htaccess trying to prevent hotlinking in the directory above the webroot where all the large images are located? If not, I would like to keep using watermark.php, but I want to get the htaccess to work which it's not. Do you have any other ideas that I can try or look into before I consider giving you admin access?

Thanks.

Chuck S · April 12th, 2006, 06:53 PM

Using watermark.php which is not an image extention yes would interfer with the ability to use htaccess.

I can not think of anything that would affect how our program works on your site if your using unmodified files from our distribution. I have now tested using storage image path on 5 separate sites all perform as noted.

Johnny Doomo · April 15th, 2006, 04:57 PM

What should it show as the location of an image when you do a right click and image properties on an image that is stored above webroot?

When I turn off using the watermark.php file, but I have fullsize images stored above the webroot and I look at their properties it says this:

http://www.domain.com/images/data/2/TMSX0005.jpg

The medium size image if turned on though loads fine from

http://www.domain.com/images/data/2/medium/TMSX0005.jpg

I have the IPS storage option set right as far as I know like this:

Current PATH setting: /home2/domain/domain_images/
Current URL setting: http://www.domain.com/images/data

So why doesn't it know where to get the fullsize images from unless I turn on the watermark.php processing? A better question, how do I fix it?

Chuck S · April 15th, 2006, 05:18 PM

Nevermind yes use watermark.php and IPS as I stated months ago only moves large images not mediums.

Your not going to use it the way you want because it is not written that way.

Unless there is some htaccess trick I am unaware of you can lock down large but not medium.

You could use IPS and have no medium and achieve what you want to do otherwise you would need to modify your code to suit your specific needs.

Johnny Doomo · April 15th, 2006, 06:27 PM

Yeah, I figured that part out a while ago. The problem that I'm reporting in this thread now though still exists. Even with mediums turned off, I still need to protect the large images. The large are normally in with the thumbnails right? So you turn on IPS so that they are above webroot and that they are in their own folder so I can use an htaccess to block the images in that folder. Well the images in the folder above webroot won't shot unless watermark.php is turned on. If watermark.php is turned on htaccess doesn't block the images.

You see my situation now? I could care less about watermark.php the most important thing to me is preventing hotlinking on my fullsize images. If that means turning off mediums, fine. If it means not using watermark.php fine. But I need the fullsize images to be viewable when using IPS which they are not. And from what I understand from the script, if you don't use IPS then they are in the same directory with the thumbnails and I don't want to prevent hotlinking of the thumbnails.

So in summary, how do I get fullsize images above the webroot to show on my site without using the watermark.php?

Chuck S · April 15th, 2006, 08:15 PM

watermark.php protects the file as I pointed that out shown earlier in this thread. If you have permission to view the file you will view it as in if your cookied in as we use authenticate or if you select anyone to view it. Otherwise it will be protected as noted.

Johnny no matter what way you slice it would need to modify the code to accomidate something like this. The software is not written to accomplish what you want specifically meaning protect this image but not that image. Image Protection is normally all or nothing.

Htaccess works on an entire directory meaning you can stop hotlinking but it will block all images in the data directory. If you move the files below the webroot yes you will need to use watermark.php to serve the files to view them.

Now no user will be able to post a link directly to the file like this using below the webroot cause the file does not exist.

http://www.domain.com/photopost/data/somefile.jpg

Now if someone gets crafty and somehow gets your watermark path like so

http://www.domain.com/photopost/watermark.php&file=23

Your going to go off user permissions.

Therefore you need to lock down unregistered viewers as I noted. You would set the switch in registration to make it so that only registered viewers can view the images

No one will be able to get the files hotlinking this way and this is how it was designed.

Just consider using the switch in registration options to keep guests from viewing the medium and large images and use watermark.php to server the images and basically you can have people hotlink thumbnails are you want and the others are protected. No code hacking required.

Johnny Doomo · April 18th, 2006, 08:49 PM

Well I have to say it's very strange the way you designed it. I want guests to be able to view images on my site, but not use terabytes of my bandwidth by viewing them on another site. I have make people register because I am trying to make a image hosting service. Hence, it would be pointless to make people to register to view the images. I was unclear that I had to use the watermark.php file if the images were above the webroot. Do you know if there is anyway to use the htaccess file when using the watermark.php? That seems like what it all comes down to. The medium images would be turned off, the large images are in their own directory ready to be protected by htaccess and the thumbs are in their own directory available to be hotlinked and linking to the fullsize page. The only problem is the damn watermark.php blocks the htaccess. Catch22

I've asked around and I've heard people claim that you can block php files with the htaccess, but appearantly it doesn't or at least doesn't code the same way as for image files. Any chance you can ask others that work behind the scenes at PP and see if they know anyway how to block the images being called through the watermark.php? If I can get that it will work very nice. If not, I have to bag all the work I did. grr

Thanks for any other help you can give. At least I understand the IPS and way the watermark file works a lot better now though.

Chuck S · April 18th, 2006, 09:01 PM

Well yes you have a catch 22 if you want to prevent hotlinking guests can not view the big images only thumbs by the switch stated.

I would suggest searching the internet for examples if you heard that. Maybe something like this

Code:

Content visible to verified customers only.

[/code]

Johnny Doomo · April 19th, 2006, 10:35 AM

That goes in the htaccess right? If so, it doesn't work either. I will do more research on the subject of blocking php files via htaccess. It apears this is going to be my only chance at using PP for this site. :\

Thanks for all your help and patients Chuck. Your alright in my book.