Hello
I am experiencing some issues with image upload when done via Java 'Upload Applet'. While all pictures are actually uploaded and added to the album, error messages, like the ones shown below, are returned:
Upload error: Upload failed: 'UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126187987|2|363|1)'.
Upload error: Upload failed: 'UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126188023|2|366|1)'.
Upload error: Upload failed: 'UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126188055|2|369|1)'.
Upload error: Upload failed: 'UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126188091|2|372|1)'.
Upload error: Upload failed: 'UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126188156|2|378|1)'.
For every 10 pictures I might get 5 uploads returning those. Again, all 10 pictures will be added to the Album.
Any ideas ? Also, should I worry about that ?
----
At the same time when adding pictures via 'From Web Browser' interface following error is displayed:
Error Detail -
Error (ERROR_OBSOLETE_DATA) : UPDATE g2_Entity SET g_modificationTimestamp=?,g_serialNumber=? WHERE g_id=? AND g_serialNumber=? (1126193898|2|475|1)
in modules/core/classes/GalleryStorage/DatabaseStorage.class at line 588 (gallerystatus::error)
in modules/core/classes/GalleryStorage.class at line 142 (mysqldatabasestorage::saveentity)
in modules/core/classes/GalleryEntity.class at line 294 (gallerystorage::saveentity)
in modules/core/classes/GalleryItem.class at line 409 (galleryfilesystementity::save)
in modules/sizelimit/classes/SizeLimitHelper.class at line 86 (galleryphotoitem::save)
in modules/sizelimit/SetSizeOption.inc at line 79 (sizelimithelper::applylimits)
in modules/core/ItemAdd.inc at line 152 (setsizeoption::handlerequestafteradd)
in main.php at line 173 (itemaddcontroller::handlerequest)
in main.php at line 87
in main.php at line 80
System Information
Gallery version 2.0-rc-2
PHP version 4.3.11 cgi
Webserver Apache/1.3.33 (Unix) mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_ssl/2.8.22 OpenSSL/0.9.7a PHP-CGI/0.1b
Database mysql 4.1.13-standard
Toolkits ImageMagick, NetPBM, Gd
Operating system Linux aristotle.neosurge.com 2.6.9-11.ELsmp #1 SMP Wed Jun 8 17:54:20 CDT 2005 i686
Browser Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Again, all the pictures in this case were added to the album
----
Gallery URL (optional):
Gallery version: 2 RC2
Webserver (with version): Apache version 1.3.33 (Unix)
Datatabase (with version): MySQL version 4.1.13-standard
PHP version (eg 4.2.1):PHP version 4.3.11
phpinfo URL (optional):
Graphics Toolkit(s): ImageMagick, NetPBM, Gd
Operating system: Win 2000, Java 2 PSE ver 1.5.0
Web browser/version: IE 6.0 SP1
G1 version (for migration bugs):
Posted: Thu, 2005-09-08 15:46
Posts: 32509
yep, you should take that seriously.
G2 has some features that are called / executed when you add items.
the add process worked, but one of these item add options didn't.
the question is why, because it seems to work for everyone else.
Posts: 3
Got the same problem. This occures when you set to scale the picture in "Edit gallery"--> Gallery Tab --> set max size.
It won't resize and produces this error message. ImageMagick is working fine. Have no idea how this can happen.
Posts: 32509
just tested imagemagick + sizelimit and added an image. it resized the inmage correctly. can't reproduce the error.
delete the db cache in site admin -> maintenance.
Posts: 32509
you can change the password again.
no idea why it doesn't work for you. i'm not quite sure if it should work right now (obviously it works for most users though).
we've found a problem in our framework a week ago and someone is working on changing it (save events are posted too early).
maybe your problem is related.
we should reevaluate this issue after this change is in cvs (+0.5-1 month from now).
if you want to fix your sizelimit issue now, you could open SizeLimitHelper.class and add a $item->refresh() before applying the changes.
Posts: 3
I had this same issue until I went to Maintenance section and:
* deleted template cache
* deleted database cache
* delete user sesssions
* optimize database
Works without errors now. Hope this helps.