Admin tool doesn't refresh to reflect repository changes

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Lane
Posts: 85
Joined: Thu Oct 26, 2006 10:58 am

Admin tool doesn't refresh to reflect repository changes

Post by Lane » Thu Jan 08, 2009 4:32 pm

I am logged into the admin tool, viewing a repository that has folder security enabled.

Another user performs a branch within the repository. But I cannot see the new folder, even after refreshing. The new branch doesn't show up in the Obliterate page either.

If I log in with a different browser, I can see it fine.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Admin tool doesn't refresh to reflect repository changes

Post by lbauer » Fri Jan 09, 2009 2:10 pm

A branch would not show up under Obliterate unless it had been deleted.

When you say you used a different browser, do you mean a different type of browser, or another instance of the same browser? Did you try deleting your browser cache?
Linda Bauer
SourceGear
Technical Support Manager

Lane
Posts: 85
Joined: Thu Oct 26, 2006 10:58 am

Re: Admin tool doesn't refresh to reflect repository changes

Post by Lane » Fri Jan 09, 2009 3:47 pm

A branch would not show up under Obliterate unless it had been deleted.
I'm talking about the list of folders on the left that appears both on the Obliterate screen and on the Folder Security screen.
When you say you used a different browser, do you mean a different type of browser, or another instance of the same browser? Did you try deleting your browser cache?
I was using FF and I switched to IE. The new folder showed up in IE. Yes, after clearing the browser cache it worked, but is that really necessary? How often does it check to see if something has changed?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Admin tool doesn't refresh to reflect repository changes

Post by lbauer » Tue Jan 13, 2009 3:23 pm

I believe we re-serve up the page every time the browser requests it, but we may be caching some tree information in the browser session for speed. If you close and reopen the browser, the page should be updated.
Linda Bauer
SourceGear
Technical Support Manager

Post Reply