Closed (fixed)
Project:
ImageCache
Version:
5.x-1.2
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2007 at 15:40 UTC
Updated:
20 Dec 2007 at 17:36 UTC
I am trying to get imagecache working on lighttpd server... I have clean URLs enabled, but despite that, when I create new preset 'test', and when I want to add a new action, lets say 'scale', when I click on Update, I get following message:
Flushed Preset Images (ID: 10)
Updated preset "test" (ID: 10)
it happens for any action that I want to do, it doesn't allow me to add any actions....
Any thoguths on this one? I repeat again, clean URLs are enabled and working on this lighttpd server.
k.
Comments
Comment #1
kalashari commentedok I managed to create new preset and set scale options, but imagecache did not create new directories... I created 'test/files' dir inside files/imagecache dir and set write permissions, but no luck either.... Imagecache would not create scaled images... I don't know why.
Comment #2
kalashari commentedThis thing is really giving me a hard time... It was all working on Apache setup on my shared hosting before I moved to VPS, where I set up lighttpd... Imagecache is simply NOT creating any images now, as it's supposed to.... I manually created all folders where images should be, I chmod folders to 777, and still it is not creating any images.
Anybody have an idea?
Comment #3
jhuckabee commentedI got it working with this re-write rule:
"^/files/imagecache/(.*)$" => "/index.php?q=files/imagecache/$1"
Give that a shot.
Comment #4
kalashari commentedhey thanks a lot, that worked for me !
Comment #5
quicksketchAn interesting solution, but you'll find that results in Drupal handling all your images! There's not much 'cache' involved if you're telling imagecache to generate the image again every request.
Comment #6
kalashari commentedYeah, I noticed.. You are right. But is there a better approach to this?
Comment #7
fwenzel commentedThere absolutely is a better way: Lighttpd's (relatively) new mod_magnet module is able to do all the magic that Apache's mod_rewrite can do, including checking if files exist. Here is the link to a blog post of somebody who implemented this specifically:
http://pixel.global-banlist.de/2007/2/6/drupal-on-lighttpd-with-clean-urls
Comment #8
jhuckabee commentedthe mod_magnet solution works great with a noticeable performance boost since drupal is no longer handling all images
Comment #9
dopry commentedComment #10
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.