L’expérience est faite pour être partagée
En bref...
- C'est fait ! Lightroom 3 est maintenant dispo : http://www.adobe.com/fr/products/photoshoplightroom/features/?view=topnew 2010-06-08
- Bonne nouvelle : #Lightroom 3 disposera d'outils de correction automatique de la distorsion et du vignetage optique : http://bit.ly/aKa88F 2010-04-27
- #Lightroom 3 beta 2 est tout chaud ! http://bit.ly/afv7pQ et http://bit.ly/c25SsS 2010-03-23
- C'est parti pour une journée au salon de la photo ! 2009-10-18
- Salon de la photo : samedi ? dimanche ? samedi ET dimanche ? 2009-10-14
- More updates...
Mots-clefs
Adobe Apple Canon Capteur Colorimétrie Compact Drobo Enfuse Entretien EOS 5D Mark II Epson EXIF Forum Full Frame Géolocalisation Gallery GeoSetter Google Maps GPS HDR Impression Introduction iPhone iPhoto Leica Lightroom Métadonnées Magellan eXplorist Microsoft Miroir Mise à jour Module Nikon Photosynth PhotoTrackr Plume Résolution R1900 Sauvegarde SensorKlear Sigma Stockage Test X-Rite Yahoo! MapsAutres blogs photo
Galeries photo

