Active
Project:
ImageCache
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Oct 2010 at 13:43 UTC
Updated:
4 Jun 2012 at 18:48 UTC
Jump to comment: Most recent file
Hi Guys
I noticed that this module is not using drupal's API to send 403 and 404 errors. I reckon it should, that's what they are there for.
I'm attaching patches with that issue fixed.
One for 6.x-2.0-dev version
one for 6.x-2.0-beta10
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | imagecache-6.x-2.0-beta10-928646_1.patch | 1.09 KB | jm.federico |
| #1 | imagecache-6.x-2.0-dev-928646_1.patch | 1.09 KB | jm.federico |
Comments
Comment #1
jm.federico commentedComment #2
jm.federico commentedChanging to major, usage of Drupals API is a must for modules.
Without this, there are modules that won't report things correctly. Like statistics module (we won't know a 403/404 was sent). Or 404 Blocks module, well, becase no page is shown, no blocks are shown.
Also, if viewing an image in full page, user will just get a blank page and will have no idea what happened. It even confused me for a second, and I knew what was going on. There is no intuitive way of knowing what happened if you are not a developer. A normal user just gets nothing and thinks, hell, page is broken. And it is not, he just got to a 403 or 404 page.
Comment #3
sandrewj commentedMay need to be re-rolled now, but works fine.
Comment #4
mikeytown2 commentedThis would be a major performance hit. Fast 404/403 is a much better option.
Comment #5
fizk commentedNeed good reason to use Drupal core if there would be a big performance hit as per #4.
Comment #6
mikeytown2 commentedhttprl_fast403() and advagg_missing_fast404() are 2 examples of a simple fast 40* call that provides some context to the user. Right now you get a blank screen with no idea what module created it. As it is, you can sometimes think its a WSOD.