@girish @nebulon - Some additional digging, and I am wondering if this could be the cause. I've tested this at the User level, and the User Group level for the same page.

The below is from the Configuration Settings of the Dokuwiki (domain replaced with example):

https://www.example.com/grp/vr_team_lead?do=admin&page=config

The plugin»authldap»usertree is filled in, but the plugin»authldap»grouptree field is empty.

Screen Shot 2023-03-20 at 2.35.20 AM.png

Similarly, the plugin»authldap»userfilter is filled in, but plugin»authldap»groupfilter is empty.

Screen Shot 2023-03-20 at 2.35.34 AM.png

For the User, it works. For the User Group, no matter what I do, it does not. Could this be why I was able to get the ACL to work at the User level, but not the User Group level?

According to the threads at Dokuwiki forum, andi the developer has said:

Yes. The ldap plugin uses the grouptree and groupfilter settings to fetch the group memberships of users.

I also did a check at:

https://www.example.com/grp/vr_team_lead&doku.php?do=check

And from what I can see, it shows that I'm logged in as the correct User, but the User's Group does not correspond to the group defined on the LDAP server. Just that I'm part of the group "user."

Screen Shot 2023-03-20 at 2.46.39 AM.png

Let me know if you guys would like to see a screenshot of my ACL setup if needed.

Thank you!

@girish I haven't yet found out about the PHP compatibility of bootstrap3.
Were you able to track down the packaging issue?

Fixed in latest package.

This is fixed in the latest package.

Just looked into this issue again with a fresh mind. I think it's not solvable without support in the platform to backup directories outside of /app/data (or alternately, we have to install dokuwiki in /app/data )

@neki it seems for this particular template/theme the issue tracker is at https://github.com/giterlizzi/dokuwiki-template-bootstrap3/issues

@ntnsndr Not sure how entrenched you are - but BookStack? Sorry, not a DokuWiki answer but worth a look if you haven't yet.

@roru2k20 To persist changes, please add the config inside /app/data/conf/local.php instead.

<?php $conf['superuser'] = ("girish");

Thanks for the heads up and the workaround!

The last update explicitly removed the admin status propagation from Cloudron user accounts to the app. This is done to unify how user accounts get permissions assigned within all apps. The idea is, that the Cloudron admin status is not carried over to apps, since apps have too many different concepts what an admin is and is not.

I guess there is no good way without requiring manual permission changes to move to this new understanding what admin means on Cloudron.