What is the error you are getting?  If I had to guess, you haven't recompiled the project, which is necessary when adding server controls to an ASP.Net project.

Hi Sumeet,

You can get rid of the extraneous 'Page X of Y' by adding the following lines to your WebLinkStyles.css:

#TheFolderTree .BrowserFooter {
    display: none;
}

Thanks for pointing that out!

As far as the syncing, I see that Wes got you off to a really great start in this thread.  Your reseller may be able to help you get it even closer to the behavior you want.  My understanding is that you want to add code so that when you open a folder in the right pane, the folder tree will expand and show the contents of that folder.  Is that correct?

[edit:] I've added a solution for the synchronization of the controls below.  In addition, here's a suggested update for WL9 to the HTML in Wes's solution, so you can get the new arrow styling/behavior (and not bombard the city of Aiken's server ;]).  In Browse.aspx, where Wes has:

<a title="Hide" id="__FoldersExpando" class="FolderExpandoClass" href="javascript:void(0);" onclick="ToggleSectionVis('__FoldersDataSection','__FoldersExpando');">
<img src="https://www.cityofaikensc.gov/WebLink8/images/chevronup.gif" class="FolderSectionExpando">
<span class="FolderSectionTitleText">Folders</span>
</a>

You might want:

<a title="Hide" id="__FoldersExpando" class="FolderExpandoClass" href="javascript:void(0);" onclick="ToggleSectionVis('__FoldersDataSection','__FoldersExpando');" aria-haspopup="true" aria-expanded="true"><img src="images/new_sprite/upArrowCollapse.png" class="FolderSectionExpando"><span class="FolderSectionTitleText">Folders</span></a>

(Make sure there's no whitespace between the elements!)

Hi Avri,

I've spoken with development and to fix the issue of the selected folder from the right pane getting added into the folder tree as a duplicate folder, then please change the modified code suggested above from

If EntryIDToOpen <> args.SelectedEntryID Then
    ' Open a shortcut -- this function retrieves the path to the folder
    SetBrowserStartID(EntryIDToOpen)
    TheFolderTree.OpenFolder(EntryIDToOpen)
Else
    ' Open a child of the current folder -- the path is already known
    SetBrowserStartID(EntryIDToOpen)
    TheFolderTree.OpenFolder(EntryIDToOpen)
    TheFolderTree.OpenChildOfCurrentFolder(EntryIDToOpen, args.SelectedEntryName, args.SelectedEntryFlags, True)
End If

to

If EntryIDToOpen <> args.SelectedEntryID Then
    ' Open a shortcut -- this function retrieves the path to the folder
    SetBrowserStartID(EntryIDToOpen)
    TheFolderTree.OpenFolder(EntryIDToOpen)
Else
    ' Open a child of the current folder -- the path is already known
    SetBrowserStartID(EntryIDToOpen)
    TheFolderTree.OpenChildOfCurrentFolder(EntryIDToOpen, args.SelectedEntryName, args.SelectedEntryFlags, True)
End If

Basically, just remove the line "TheFolderTree.OpenFolder(EntryIDToOpen)" from the "Else" section. After you recompile the project, you should notice that the folder tree in WebLink 9 will now behave the same as the folder tree in other client side applications like the desktop Client and Web Access. When you select a folder from the right pane, the folder level that the selected folder is a part of will be expanded in the tree and the selected folder will be indicated as being opened. However, the selected folder itself will not be automatically expanded in the tree.

With the slight change to Melanie's suggestion, here is what you see in WebLink 9

And here is what you see in the desktop Client

In both cases, after I logged into the repository, I went into the right pane and I selected the "_Cases" folder followed by the "160000-169999" folder. Both applications behave the same in that the folder tree on the left will expand up to the same folder level that "160000-169999" is located at and indicate that folder being opened, but it does not automatically expand to show the subfolders underneath "160000-169999" in the folder tree.

Note that if what you are wanting is to also auto-expand the selected folder from the right in the folder tree on the left, then we can look into that as an enhancement for a future release of WebLink. However, the suggestions by Wes from this previous thread and Melanie in this thread (with the slight change) will get you the default folder tree behavior found in our other client side applications.