Hello alloyphoto,
I have installed the new version, but it don't work.
Now I can't publish my photos.
Another Error:
"Error code403
Forbidden"
I've send you the log-file
regards
Friesian wrote:
"Error code403
Forbidden"
There seems to be an issue with your Piwigo installation or with the configuration of your HTTP server. The API request returns the HTTP error 403 (Forbidden) when trying to access the following URL: http://diskstation/piwigo/ws.php
If you are unsure about how to fix this I would recommend asking help from the Piwigo team.
Offline
Friesian wrote:
Hello alloyphoto,
I have installed the new version, but it don't work.
Now I can't publish my photos.
Another Error:
"Error code403
Forbidden"
I've send you the log-file
regards
Check the configuration of your service of publication (Lightroom).
Offline
Friesian wrote:
"Error code403
Forbidden"
Another possible cause of this issue is the incorrect or incomplete URL for your Piwigo installation.
Offline
I've checked the configuration, it's all ok.
The Plugin can create categories, so the connection is ok.
But when I try to publish my photos, the error message is coming.
So there is any problem to publish the photos, I think.
Friesian wrote:
I've checked the configuration, it's all ok.
The Plugin can create categories, so the connection is ok.
But when I try to publish my photos, the error message is coming.
So there is any problem to publish the photos, I think.
Before publishing photos the plug-in invokes the pwg.getVersion method. According to your log file, this causes the error. Could someone from the Piwigo team comment on this please? Could it be the getVersion method is not available for some reason?
Last edited by alloyphoto (2011-02-22 20:49:26)
Offline
I reviewed the Piwigo source code and found that getVersion returns a "Forbidden" error if the show_version option in Piwigo configuration is turned off. I believe all you need to do is edit your configuration and enable the "show version" option.
Last edited by alloyphoto (2011-02-22 19:18:30)
Offline
alloyphoto wrote:
I reviewed the Piwigo source code and found that getVersion returns a "Forbidden" error if the show_version option in Piwigo configuration is turned off. I believe all you need to do is edit your configuration and enable the "show version" option.
Where can I change the "show version" option?
Friesian wrote:
Where can I change the "show version" option?
That I don't know. I am hoping someone from the Piwigo team would be able to provide an answer.
Offline
Friesian wrote:
alloyphoto wrote:
I reviewed the Piwigo source code and found that getVersion returns a "Forbidden" error if the show_version option in Piwigo configuration is turned off. I believe all you need to do is edit your configuration and enable the "show version" option.
Where can I change the "show version" option?
In [ Administration >> Plugins >> LocalFiles Editor > Local Configuration ] (first page)
Add this code :
// show_version : shall the version of Piwigo be displayed at the // bottom of each page ? $conf['show_version'] = true;
Offline
alloyphoto wrote:
I added another fix for the issue with creating the album hierarchy when using album sets. Build #381 is available for download.
Thank you very much, I'll try that tomorrow!
Thanks again
Offline
Hum... I think I should modify the code and replace
if ($conf['show_version'])
by
if ($conf['show_version'] or is_admin())
Admins can see the version number in the administration, why couldn't they see it in the web API!
Offline
plg wrote:
Admins can see the version number in the administration, why couldn't they see it in the web API!
Pierrick, I could be wrong, but I think the pwg.getVersion method can be invoked by a non-authenticated user and that was the main reason behind protecting the returned value with a configuration option. If you make it available to authenticated users only, then the checking of the "show version" option can go away.
Last edited by alloyphoto (2011-02-23 00:11:57)
Offline
Pierrick, you are right. If the user is authenticated as admin, then it shouldn't matter how the configuration option is set. Your solution would work perfectly.
Offline
Offline