Piwigo.org

Zaphod · 2011-08-28 15:52:34

Strange, I just updated some photos where I changed the filename... and it worked.
I had to manually select the photos for republish.
I use version 1.4.2

Gotcha · 2011-08-28 15:57:33

I'm in version v1.5

alloyphoto · 2011-09-11 01:35:23

Gotcha wrote:
I have a question:
How to synchronize the file name?

I don't think filename can be updated, at least I don't see an option to specify an alternative filename using the pwg.images.setInfo method.

alloyphoto · 2011-09-11 01:37:38

Piwigo plug-in version 1.5.1 is available: http://alloyphoto.com/plugins/piwigo/

This update fixes the issue with using the "Synchronize Metadata" and "Un-mark to Republish" functions - in earlier version of the plug-in they could produce a "No photos selected" error when in fact there were selected photos.

Zaphod · 2011-09-11 10:22:40

alloyphoto wrote:
Gotcha wrote:
I have a question:
How to synchronize the file name?
I don't think filename can be updated, at least I don't see an option to specify an alternative filename using the pwg.images.setInfo method.

The "real" filename, the one that is like : "20110911100649-43f131e9.jpg" cannot be specified.

The "filename" displayed inside piwigo (which is only a value stored in the database) can be updated.

I just verified it.
- Published one photo
- changed the name inside lightroom
- republished

The filename is changed in Piwigo.

It also works when changing the export rename mask in the plugin options.

Gotcha · 2011-09-11 14:43:42

Hi,
Ok the filename is now correctly changed.

I feel like there is bugs on the buttons of publication. I continue my investigations.

Thanks.

alloyphoto · 2011-09-11 15:43:19

Zaphod wrote:
The "filename" displayed inside piwigo (which is only a value stored in the database) can be updated.

You are correct, this corresponds to the "Title" metadata field and it can be updated via republishing or by using the "Synchronize Metadata" function on the Extras screen.

Zaphod · 2011-09-11 16:08:08

Filename is different from medata's "Title".

The filename displayed in piwigo corresponds to the name the would have if you export it the usual way.

Piwigo replaces the filename by something like "20110911100649-43f131e9.jpg" but stores the original filename in the database.

alloyphoto · 2011-09-11 16:14:23

Zaphod wrote:
Filename is different from medata's "Title".

The filename displayed in piwigo corresponds to the name the would have if you export it the usual way.

Piwigo replaces the filename by something like "20110911100649-43f131e9.jpg" but stores the original filename in the database.

That's what I meant. The filename is assigned at the upload time of the original file and it can't be changed without replacing the binary content of the photo. If you modify photo's metadata only, then republishing does not replace the JPEG file, only the metadata gets updated. This way, you can update the "Title" but not the filename.
However, if you change develop settings and then republish, the entire JPEG file is going to be replaced, and if you modified your File Naming settings at that time, the new name is also going to be recorded. Keep in mind though, when JPEG is replaced you will lose comments or ratings the original photo had.

Zaphod · 2011-09-11 18:30:20

alloyphoto wrote:
However, if you change develop settings and then republish, the entire JPEG file is going to be replaced, and if you modified your File Naming settings at that time, the new name is also going to be recorded. Keep in mind though, when JPEG is replaced you will lose comments or ratings the original photo had.

None of these are lost.
The binary file is changed in piwigo, but its database entry stays the same, so you keep everything.

That's what's great with this plugin & piwigo.

I won't use a publish service which loses everything when you republish a modified photo...
The point of publishing services is to be able to update a photo when you want, easily.

Last edited by Zaphod (2011-09-11 18:33:43)

alloyphoto · 2011-09-11 18:38:34

Alright, perhaps I am mistaken, It's been a long time :)

alloyphoto · 2011-09-12 16:32:49

I found another issue with updating photo tags when using the "Synchronize Metadata" function. The fix will be included in the 1.5.2 update, which should be available by tomorrow.

alloyphoto · 2011-09-13 05:58:30

Ok, version 1.5.2 is now available for download.
Now "Synchronize Metadata" works correctly and keywords (tags) are updating as expected.
Here is the link to the plug-in's home page: http://alloyphoto.com/plugins/piwigo/

Guys, here is a gentle reminder - please don't forget to rate the plug-in at Adobe Exchange (you'll find the link in the side bar on the plug-in's home page), and also recommend the plug-in on Facebook and Twitter - the social buttons are located in the bottom section of the side bar on the plug-in's home page. Thanks!

Last edited by alloyphoto (2011-09-13 06:03:27)

Orisha99 · 2011-09-27 10:05:09

Hello,

I'm now using Vladimir's registered plugin (1.5.2, on windows XP SP3) with Lightroom 3.4.1 and the version 2.2.5 of Piwigo on a 2.6.18 xenU, hosted Linux.

Everything works fine in my first tests at home. Only I find the plug-in lacks the ability to change permissions on the albums.

So, when I create an album in the plug-in and publish it on Piwigo, this albums appears as public, and I have to connect to the gallery to change its status and adjust users permissions.

In the professional environment (our university's photo library, which I'm now setting up, planning to use LR, the plugin in Piwigo in the same combination I have now working at home) this will be a problem. The unauthentified visitor should not have any access to the pictures before their legal status is ascertained, which requires some time in certain cases.

Of course I will connect to Piwigo as soon as the album is uploaded, but there is an interval during that time when the album is unprotected, and I would like to eliminate this step completely.

Vladimir told me a permissions change feature is not implemented in the API as yet. I think this would be a great idea.

Are there any project to add the feature to the API? Without compromising security, of course, which I suppose isn't simple?

Best regards,
Orisha

Zaphod · 2011-09-27 13:03:07

If you put this line in the: local/config/config.inc.php file:

Code:

$conf['newcat_default_status'] = 'private';

All your new albums will be private, with the access rights available for admins only.

Piwigo.org

Announcement

#256 2011-08-28 15:52:34

Re: Lightroom plug-in beta testing - invitation

#257 2011-08-28 15:57:33

Re: Lightroom plug-in beta testing - invitation

#258 2011-09-11 01:35:23

Re: Lightroom plug-in beta testing - invitation

Gotcha wrote:

#259 2011-09-11 01:37:38

Re: Lightroom plug-in beta testing - invitation

#260 2011-09-11 10:22:40

Re: Lightroom plug-in beta testing - invitation

alloyphoto wrote:

Gotcha wrote:

#261 2011-09-11 14:43:42

Re: Lightroom plug-in beta testing - invitation

#262 2011-09-11 15:43:19

Re: Lightroom plug-in beta testing - invitation

Zaphod wrote:

#263 2011-09-11 16:08:08

Re: Lightroom plug-in beta testing - invitation

#264 2011-09-11 16:14:23

Re: Lightroom plug-in beta testing - invitation

Zaphod wrote:

#265 2011-09-11 18:30:20

Re: Lightroom plug-in beta testing - invitation

alloyphoto wrote:

#266 2011-09-11 18:38:34

Re: Lightroom plug-in beta testing - invitation

#267 2011-09-12 16:32:49

Re: Lightroom plug-in beta testing - invitation

#268 2011-09-13 05:58:30

Re: Lightroom plug-in beta testing - invitation

#269 2011-09-27 10:05:09

Re: Lightroom plug-in beta testing - invitation

#270 2011-09-27 13:03:07

Re: Lightroom plug-in beta testing - invitation

Code:

Board footer