Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with caching and original image being returned #13

Closed
nickdunn opened this issue Aug 3, 2011 · 8 comments
Closed

Issue with caching and original image being returned #13

nickdunn opened this issue Aug 3, 2011 · 8 comments

Comments

@nickdunn
Copy link
Contributor

nickdunn commented Aug 3, 2011

See http://symphony-cms.com/discuss/thread/74805/

@michael-e
Copy link
Member

Approved. Looks like a cache request delivers the original image instead of the cached one. (The cached image is correct.)

@nickdunn
Copy link
Contributor Author

nickdunn commented Aug 3, 2011

Could it be:
b4b19fd

@michael-e
Copy link
Member

I guess you nailed it.

It's hard to understand the logic here, it's rather weird. I think @klaftertief was tricked by

if($param->mode == MODE_NONE){

which at this point probably means that there is "no need to do any (new) processing on the image". It does not mean that there has been no mode set in the request.

@michael-e
Copy link
Member

@klaftertief: Can you please check the mentioned commit and give us some feedback?

@klaftertief
Copy link
Contributor

Yep, @michael-e is right with his explanation. When images are read from the cache (server side) $param->mode is set to MODE_NONE. So the commit above should be reverted. This means, that the direct display mode is broken. Can you confirm this?

Sorry for the inconvenience.

@michael-e
Copy link
Member

Pull request sent (see above).

Yes, the direct display mode is broken. As soon as somebody found the time to fix this, we must change the submodule reference in the Symphony repo (and maybe release a new version?).

brendo added a commit that referenced this issue Aug 3, 2011
@brendo
Copy link
Member

brendo commented Aug 3, 2011

So is this issue is 'closed' by the above pull request and #15 is a new issue?

@michael-e
Copy link
Member

Correct.

@brendo brendo closed this as completed Aug 3, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants