Closed (fixed)
Project:
Brilliant Gallery
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
8 Jul 2008 at 12:51 UTC
Updated:
1 Sep 2008 at 15:29 UTC
Jump to comment: Most recent file
well actually no full size image too. i get this code for my page:
<ul style="width: 106px;"><li style="float: left; width: 100px; list-style: none; background: #bbbbbb; height: 75px; padding: 3px; text-align: center; margin: 0; border: none;">
<a href="/drupal/sites/default/files/gallery/glest/s01.jpg" title="s01"><img style="border:0" alt="" rel="lightbox" src="/drupal/modules/brilliant_gallery/image.php?imgp=L3d3dy9odGRvY3MvdzAwNmVjNzAvZHJ1cGFsL3NpdGVzL2RlZmF1bHQvZmlsZXMvZ2FsbGVyeS9nbGVzdC9zMDEuanBn&imgw=100&imgh=75" /></a>
</li>
</ul>i used [bg|glest|1|100|sort|1|#bbbbbb|1|Screen] to generate the code.
but i dont see a thumbnail and cant open a link to the full size image, i only see a gray ractagle.
When i open the image link directly i get some php and sql errors:
Warning: imagecreatetruecolor() [function.imagecreatetruecolor]: Invalid image dimensions in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 126
Warning: imagecopyresampled(): supplied argument is not a valid Image resource in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 127
Warning: imageinterlace(): supplied argument is not a valid Image resource in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 129
Warning: imagecolortransparent(): supplied argument is not a valid Image resource in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 130
Warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ':2:i:0;s:24:"Content-type: image/jpeg";i:1;s:248:"PGJyIC8+CjxiPldhcm5pbmc8L2I+Oi' at line 1 query: UPDATE a:2:i:0;s:24:"Content-type: image/jpeg";i:1;s:248:"PGJyIC8+CjxiPldhcm5pbmc8L2I+OiAgaW1hZ2VqcGVnKCk6IHN1cHBsaWVkIGFyZ3VtZW50IGlzIG5vdCBhIHZhbGlkIEltYWdlIHJlc291cmNlIGluIDxiPi93d3cvaHRkb2NzL3cwMDZlYzcwL2RydXBhbC9tb2R1bGVzL2JyaWxsaWFudF9nYWxsZXJ5L2ltYWdlLnBocDwvYj4gb24gbGluZSA8Yj4xMzU8L2I+PGJyIC8+Cg=="; SET data = 'cache', created = 1215518803, expire = 1215778003, headers = '', serialized = 0 WHERE cid = 'bg_2c7ec6e20b24a4568560fee19c942f67' in /www/htdocs/w006ec70/drupal/includes/database.mysqli.inc on line 128
Warning: Cannot modify header information - headers already sent by (output started at /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php:126) in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 38
Warning: imagejpeg(): supplied argument is not a valid Image resource in /www/htdocs/w006ec70/drupal/modules/brilliant_gallery/image.php on line 135| Comment | File | Size | Author |
|---|---|---|---|
| #3 | patch1.diff | 3.81 KB | driki_ |
Comments
Comment #1
e_log commentedafter some debugging i found out that i could open the link to the full size image and it works with lightbox too, but i still get no thumbnail (GD Support is enabled)
Comment #2
e_log commentedi moved the site to a new server and viola it works like a charm, so i checked the gd version to see if it has something to do with it and there was a difference between the freetype version used. The one on the previous server was: 2.1.3 the new one is: 2.2.1.
my insight in this stuff is limited and I'm not sure if this was the problem, i just guess.
Comment #3
driki_ commentedHello,
I had the same problem.
Here is a patch with bug fix.
Comment #4
vacilando commentedExcellent, thanks, drico! Patch/changes applied in 6.x-1.2 and 5.x-4.1 (here without the cache_set change of course).
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #6
ericinwisconsin commentedI'm having this problem too. I'm pretty good with Linux line commands, but completely daft with dff & patch. Can someone list the commands to use the diff file? Thanks!
Comment #7
driki_ commentedI think you just have to get the patch and then
patch -p0 < patchfile
Or maybe get the module again, has the patch seems to have been commited