Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trace #2932

Closed
zounp opened this issue Dec 4, 2019 · 6 comments
Closed

Trace #2932

zounp opened this issue Dec 4, 2019 · 6 comments

Comments

@zounp
Copy link

zounp commented Dec 4, 2019

I tried to hide the "Media Manager" link and trace when not logged in. I could not find a solution.
I also tried the "Other actions (comma separated)" field but with no succes.

It would be nice if every object, like trace, the "Media Manager" link, the, backlink & back to top ..., object / items and ... except of course "Log in" could be hidden
Configurable in the Configuration Manager under "disableactions -> Disable DokuWiki actions'

Also it would be nice if there are two "disableactions -> Disable DokuWiki actions' blocks. One when not logged in and one when logged in. In this way Dokuwiki is applicable in more use cases.
Thanks.

@phy25
Copy link
Collaborator

phy25 commented Dec 4, 2019

It would be nice if every object, like trace, the "Media Manager" link, the, backlink & back to top ..., object / items and ... except of course "Log in" could be hidden

I don't think it's possible in core to hide these based on login status. I am not sure if a plugin is able to hide them all, but some frontend trick can do it as well (output CSS that hides these links based on login status).

Meantime, I don't think this should be in core. (Edit: I am not sure if this can be all decided by template?)

@zounp
Copy link
Author

zounp commented Dec 13, 2019

I think it should be in core as are all the other options in the Configuration Manager under "disableactions. That makes Dokuwiki more powerful / universal and it feels logical to me if they where hideable .
Also in if they can be turned off, at least for users not logged in, it gives the site owner the choice, he / she can decide what is shown and what not.

Maybe a frontend trick can that outputs CSS that hides these links based on login status can work. However not all users of Dokuwiki have enough knowledge of the code / structure of Dokuwiki and / or CSS to accomplish that.

Like me, their main objective is making a nice wiki, website, with Dokuwiki. I like to use Dokuwiki as much as I can for websites since I am very, very productive with Dokuwiki. There is not much of a learning curve, like Wordpress for instance, and far most of the things I want to accomplish work (almost) out of the box. That is very very good !!!
Thanks for all the effort.

@phy25
Copy link
Collaborator

phy25 commented Dec 13, 2019

I want to stress that my point is on login-status based.

Also, I believe it's doable using a plugin (see the tag on this issue), but I mentioned CSS solution because I was not sure if a plugin can inject at PHP level to control this based on login status. I think about this again and maybe it's doable through hooks by a plugin as well.

@zounp
Copy link
Author

zounp commented Dec 17, 2019

Login-status based would be fine. The main objective is to hide objects that readers do not need, objects that distract (in the view of the author of the wiki / website). So all objects on in when logged in and every object selectable when not logged in would also be nice and flexible

@vaniwiki
Copy link
Contributor

vaniwiki commented Jul 13, 2021

https://dokuwiki.org/plugin:denyactions and/or https://www.dokuwiki.org/plugin:tplmod can achieve something like that. :)

Non-logged in users only have "back to top" and "log in" showing on my site.

@vaniwiki
Copy link
Contributor

vaniwiki commented Jul 17, 2021

Relevant settings from Tplmod plugin:

Screenshot 2021-07-17 at 10 26 56 AM

Update: I realised the relevant setting was found in the ComboStrap template: Enable Private Toolbar. 🥇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants