Configure Cross-Site Display Archives

Select Site URL Containing SharePoint List

Return to Toolpane Configuration Settings

Each instance of Cross Site Display can display one SharePoint list or library.

Enter the site URL that contains the SharePoint list or library to be displayed. Click the View Lists and Libraries button to load all lists and libraries from the specified site. Site URLs can be absolute (http://servername/site) or relative (./site).

NOTE: Bamboo recommends using a relative URL if the Web application has multiple access points using Alternative Access Mappings (AAM) or if the Web Part will be saved as part of a site template.

Select a default view for Cross Site

Return to Toolpane Configuration Settings

Select the view to display by default for the list or library. Cross Site Display will automatically discover the default view for the list or library. You can restrict Cross Site Display to display only this view by disabling the View drop-down menu in the toolbar settings.

Notice in this example a Task list has been chosen and this type of list typically has multiple views. You can select the view called “My Tasks” and whomever opens the page where the web part has been placed will see tasks assigned to them in the view. If you were to choose the “Due Today” view, then only tasks that are due now will show up in the view on the page.

Select a List or Library for Cross Site

Return to Toolpane Configuration Settings

Each instance of Cross Site Display can display one SharePoint list or library. See the table below containing the instructions for the lists, libraries, and views that can be displayed in the Cross-Site Display Web Part.

To select a list or library to display in an instance of Cross Site Display:

Step	Action
1.	Click the View Lists and Libraries button to populate the Available Lists and Libraries drop-down list.
2.	In the SharePoint List or Library drop-down list, select the list or library to display in the Cross-Site Display Web Part

Top

The following lists, libraries, and views can be displayed in Cross Site Display:

Libraries		Views
Document Library		Standard Views
Form Library		Calendar Views
Picture Library		Gantt Views
Wiki Page Library		Survey List Views
Lists		Overview
Announcements		All Responses
Calendar		Graphical Summary
Contacts		Discussion Board Views
Custom Lists		Subject View
Discussion Board		Flat View
Issue Tracking		Threaded View
Links		Picture Library Views
Project Tasks		Detailed View
Survey		Filmstrip View
		Thumbnail View

Top

Localize Bamboo Web Parts for your Language

Overview of the localization process for Bamboo Products

Applies to:

All Bamboo Web Part components
Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007
SharePoint Foundation 2010 and SharePoint Server 2010
SharePoint Foundation 2013 and SharePoint Server 2013

Bamboo products can be configured to display product menus, user interface text, and settings in your local language. You can also customize the default text provided with the product. To change the language or text a product displays, perform the steps described in this page. Click a link below for detailed information about each step.

About the Language Files
Editing Text in Language Files
Selecting a New Language File for a Product

Top

About the Language Files

There are four language files included with Bamboo products. Their name and location may differ by product.

Setting	Older Products	Newer Products
Web Part Language Settings		Newer products will show the language choices in the Web Part settings using the abbreviated [language]-[COUNTRY] format (e.g. “en-US”)
Language File Names	1033.English.xml (the default) 1031.German.xml 1034.Spanish.xml 1036.French.xml	Bamboo.[Product].en-US.resx (the default) Bamboo.[Product].de-DE.resx Bamboo.[Product].es-ES.resx Bamboo.[Product].fr-FR.resx
Language File Location	These files are located in the wpresources folder. This folder and its associated language files may be located under one of the following paths on each SharePoint server: servernamedriveInetpubwwwrootwss VirtualDirectoriesportwpresources[Product] servernamedriveInetpubwwwrootwss VirtualDirectoriesportwpresources[Product] LanguageFiles servernamedriveProgram FilesCommon FilesMicrosoft Sharedweb server extensionswpresources[Product]	Depending on your version of SharePoint, your localization files may be found in the following locations. servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions15CONFIGAdminResources (SharePoint 2013) servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions14CONFIGAdminResources (SharePoint 2010)

Setting

Older Products

Newer Products

Web Part Language Settings

Newer products will show the language choices in the Web Part settings using the abbreviated [language]-[COUNTRY] format (e.g. “en-US”)

Language File Names

1033.English.xml (the default)
1031.German.xml
1034.Spanish.xml
1036.French.xml

Bamboo.[Product].en-US.resx (the default)
Bamboo.[Product].de-DE.resx
Bamboo.[Product].es-ES.resx
Bamboo.[Product].fr-FR.resx

Language File Location

These files are located in the wpresources folder. This folder and its associated language files may be located under one of the following paths on each SharePoint server:

servernamedriveInetpubwwwrootwss
VirtualDirectoriesportwpresources[Product]
servernamedriveInetpubwwwrootwss
VirtualDirectoriesportwpresources[Product] LanguageFiles
servernamedriveProgram FilesCommon FilesMicrosoft Sharedweb server extensionswpresources[Product]

Depending on your version of SharePoint, your localization files may be found in the following locations.

servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions15CONFIGAdminResources (SharePoint 2013)
servernamedriveProgram FilesCommon Filesmicrosoft sharedWeb Server Extensions14CONFIGAdminResources (SharePoint 2010)

The German, Spanish and French files have not yet been translated; although the file name suggests otherwise, their content is English. Edit these files to provide your own text or translation of the product user interface and settings.

IMPORTANT: If you do not rename the files you modify, your customizations will be overwritten when you upgrade to a new Bamboo product release.

To make sure that your customizations do not get overwritten when you upgrade the product, follow these steps:

Step	Action
1.	Copy the default file for the appropriate language and rename the copy. For example, you might save a localized French language file as CompanyName.1036.French.xml or Copy.Bamboo.ProductName.fr-FR.resx. NOTE: When you next upgrade the product, the default file (i.e., 1036.French.xml) will be overwritten with the new version. Your file will not. You can use any file name, as long as the file extension is .xml (or .resx for newer products). To create language files for languages other than German, English, Spanish, or French, copy one of the existing language files and rename it. Then edit the file to provide your own translation.
2.	When you upgrade your Bamboo product, the installation/setup application will not remove or overwrite language files you created if you saved them with a name other than the default. However, product upgrades may require that you merge new resource strings for the new product release. NOTE: If you forget to add new resource strings to your custom language file, you may see strange things in the user interface. The product will display missing resource string IDs instead of text. Copy these new resource string IDs from a default language file to your custom file and make any desired translations.

Step

Action

Copy the default file for the appropriate language and rename the copy. For example, you might save a localized French language file as CompanyName.1036.French.xml or Copy.Bamboo.ProductName.fr-FR.resx.

NOTE: When you next upgrade the product, the default file (i.e., 1036.French.xml) will be overwritten with the new version. Your file will not. You can use any file name, as long as the file extension is .xml (or .resx for newer products).

To create language files for languages other than German, English, Spanish, or French, copy one of the existing language files and rename it. Then edit the file to provide your own translation.

When you upgrade your Bamboo product, the installation/setup application will not remove or overwrite language files you created if you saved them with a name other than the default. However, product upgrades may require that you merge new resource strings for the new product release.

NOTE: If you forget to add new resource strings to your custom language file, you may see strange things in the user interface. The product will display missing resource string IDs instead of text.

Copy these new resource string IDs from a default language file to your custom file and make any desired translations.

Top

Editing Text in Language Files

IMPORTANT: Before making any changes to any file, back up your original file and put it in a safe place.

To change text in a language file, follow these steps:

Step	Action
1.	Open the language file in a text editor and locate the text you want to change.
2.	Edit the text between the <resource></resource> tags but do not edit the tags. NOTE: Do NOT modify the resource id value. Modify only the text between the <resource></resource> tags. If you want to remove text completely, delete only the text; do not delete the <resource> entry from the file, or the product interface will display an error message. In the example below, the text you can modify is highlighted in gray.
3.	When you are finished with your changes, save the file and copy it to the appropriate resources folder on all Web front-end servers in your SharePoint farm.
4.	Follow the instructions below to select your new language file in the product settings.

Top

Selecting a New Language File for a Product

The instructions below for changing language file settings apply to Bamboo products with settings configured in the Web Part tool pane or Web Part Settings pop-up page. If you have multiple instances of a product in your portal, you must make the same change for each instance that requires the change.

Change the Language Settings in the Web Part Tool Pane:

Step	Action
1.	Click the edit drop-down menu on the Web Part title bar and select Edit Web Part (or Modify Shared Web Part if you are using SharePoint 2007). See the example from the Group Email Web Part.
2.	In the Language Settings section of the Web Part tool pane, select the language file you want to use. See the example from the Group Email Web Part. If you have created a new file (i.e., Copy.Bamboo.ProductName.fr-FR.resx), it should appear in the list as a valid selection.
3.	Click Apply and then OK in the Web Part tool pane to apply your changes.

Change the Language Settings in the Web Part Settings Pop-up Page:

Step	Action
1.	Click the edit drop-down menu on the Web Part title bar and select Edit Web Part (or Modify Shared Web Part if you are using SharePoint 2007).
2.	Click the [Product] Settings button in the Web Part tool pane.
3.	Click Language Settings in the Web Part Settings page and select the language file you want to use. If your product does not have a Language Settings section, look for the Select a Language drop-down list in General Settings instead. If you have created a new language file (i.e., Copy.Bamboo.ProductName.fr-FR.resx), it should appear in the list as a valid selection.
4.	Click the Save & Close button to save the Web Part settings.
5.	Click Apply and then OK in the Web Part tool pane to apply your changes.

How to Display Multiple Lists or Libraries on a Page

To display multiple lists or libraries on a page, add multiple instances of Cross Site Display to a Web Part page.

Each Web Part instance is configured individually and can display a different list or library.

Configure Cross SIte to Use a Custom Login Account so Users Can View Data

Return to Toolpane Configuration Settings

Cross Site Display uses standard SharePoint security trimming to display items from a list or library. If the currently logged-in user does not have access to view a list or item, it will not be displayed in Cross Site Display .

However, if you would like users to be able to view items in a list even if they do not normally have permission to do so, you can configure a Custom Login Account for the Cross Site Display to use so as to display items with read-only access. The Custom Login Account must have at least View permission on all items in the list or library.

Note: The Custom Login Account is used to display SharePoint items only. If the user attempts to perform other actions on the list or item, Cross Site Display will use the identity of the current user instead of the Custom Login Account.

Configure Full Toolbar Settings

Return to Toolpane Configuration Settings

By default, Cross Site Display will display the full SharePoint toolbar at the top of the list or library. The toolbar includes access to new item actions, the Actions menu, the Settings menu, and the View drop-down list, if they are available to the current user. To hide these options for all users, uncheck Display Full Toolbar.

To disable the ability for users to change the view displayed in Cross Site Display, uncheck the option Display Select View Menu. This will allow users to still access toolbar options, but restrict their actions to the view defined by the administrator.

Step

Action

Result

Display Full Toolbar

By default, Cross Site Display will display the full SharePoint toolbar at the top of the list or library. The toolbar includes access to new item actions, the Actions menu, the Settings menu, and the View drop-down list, if they are available to the currently logged-in user. To hide these options for all users, uncheck Display Full Toolbar.

Display Select View Menu

On the right side of the web part view that users will see is the drop down selector that a user can pick to see the various views in a list.

If you prefer not to show this selector, you can disable it by unchecking this box. Users who do not have the permission to create or edit views will not see the Modify this View or Create View options in the menu.