Hello everyone,
After upgrading to Nextcloud 25 (AIO), Deck sharing options on a user/group etc. are now limited to “can edit” instead of “can edit, can manage, owner”.
I’m wondering if anyone is noticing this same issue.
Thanks in advance guys.
Hello and welcome to the community support forum
According to this Pull Request this should have been fixed in Deck 1.8.3:
nextcloud:master
← small1:fixcomponentrenaming
opened 02:53PM - 12 Dec 22 UTC
Signed-off-by: Johan Bernhardsson <johan.bernhardsson@redpill-linpro.com>
* R… esolves: #4215
* Target version: master
### Summary
Fixes component renaming so that acl works on shares
### Checklist
- [x] Code is properly formatted
- [x] Sign-off message is added to all commits
- [x] Tests (unit, integration, api and/or acceptance) are included
- [x] Documentation (manuals or wiki) has been updated or is not required
At least the corresponding issue seems to be exactly what you described:
opened 04:28PM - 18 Nov 22 UTC
closed 09:55AM - 19 Dec 22 UTC
bug
good first issue
1. to develop
high
bug: regression
<!--
Thanks for reporting issues back!
Guidelines for submitting issues:
… * Please search the existing issues first, it's likely that your issue was already reported or even fixed.
* SECURITY: Report any potential security bug to us via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/) instead of filing an issue in our bug tracker.
* The issues in other components should be reported in their respective repositories: You will find them in our GitHub Organization (https://github.com/nextcloud/)
* You can also use the Issue Template app to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Choose a deck board you've shared with other users
2. Click on three dot menu > board details
3. In the right menu bar, click on the three dots next to a user/group name
**Expected behavior**
You should see a menu with can share / manage / owner / delete

**Actual behavior**
The only option displayed is delete

**Screenshots**
If applicable, add screenshots to help explain your problem.
**Client details:**
firefox latest version / windows 11
<details>
<summary>Server details: c.nc.c</summary>
<!--
You can use the Issue Template application to prefill most of the required information: https://apps.nextcloud.com/apps/issuetemplate
-->
**Operating system**:
**Web server:**
**Database:**
**PHP version:**
**Nextcloud version:** (see Nextcloud admin page)
**Where did you install Nextcloud from:**
**Signing status:**
```
Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.
```
**List of activated apps:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
```
**Nextcloud configuration:**
```
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
```
**Are you using an external user-backend, if yes which one:** LDAP/ActiveDirectory/Webdav/...
</details>
<details>
<summary>Logs</summary>
#### Nextcloud log (data/nextcloud.log)
```
Insert your Nextcloud log here
```
#### Browser log
```
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
```
</details>
So I assume: Just be a little bit patient until the release rolls out to you
Thanks @stefan-niedermann , I just checked and is now fixed!