Hide sidebar blocks. - Githubissues

andersonbrantes commented 5 years ago

Hello, you are doing a great job with this tool. Is there a configuration to hide the “recent activity”, “recently updated pages” and “my recently viewed” sidebar blocks?

ssddanbrown commented 5 years ago

Hi @andersonbrantes, Hiding such items is not supported via UI options or anything like that. If you are handy with CSS it's possible to hide these with CSS rules, placed in the Custom HTML head content setting.

If you can confirm the view you're looking at (Do you have a custom homepage set?) I could help with those rules.

andersonbrantes commented 5 years ago

Ok @ssddanbrown , I will try to do it with CSS... I didn't know the custom homepage feature, that's a great idea. I am using BookStack for a Wiki that has private and public documents. The main idea is only users with private permissions could see these sidebar blocks(recent activity, recently updated pages, my recently viewed). Do you think it is possible with the custom pages?

unknowndomain commented 5 years ago

@andersonbrantes something like this is what I use: <style>#sidebar { display: none; } [expand-toggle] { visibility: hidden; }</style> I put this in the page content for our homepage rather than in the custom HTML header where you'd only want: <style>#sidebar { display: none; }</style>

andersonbrantes commented 5 years ago

Hi @unknowndomain... I could use something like that, but, I want this rule only for public pages. This is tricky to do with CSS without a specific identifier(Id or Class) for this. Maybe I can do it with Javascript. But, the best way would be on the server side, I think.

There is a similar issue to what I want to do: #1319

unknowndomain commented 5 years ago

I agree, another solution which would be helpful generally is that the body tag have a few classes on it to help you figure out what kind of page you are on, i.e. <body class="shelf"> or <body class="page public"> or <body class="page private">

That way you could write CSS selectors like body.private or body.page.public.

This is how WordPress handles the issue.

ayyilmaz commented 4 years ago

I think hiding recent activity block from public is important in terms of security at some cases. Some users who has different roles should see this.

HAMFEM commented 4 years ago

I think hiding recent activity block from public is important in terms of security at some cases. Some users who has different roles should see this.

I fully agree. Pages hidden to some roles appear in the recently changed area to all roles, and they can access it by just clicking the link. Hiding the side bar is not a good solution, as it makes the navigation less practical in the book/chapter level.

haveyougotanypets commented 4 years ago

On the custom css route it would be helpful if IDs or better still class names set for the entire block section so they can be hidden individually. Currently they seem to be applied somewhat inconsistently.

For example i can set in Custom HTML Head Content:

<style>
#recent-activity {display:none;}
</style>

and it removes the whole block. But if i do:

<style>
#recently-updated-pages {display:none;}
</style>

it removes the block contents but not the header because the id tag has been applied at the sub block of the full recently-updated-pages block content.

If the IDs were set on the top block element for each section that would be helpful fix.

Lastly I would think about using classes rather than IDs as at some point you can guarantee someone is going to want to use the same block twice on a page in a customised theme for whatever reason and if you use IDs it will be invalid html and you've got yourself another support ticket.

Lovely looking wiki so far, looking forward to seeing it improve over time!

purpletreesoft commented 4 years ago

Any progress on this? This is an important feature IMHO. Right sidebar, history, and if possible top-right header content should be hidden from public.

SloCompTech commented 3 years ago

Hi, I'm looking forward to see this feature. I'm looking for a way to hide recent activity, especially usernames for guest viewers. Maybe this could be simply implemented to display Someone instead of real username when guest loads the page ?

kulpin74 commented 3 years ago

It's very important feature. In our case we send guest links on specified documents, but all guests can see all documents in Recent activity. Maybe this can be solved through User rights?

SloCompTech commented 3 years ago

Yes, possible solution would be, to replace username with Someone and disable link to user based on user role or permission.

ssddanbrown commented 3 years ago

It's very important feature. In our case we send guest links on specified documents, but all guests can see all documents in Recent activity. Maybe this can be solved through User rights?

Yes, Users (Including guests) should only be able to see the activity for items they have access to. By default the guest user can view everything but this is configurable by alterting their role.

kulpin74 commented 3 years ago

It's very important feature. In our case we send guest links on specified documents, but all guests can see all documents in Recent activity. Maybe this can be solved through User rights?

Yes, Users (Including guests) should only be able to see the activity for items they have access to. By default the guest user can view everything but this is configurable by alterting their role.

If this could be the role "List chapter, books, shelf" it would be great. We could send a link for book/chapter but if we dont't give that role - guests will not be able to list anothers books/chapters. This role can affect showing recent activity too. And of course Guests mustn't be able to view User name or another private information.

sarah-arrrgh commented 2 years ago

I've worked around this for now by hiding the sidebar things we don't need in

BookStackApp / BookStack

Hide sidebar blocks. #1291