Return to Jive Software

Skip navigation
Up to Discussions in Support
1,478 Views 2 Replies Last post: Mar 4, 2009 3:44 PM by Will RSS
MarkMorley Novice
MarkMorley
1 posts since
Feb 11, 2009
Currently Being Moderated

Feb 11, 2009 4:34 AM

Glimpsed something I don't think I should have

This could be a potential bug.

If you hovering over someone's name to see what recent content they have produced and you don't have the required permissions to see that content a list still displays momentarily - just long enough to read some of it - then the system must identify that you haven't got permissions and the list disappears.

 

Corollary:

If you go to look at the 'stuff' that this person has created (which you don't have permissions to access) and they have created a lot of 'stuff' then you get to see that there are several pages of person's name has not created any whatever (blog posts for example). This is a bit of a give away that they have actually created something, and lots of it. It would see better just to have one page that says this.

 

v.2.5.4

Tags: permissions, permission, bug, recent_content
Will Jive Employee
Will
4,583 posts since
Nov 2, 2004
Currently Being Moderated
Mar 4, 2009 8:05 AM in response to: MarkMorley
Re: Glimpsed something I don't think I should have

Thanks for reporting this. I will test it locally and see if I can reproduce, and let you know what the results are.

 

I believe the blog post count one is known, but I will look into that one as well

Will Jive Employee
Will
4,583 posts since
Nov 2, 2004
Currently Being Moderated
Mar 4, 2009 3:44 PM in response to: MarkMorley
Re: Glimpsed something I don't think I should have

Hi,

 

I was able to reproduce the second issue with the blogs, and have logged a product bug for it, but I was not able to reproduce flash of non-authorized content. Would you be able to screen capture this (using something like Jing )?

 

Thanks,

More Like This

  • Retrieving data ...

Bookmarked By (0)

Case Product Issues

Loading Jira issues

Loading related product issues for this case
To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.