Support for the entire Community plug-in functionality

[eTaurus]

Piwigo 13.6.0 (Docker container by LinuxServer.io)
Nginx as reverse proxy
Community plug-in 12.c
Piwigo NG 2.0.1-beta (Android)

With the above setup users without Webmaster status or Admins rights cannot see empty albums which they are allowed to see, even those they are allowed to upload pictures to. This makes them practically unable to upload pictures to an empty album.
There are no problems when using a browser.
When there is an album containing at least one picture the album becomes visible but users are not able to create a sub-album.
The upload functionality is working without problems otherwise.

It would be nice if the app would support the functionality of the Community plug-in in its entirety.

[remi-martin]

Hi, thanks for your feedback.

For now, the API does not provides the list of roles and permissions of a community user, so we can't know if they have access to certain features suchs as creating or editing an album, ...

Concerning album visibility, I assume it is a bug.

[eTaurus]

For now, the API does not provides the list of roles and permissions of a community user, so we can't know if they have access to certain features suchs as creating or editing an album, ...

Where should I post a feature request for this? Piwigo or the Community plugin?

[remi-martin]

I'll ask the developpers

[remi-martin]

They are aware of this issue. If you want to post a feature request, you can do it on the Community plugin's repository.

[remi-martin]

With 2.2.3, community users can now edit their own photos, but only from the albums they can access.

The best behavior we are working on would be to allow community users to have all actions (edit, move, delete, ...) on the photos they uploaded, even if they have been moved since.

2.2.3 will release soon.