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

QImageLabel Failing #152

Closed
vaibhav-kaushal opened this issue Feb 27, 2013 · 5 comments
Closed

QImageLabel Failing #152

vaibhav-kaushal opened this issue Feb 27, 2013 · 5 comments

Comments

@vaibhav-kaushal
Copy link
Member

One of my friends have been facing an issue with QImageLable - the trouble is that when he does not specify the CacheFolder for the lable, the image rendering fails. The reason specified in the error log is - 'filename too long'. Is there somehow we can fix this? The error log says this:

[Wed Feb 27 12:26:29 2013] [error] [client 127.0.0.1] (36)File name too long: access to /eNp9Vsly4zYQnU9J8ZhDJEqWF_okyXasZCxrLI2dnFIg2aQQgwAHAL1Nzb-nAQIgKXtycZXxen39uqnbJI6T6MuqIiV8JimwKDk5Sb6rJD5Jok-_flJaLkm2hyvBcpDR-focoZmHroSEpWACAZUcJ1FRZBkh0cBmQbLHvs10Gsenp9bmqIvD9Za-QXROk4lBxh7ZwYu2tljlNTAmfnkQkuX2qa2Qcv3XUgiZU060jTAegH-_ByctmDJuiiulaHi-k4SrmkjgmC9tY4QeLD271xpM3mkS1by0FUx9ki8NYVS_mgTx2Poe-xTbSgi9Nx2auLFJH_u410LSN0QImzNachMTOWFQtD2febt7kJpmPStMrEVtjU59DRuSY5vlA8313hbShejQa6DlXgc49vC2JllH3sw_74w1B6UCFDzmvGQdo7OBWnJL2BVlsCGmmPV5X1ALnAdIp4mPoK1-ZeDkshZ6Czr6wMo1uh4oaanUkhFT77obEE7hgqqakVc_AscaOjjgJymPvL-Z30IY4TltHPeRFU6QZu91Y7A1qUCZYDMsZqTk0-j5-XmUNSnkI8oz1uSgRt_a___JcKFGBXqp0e-oGpr9Vhdpb8wu3-0TSEY5hIxnfXSrJX0E0eiP4a88P_AOMr5FFVgZD9d8nmUogT_BAZOJBSr6siSNAnWPzedEU8FDxEmYRyNVWP0esWEwl5ykDPIwmMD4HXxrqISO8aMgSpKusIeXoMlpuBZCsB2tXZlhzboCL6UMogsl3FNFUwZhPY-930ZCAVjCHRjKbkDvRe5aaZ-iQa9-t9bdnuBrX6Yh8rWu2AIKnPYh1waZFzrc2iDUFcc_TWa6GKrb5CCSU3OThstgZFIw8fwzXZsWhaLt5A5MzjpOHZ_dUf5sD1SvbpH-
eyFJWRJL4xC4A0XfPgIupKjrd4DRDIpUCrayXCO7WRx16dERvzqV8znzbxt7uZ2nm__Ug8s9ZbnD5lKaM0CScfL9R78ps6cDAq0GzZR7GpwNEcu5E-7EQ7d8g8fvQLb4fiNyWtBO6k6fiDxIUtcosJ7BeDD7_xVgp9dlo7So5hr3P200uFZ7Kxts7Lnr4e62Ildzq7ADllypuPEtjGwjW0Gk3aa5Tg6ucLiVXxU4i0BbOOp_kCeyzSSttTr8Kthqt3sAD03GvV8gXcMeDfnaatUN9rwDWbkfAS27LgZardSCiezxkkEVvv4__gPKA72T/q.png failed, referer: http://cubed/opentest/forumTest.php

What can be the solution? I am stuck because unless you bring in the database again (and I don't want to bring that in) for this control, it may not be reliable. Otherwise, we have to make the 'CacheFolder' mandatory.

Regards

@olegabr
Copy link
Member

olegabr commented Feb 27, 2013

The issue #92 can be related to this.

@vaibhav-kaushal
Copy link
Member Author

Probably not. I guess what we are doing is to serialize/deserialize the
control and it is getting too long!

Compression/Decompression is working fine. Also, I am not able to reproduce
#92 on my end either.

On Wed, Feb 27, 2013 at 3:43 PM, Oleg Abrosimov notifications@github.comwrote:

The issue #92 #92 can be
related to this.


Reply to this email directly or view it on GitHubhttps://github.com//issues/152#issuecomment-14166137
.

Regards
Vaibhav Kaushal http://about.me/vaibhav.kaushal

@olegabr
Copy link
Member

olegabr commented Mar 3, 2013

The link where the problem is described: http://serverfault.com/questions/388858/how-to-fix-file-name-too-long-error-in-apache2

It seems that in a case of CacheFolder not set, the whole QImageControl architecture is broken. It can produce URL's that would be rejected by the web server. The QImageControl should be redesigned.

@vaibhav-kaushal
Copy link
Member Author

Yet another instance: http://www.c-integration.com/forum/showthread.php/50-qimagelabel-not-working

How about we make CacheFolder a mandatory property (which when not set will raise a red flag)?

olegabr added a commit to olegabr/qcubed that referenced this issue Mar 17, 2013
…or file name length.

* It fixes issues qcubed#92 and qcubed#152
* The example of QImageLabel is changed to use CacheFolder property.
* The exception is throwed if the CacheFolder is not specified and the resulting file name length exceeds the 255 limit.
@olegabr
Copy link
Member

olegabr commented Mar 17, 2013

The resolution proposed here: bug-152. Waits for the #188 to be accepted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants