Anyone else having this issue? Lightroom just updated to V15... That requires the Alloyphoto piwigo plugin to updated. Alloyphoto site is down (database issues). I can't get a response from them either. Is this plugin dead in the water?
Offline
Hi @Film54
Yes we know and we're concerned. I'm trying to contact Vlad but I don't get any response. Here is the email I sent him:
plg by email to alloyphoto wrote:
Hi Vlad,
I hope you're fine.
For several weeks now, your website alloyphoto.com gets an "Error establishing a database connection". Of course it prevents any user to buy a new license, but it seems to also block the use of the plugin in Lighroom.
For a few users, the Piwigo plugin for Lightroom is an important piece of the Piwigo experience. Having it unusable from time to time is a real problem, considering we (Piwigo Team) have no power over it. I would be happy to discuss a long-term sustainable solution for Piwigo users.
Bye,
For at least three years, the plugin has not been updated and the site is regularly down for days or even weeks at a time. So we have a fundamental problem to solve. I would like Vlad to “transfer” (or “sell” to us, if the cost is reasonable) his plugin to us. We could then distribute it via piwigo.org
The other solution would be for Pigolabs (the company behind Piwigo.com) to finance the development of a new Lightroom plugin. But that would only be if Vlad refuses to transfer his plugin to us.
User "pascalou" has reported:
pascalou wrote:
FYI, I was able to downgrade my LrC to 14.5.1 and reactivate the plugin with my key from last year. Obviously, this is neither satisfactory nor very sustainable, but it works....
Offline
Hi,
I've also been using the LrC Export Plugin for quite some time. It was a key factor in my decision to choose Piwigo as my platform. Without the plugin, there's no convenient way to manage my Piwigo instance, including comments. Since I frequently make adjustments to the images, it's the only practical way to keep track of everything. I also make extensive use of the two-way commenting feature.
While the plugin isn't super fast, it's extremely convenient. The latest available version even survived the recent Piwigo updates, but with each update, I was worried it might stop working.
Since the Alloyphoto website is down, I've also downgraded my LrC to version 14.5.1. This means my key from last year still works. Of course, this isn't a permanent solution, but I can live with it for a while.
I'm pleased with the initiative described above and the prospect of continued support for the export plugin. I would find it very good if Pigolabs took over the plugin so that it could continue to be maintained.
Offline
Today I have been able to talk to a coworker of Vlad. I hope Vlad will get my message and make some feedback.
Offline
P.R. wrote:
The latest available version even survived the recent Piwigo updates, but with each update, I was worried it might stop working.
This is more related to the way we (Piwigo dev team) "don't break anything" on the API, rather than the plugin itself.
What I'm more worried is that the plugin may no longer work with latest versions of Lightroom.
Offline
plg wrote:
This is more related to the way we (Piwigo dev team) "don't break anything" on the API, rather than the plugin itself.
Then I would like to take this opportunity to express my sincere thanks! Well done!
So the functionality is available in the new LrC main version 15, but the plugin switches back to demo mode and deletes the old key. When downgrading to version 14, the key is gone and must be re-entered. The activation apparently runs offline within the plugin, otherwise reactivation would not have been successful in the current situation with the server unavailable.
Why you have to buy some plugins again with every new main version of LrC is a mystery to me. There seem to be alternative options, because not all plugins behave this way.
Ultimately, it comes down to having to enter a new key. Then you should gain a year. Adobe is very cautious in this area within the main versions and focuses strongly on compatibility. This is evidenced by an image conversion plugin from 2013 that still works perfectly for me (further development was discontinued in 2013). But yes, if there are major changes in the area of database fields, it becomes difficult.
I have not noticed any deficiencies in the ongoing operation of the plugin. So I would almost bet that the version as it is now will continue to serve for a few more years – provided that the problem with the key no longer arises.
plg wrote:
Today I have been able to talk to a coworker of Vlad. I hope Vlad will get my message and make some feedback.
That's good news. Let's hope for the best.
Translated with DeepL.com (free version)
Offline