thankyousteve.org

protected override void OnInit(EventArgs e)
{
    btnSearch.InnerHtml = getDictionaryItem("cwsSearch");
}

The helper-method getDictionaryItem() takes over all required tasks related to the communication with the Umbraco-API:

private string getDictionaryItem(string key)
{
    string result = umbraco.library.GetDictionaryItem(key);
    if (String.IsNullOrEmpty(result)) result = "[#" + key + "]";
    return result;
}

1. Open SQL-Server Management Studio 2008 and connect to desired database server.
2. Menu: File > Open > File... > select your backup script (*.sql)
3. In the opened window, check to see if your script is running as the desired database. The script should begin with:

   USE
   [MySqlDatabase]
   GO
   

4. If this is not the case, edit the script.
5. Run script with F5 > check to see if the script was run successfully > Finish.

Management Studio 2008 information: http://technet.microsoft.com/en-us/library/ms365247.aspx

Download-link: http://go.microsoft.com/fwlink/?LinkId=144346

The following steps are required (Management console needs to be installed):

1. Connect to the database.
2. Expand the folder "databases" and select the desired database.
3. In the context menu [right-click] open > Tasks > generate scripts...
4. Confirm the script assistant with > next
5. Select database > next
6. Use the following configuration:
   • Drop as Skript: True
   • Include 'IF NOT EXISTS': True
   • Create script for Server: SQL Server 2005
   • Create script for data: True
   • Then click > next
7. Choose object type: select in table > next
8. Select tables: Select all > next
9. Output options: select write script in file > choose meaningful filename > next > Finish
10. After successful generation > close the assistant

If you have (like me) been wondering why accessing data elements of the current document would always return empty values, you should take a look at the following XSLT advice:

When using the toolbar to insert a data element (here: 'article photo'), following code is added:

<xsl:value-of select="data [@alias = 'articlePhoto']"/>

This code is correct if it is part of an enumeration loop. Without this reference to the current item, the code snippet has to read:

<xsl:value-of select="$currentPage/data [@alias = 'articlePhoto']"/>

Furthermore, the variable $currentPage in the XSLT-script needs to be initialized correctly:

<xsl:param name="currentPage"/>

HTH

After installing Runway along with Umbraco, one might realise that the navigation icons in the Lightbox viewer go missing. Reason for this is the associated XSLT-script "galleryListPhotos.xslt". The terms "runway" and "runway-modules" were introduced only shortly before release, causing some minor inconsistencies.

To show the icons correctly, a fix for XSLT-script is needed. Instead of:

$(function() {
   $('.nitroGallery a:rel:lightbox').lightBox({

The correct version is:

$(function() {
   $('.runwayGallery a:rel:lightbox').lightBox({

This should deal with the issue.

• param="[$item]"

• param="[#item]"

• param="const"

Calling macro within anchor-tag's href-attribute

The problem was solved by changing the outer " to '

<a href='<umbraco:Macro Alias="GetNiceUrl" sourceUrl="[#banner1Link]" runat="server"/>'>

For more information visit Umbraco-Books:
Macro parameter syntax

For redirecting, two possibilities exist with ASP.NET:

• Redirect on the HTTP protocol layer
• Server redirect

The second approach does not work with the method server.transfer("url") because in Umbraco, the addresses of the target site are virtual ASPX-pages that are not available in the physical server directory.

Redirects have to be done with the method response.redirect("url").

It is simple to create a multilingual website using Umbraco together with Warren Buckley's Creative Website Starter 2.0. All the required steps will be explained here:

• Different approaches with Umbraco
• Practical page structure
• Necessary add-ons
• Program-controlled integration of a language
• Navigating between available languages

No umlauts in page headlines

If CWS2 is used to develop a German website, the umlauts in the page headlines go missing. Reason for this is the technology used for displaying any desired font with the sIFR JavaScript Plugin.

sIFR is short for Scalable Inman Flash Replacement. For displaying a letter, a matching vector graphic is loaded from an Adobe Flash file. The file CWS2 uses is called Amasis_MT.swf. However, this file does not contain any German umlauts. To fix this, a different Flash file must be used.

The online generator sIFR Generator can be used to create a suitable Flash file. In order to do this, you must choose a TrueType font from your computer and upload it to the generator. Then choose the sIFR 3 r436 Version and continue by selecting full character set of the font file, so that the umlauts are included. The Flash file can now be downloaded and used to replace the old Amasis_MT.swf file under the same name.

Other very useful information on sIFR can be found here:

• sIFR 3 - Documentation & FAQ
• sIFRvault - font type resource
• sIFR Tutorial: Use Your Own Fonts