about 9 months ago
Problem during export:
“An internal error occured: Expected header 1 ‘field’ sub-item to be a string, not nil”
Lightroom: 2.5
Gallery-Version = 2.2.5 Kern 1.2.0.7
PHP-Version = 4.4.9 apache2handler
Webserver = Apache
Datenbank = mysql 4.1.22-max-log, lock.system=flock
Werkzeuge = Exif, Getid3, Thumbnail, Gd, LinkItemToolkit
Beschleunigung = partial/900, partial/900
Betriebssystem = Linux dd13608 2.6.25.20-25.1-pae #1 SMP 2009-03-12 13:13:03 +0100 i686
Standard-Motiv = carbon
gettext = Aktiviert
Sprache = de_DE
Browser = Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_1; de-de) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
Zeilen in der GalleryAccessMap Tabelle = 33
Zeilen in der GalleryAccessSubscriberMap Tabelle = 1903
Zeilen in der GalleryUser Tabelle = 3
Zeilen in der GalleryItem Tabelle = 1898
Zeilen in der GalleryAlbumItem Tabelle = 24
Zeilen in der GalleryCacheMap Tabelle = 7837
about 9 months ago
Thanks for the feedback.
Problem reproduced and fixed in the 2.0.3 release.
about 6 months ago
Salut!
Really a great plugin, thanks! The only problem is, that – being on Mac – special characters (umlauts) get crippled when uploading to Gallery. I don’t have this problem on Windows, but get the same effect, when uploading to a Coppermine image gallery. I found this thread http://gallery.menalto.com/node/72147, but the workaround, described there, did not work in my case.
The problem obviously has to do with the way, on Mac metadata is written to jpg files. It is NOT a Lightroom problem solely, I had the same problem with ViewNX for instance.
After hours of research I found a workaround myself, which consist in rewriting the tags, which are of interest for me and for the export to Gallery, with the help of exiftool while converting special characters to entities. Here is the code:
exiftool -r -overwrite_original -E ‘-Description>ImageDescription’ ‘-Description>Caption-Abstract’ ‘-Subject>Keywords’ ‘-Location>Sub-location’ ‘-Country>Country-PrimaryLocationName’ ‘-City>City’ /directory/where/the/image/files/reside
I created a routine with Macs Automator (called automatically by Lightroom after exporting), which does not only execute the command above, but also uploads the resulting files via ftp to the tmp directiory of Gallery. But from here on, I do the last step the manual way.
Did you hear about this problem with special characters? And do you have an idea, how possibly fix it in a more elegant way than described above? I would love to use your plugin, but also keep my german umlauts in descriptions, keywords etc.
Regards
Tobi
about 6 months ago
When attempting to contact a server using HTTPS, line 36 throws a ‘An internal error has occurred: [string "GalleryRemoteProtocol.lua"]:36: attempt to concatenate local ‘raw’ (a nil value)’
I have fallen back to non-encrypted connection with success, although if you can make this wonderful plugin SSL compliant I would be very happy
Alternatively, either a warning that HTTPS breaks, or a error that means something to the user would be good.
Thank you!
about 6 months ago
Thanks for the feedback!
I have never tested the plugin with HTTPS, however, it should work.
There are a few reasons for it not to work :
the certificate used for the SSL handshake is not signed by a traditionnal CA or maybe that the CA has not been declared in the list of the trusted AC on the OS (if LR refers to this list to check a certificate)
the site uses HTTPS and HTTP authentication. In the second case, the plugin can not provide any login and password for the HTTP authentication.
Does any of the previous reasons apply here?
about 4 months ago
I have the same problem as Amaud.
An internal error has occurred: [string "GalleryRemoteProtocol"]:36: attempt to concatenate local ‘raw’ (a nil value)
I am not using https, using 2.0.4 with lightroom 2.6 gallery 2.3
This happens occasionally – especially when I am uploading many files or one upload session after the other.
Only had this recently – last 3 months
about 4 months ago
Sorry – same problem as Bel.
about 4 months ago
First of all, thanks for the great plugin, it make the workflow quite easy for me.
Nevertheless I have two suggestions.
As I do not upload all pictures to Gallery2 it would be great to be able to filter based on an information, which pictures are already uploaded, eg to be able to reload them to Gallery.
I saw this function in the plugins ofJeffrey http://regex.info/blog/lightroom-goodies/picasaweb#history .
During the export a flag in the custom metadata is done, indicating it is uploaded to a certain place.
Another option, but maybe to complicated would be also beside the upload to Gallery indicator the information in which album it is loaded.
Nevertheless it is a great tool, so just ideas to make it even better.
THANKS
about 4 months ago
Hi,
Thanks for the feedback.
I’ve already studied this feature. Bad news : Gallery 2 does not assign any ID to the elements (albums, photos, movies, etc.) so that it is very easy to modify an uploaded elements afterwards. I would also love to be able to reupload a picture after I improve the developments settings.
The fact is that if I log where an element has been uploaded, I may ran into troubles : Gallery may remove/change the filename (spaces and other characters are replaced with _) which is not notified to the plugin once a picture is uploaded. If a user moves/renames/duplicates a picture, then once again the problem occurs. If I implement such a feature, I expect to receive a lot of complaints from users saying it does not work, so I prefer not to.
Second bad news is that Gallery 3 will behave the same way… I would have loved to see the Gallery team take a few features from Flickr such as this one…
about 2 months ago
I am getting this error when I try to export my photos.
An internal error has occurred: [string "GalleryUploadTask.lua"]:86: attempt to call field ‘versionTable’ (a nil value)
about 1 month ago
Can you make it compatible with Gallery 3.X?
about 1 month ago
I will.
Gallery 3 does not use the Gallery Remote API. Instead, the development team is building a brand new REST interface, meaning that I will have to code a totally new API to access G3.
First, I wait for this API to become “Gold”, then I will code the same features that already are available to G1/G2.
I’ll then check what I can do to make a better use of LR3 new features such as Publishing Services.
about 1 month ago
Hey, great plugin, works like a charm, I couldn’t possibly use gallery if it weren’t for your plugin. So thanks a lot for your outstanding work.
One thing keeps bugging me, though. I frequently upload pictures to one of three different albums, always using the same settings. Being able to save configurations as Export Presets would be really, really cool. For now I always get an ‘internal error’ saying that ‘album’ is null and couldn’t be concatenated. No idea if this can be done, I’m still quite useless at LUA, though I’m learning.
Ah, another thing, while I’m at it .. a super-simple implementation of replacing images already in place would still help lots of people, you could just put a big red “Experimental – use at your own risk” next to such an option to keep problem reports down. In my case, just receiving a prompt “Replace Image Yes/No” when there’s already a photo with the same filename in the current album would do perfectly well. There’d be a lot of cases where this wouldn’t work as intended, but that’s why that option would be unchecked per default and why it’d have a big red warning next to it. This couldn’t possibly work as well as the flickr publishing service, and a lot of people would screw it up, but it would be extremely handy for a lot of us out there.
As to the first feature request, a two-click-export (one for the context menu, one for the export preset) would just totally rock.
So long
Felix
about 1 month ago
Hi Arnaud,
thank you for your great work! I am using LtG for a long time. Until today I worked with LR2 and had no problems.
Unfortunately your plugin does not work together with LR3. I got the following error message while exporting pictures to my G2 (translated from German to English):
“An internal error occured: LrCatalogDo was marked depreceated in Lightroom 2.0 and is not supported as of Lightroom 3.0. This call is no longer needed.”
Allthough I am able to create new albums, I am not able to upload the pictures.
Is there a way to bypass this error?
A second thing, which I would like to improve is the list of existing albums: Because that I have some hundreds of albums in my Gallery it is annoying to navigate with the current kind of list of existing albums. It would be great to have dropdown list like normal Windows or MacOS dropdown lists with a navigation bar on the right side. This would improve navigation very much!
about 1 month ago
Hi,
Thanks for the feedback.
I did not have time to test completely my plugin with LR3. However I will and if something needs to be fixed, it will.
Regarding the UI to select the album, I have the same problem. I did not find anything better yet since LR1 and LR2 only offer a subset of the visual widgets we are used to on our machines : there was no “tree” widget, so I had to chose the less bad solution which was a drop-down menu. I’ll check if LR3 came with additional widgets that may solve this issue.
about 2 weeks ago
Hey there,
Thanks very much for this plugin. I have been using it succesfully for a while however, tonight it has stopped allowing me to upload pictures. I am getting two errors:
[string "GalleryRemoteProtocol"]:36: attempt to concatenate local ‘raw’ (a nil value)
and
An internal error has occurred: [string "GalleryRemoteProtocol"]:36: attempt to concatenate local ‘raw’ (a nil value)
Please let me know if there is something that I can help test with or if there is a work-around.
Thanks!
about 1 week ago
Hi,
I have no idea where it’s coming from. I need to get the full log file in order to understand where the function has been called.
Please send me the full log file of the plugin (activate the login function within the plugin manager – select the plugin and set the log level to verbose).
about 5 days ago
Hi there, I have tried to enable logging but now I can’t get anything about the plugin to work. Is there a way to reset the plugin and it’s cache?
about 5 days ago
Hi Arnaud!
I saw, that you moved to 2.0.4. So I tried it again with LR3 and now it seems to work fine! Thank you for that!
Do you have news about the UI widgets in LR3 (DropDown vs. Tree)?
Thank you for your excellent work!
Cheers,
Thomas
about 5 days ago
If I switch to HTTPS on my server, I get the same error message. Could it be, that you are using a self-signed webserver certificate or an untrusted certificate as me?
I tried to enable logging, but cannot find the logfile. Where will it be written?
about 4 days ago
Hey Thomas,
I am not using an https connection so I don’t think that is the problem… something has changed with my install but I can’t figure out what.
Now lightroom just errors and won’t even try to run the plugin.
about 4 days ago
The logfile is writen in the “My Documents” directory on Windows, and in the “Home” directory in MacOS X.
about 3 days ago
The plugin has no cache, however, it relies on Lightroom to manage its preferences. If you want to totally remove the plugin, you have to remove the plugin from its directory and you have to edit Lightroom’s preference file (it’s a text file), look for the block related to the plugin, delete all lines. Be careful : make a backup of this file before editing it.