Hmm no one?  Guess I need to refresh my XSL and see why it's not working on a child page.  

Where are these starter kit skins downloaded from?  

Hi Nick.

Could you provide us with the code from the XSLT macro you have inserted. Maybe we can see what's going on then :)

/Kim A

Ah good point, I didn't think of it since it was in the skin already, not custom. 

<xsl:variable name="sliderNode" select="$currentPage/parent::*/child::*[@level=1]"/>

 <div id="slider">
    <div id="imageSlider">
      <xsl:for-each select="$sliderNode/child::umediaSlider">
           <div class="imageSlide">
              <div class="imageSliderInfo">
                  <h2> <xsl:value-of select="@nodeName"/></h2>
                  <xsl:value-of select="teaserText" disable-output-escaping="yes"/>
                </div>
                <div class="imageSliderImage">
                  <img src="{umbracoFile}" width="500" height="320" />
                </div>
            </div>
       
      </xsl:for-each>
   </div>
</div>

Hmm...okay.

I haven't seen the sructure in the content tree, but I guess that there are some nodes under the homepage-node with a document type of umediaSlider.

If that's correct, I think you can just chage the variable to this:

<xsl:variable name="sliderNode" select="$currentPage/ancestor-or-self::*[@level=1]"/>

Does that make any difference.

/Kim A

No that didn't work.  broke for both.

It's the straight vanilla Business site quick install that comes with 4.6.1.  I was surprised to find out the templates didn't actually use the macros's but had the html hard codeded in them.  The uslider node doesn't sit under the homepage node, but on the same level on the level under the content node.  Looks like the template the macro doesn't work on is under the one it does...So I think you pointed me in the right direction.  Like I said I'll have to refresh my xslt skills.  My guess is it is not going far enough up the tree.

Awesome that last one worked. except i had to change inside the brackets back to @level=1.  I need to learn XSLT...Again.

I'm glad I found this post, becuase I faced the same issue here.

So looks like we have to change the slider setting from Static to Dynamic, ok, it is a chance to learn new XSLT.

There is something really puzling me !!!!

I read almost everywhere about using displaying images using img tag, and all the reference I found they request the use of XSL Umbraco Extension GetMedia() or something like that.

But, I am surprized to find out that in the above example, curly braces are used to specify the value of the image src using umbracoFile property

                <div class="imageSliderImage">
                  <img src="{umbracoFile}" width="500" height="320" />
                </div>

Is this a new feature in Umbraco 4.6.1 ?

Tarek

Hi tarek

You onlu need to use the GetMedia extension if you are grabbing the image from a media picker. I don't know which data type are used in this starter kit, but I gues it's an upload field with an alias of umbracoFile maybe?

/Kim A

Hi Tarek

The curly braces stuff is not something that is feature specific to Umbraco. It's a XSLT feature, which has always been there :)

If you're are in fact using the media section to store your images then have a look at this wiki entry about how to use the GetMedia extension: http://our.umbraco.org/wiki/reference/umbracolibrary/getmedia

Hope this helps.

/Jan

Thanks all for the reply.

I see the difference now. Media Picker and Upload Field and different.

But, I could not find any reference to the use of curly braces in any wiki or reference site. I found it by chance posted several years ago by D. Robar in the old Umbraco Forums. Looks like this is one of the "minor" undocumented features of Umbraco XSLT.

Is there a complete reference to XSLT implementation in Umbraco ?

Also, where I can get general reference to XSLT XPath. For example, I want to know the difference between :

<xsl:variable name="sliderNode" select="$currentPage/ancestor-or-self::root/umediaSliders"/>

and

<xsl:variable name="sliderNode" select="$currentPage/ancestor-or-self/umediaSliders"/>

Where I can find good reference for XSLT ?

Tarek.

Hi Tarek

Try taking a look at this page: http://our.umbraco.org/wiki/reference/xslt

The menu on your right hand have got links to some great examples and descriptions on how to use XSLT in Umbraco.

/Kim A

I find this code in CSS Custom.css:

/* EDITOR PROPERTIES - PLEASE DON'T DELETE THIS LINE TO AVOID DUPLICATE PROPERTIES */
body{ background-color:#333440;}
.newsbox .feedList h4 a, #sitedescription h1, a{ color:#ec008c;}
.primary-bgcolor, a.ui-btn-big, .newsbox .feedList h4 a:hover, #slider #imageSliderNav a.activeSlide{ background-color:#ec008c;}
#header #mainmenu ul, #header #mainmenu ul li{ background-color:#22212C;}
#header #mainmenu ul li.home a{ color:#22212C;}
body{ background-color:#333440;}
.newsbox .feedList h4 a, #sitedescription h1, a{ color:#ec008c;}
.primary-bgcolor, a.ui-btn-big, .newsbox .feedList h4 a:hover, #slider #imageSliderNav a.activeSlide{ background-color:#ec008c;}
#header #mainmenu ul, #header #mainmenu ul li{ background-color:#22212C;}
#header #mainmenu ul li.home a{ color:#22212C;}

But, I don't know how to reach this code to edit it from Umbraco back-office.

There is a bug where I must chage this line:

#header #mainmenu ul li.home a{ color:#22212C;}

To:

#header #mainmenu ul li.home a{ color:#ffffff;}

The above bug is causing the color of the "Home" navigation text to be black when you navigate to another page, which makes the home menu disapear.

How I can change it from Umbraco ?

Note: I am using FireFox 3.6 for now.

Hmm I'm sure I posted this...

In backoffice got to Settings->StyleSheet.  You should see custom.css under there.  Now to get the home icon to show when the button is not focused.

Thanks Good catch.

Hi Tarek

Like Nick says, you can go to the settings-section and fold out the Stylesheet folder. In here you can create all the stylesheets you want. And there might already be someone in that folder.

The stylesheets that's found in the Stylesheet-folder inside Umbraco is stored in the /css-folder in the file system, so you can actually change them both inside Umbraco or from the file system in yout favorit editor like Visual Studio, TextMate, Notepad++ etc.

/Kim A

Thanks - Nick and Kim.

I know how to modify CSS from Umbraco and also from Notepad.

My question was: I am unable to access the above CSS from Umbraco/Settings/CSS Folder.

Aparently, the CSS file "custom.css" has some problems.

When I created a new CSS entry (right-click) under custom.css, the following code was removed by Umbraco:

/* EDITOR PROPERTIES - PLEASE DON'T DELETE THIS LINE TO AVOID DUPLICATE PROPERTIES */
body{ background-color:#333440;}
.newsbox .feedList h4 a, #sitedescription h1, a{ color:#ec008c;}
.primary-bgcolor, a.ui-btn-big, .newsbox .feedList h4 a:hover, #slider #imageSliderNav a.activeSlide{ background-color:#ec008c;}
#header #mainmenu ul, #header #mainmenu ul li{ background-color:#22212C;}
#header #mainmenu ul li.home a{ color:#22212C;}
body{ background-color:#333440;}
.newsbox .feedList h4 a, #sitedescription h1, a{ color:#ec008c;}
.primary-bgcolor, a.ui-btn-big, .newsbox .feedList h4 a:hover, #slider #imageSliderNav a.activeSlide{ background-color:#ec008c;}
#header #mainmenu ul, #header #mainmenu ul li{ background-color:#22212C;}
#header #mainmenu ul li.home a{ color:#22212C;}

Oh ! Good that I got copy of it in this forum post. Mybe it is required by the starter kit.

The question know is:

1. Why the above code was in CSS file custom.css but could not reach it from Umbraco?

2. Why it was deleted when I create a sub CSS definition from Umbraco back-office ?

3. Is this CSS code required by this Business Starter Kit ?

Tarek.

I see the above code...but it is formated differently and there are no comments in the Umbraco editor.  

Nick,

Aparently, the version you have of the BSK, CSS custom.css, is different than mine.

I am just reporting what I find when working with BSK.

Tarek.

That could very well be.

Kim where are the starter kits located?  Can I go get the templates and what not from the Codeplex Repository somewhere?  I've looked unsuccessfully, but only using the online brower.

I installed the BSK using a fresh install of new Umbraco 4.6.1 and I chose the Business Starter kit during the install process.

I did not install BSK with the fresh separate download of BSK.

I am preparing for a POC requested by our IT Director and I am trying to be ready for all possible cases which might cause troubles. So, I need to understand what is going on?!?!

Tarek

Yes I installed that one too.  It seems half finished.

Hi Nick

I'm actually not sure if you can download the four different starter kits when you are not in the process of installing a new instance of Umbraco. But if you really need it, you can of course install a new Umbraco site, and choose the starter kit that you want, to check out the different files.

/Kim A

Hi,

I am also using the umedia skin of the Business Starter Kit in Umbraco 4.7

The umediaSlider was working, but then I wanted the umediaslider not on level 1 but under my homepage, because I'm planning for a multilanguage website (see screenshot, the document node using the umediaSlider is called Frontpage Sliders)

I adjusted the u.umediaslderimages.xslt to this new structure and changed the code for the sliderNode variable:

<xsl:variable name="sliderNode" select="$currentPage/ancestor-or-self::*[@nodeName= 'umediaSliders']"/>

But apparently this doesn't work. Not only do my sliderimages not appear, but the slider is now not only on the homepage - as it used to be - but one EVERY page under the homepage! This is something I don't understand, as I didn't make changes to the templates.

Is anybody seeing what am I doing wrong?

Thanks for your help,

Anthony Candaele
Belgium

I solved my problem by changing the code for the sliderNode variable to this:

<xsl:variable name="sliderNode" select="$currentPage/child::umediaSliders"/>

The problem with the slider appearing on every page was a false alarm. Because I moved the document node Frontpage Sliders under the Homepage document node, it appeared in the navigation menu. So just by adding a Hide from navigation property to the umediaSliders document type solved this problem too.

good night,

Anthony

Can anyone give me the xsl code to get these sliders to work? I tried all the examples in these three pages with no luck.

Or else can someone tell me how to create and test xpath queries against Umbraco? It's like fumbling around in the dark.

Hi Draggor and welcome to the forum :)

In order to figure out what the XML you're trying to target looks like you can go to the App_Data folder and open the umbraco.config file to see the XML structure. (Do not make changes in this file! Only look at it).

Then it should be more clear how things are structured and how you should write your xpath queries against it.

Hope this helps.

/Jan

Hi all, I'm new to umbraco (and to xsl also),  I've installed the Simply Starter Kit and also trying to get the sliders to work.

I've looked umbraco.config as Jan suggested and more or less this is the structure:

<root id="-1">
  <umbHomepage ...>
    ...
  </umbHomepage>
  <umediaSliders ...>
    <umediaSlider ...
    <umediaSlider ...
    <umediaSlider ...
    <umediaSlider ...
  </umediaSliders>
</root>

So how should I construct the xpath?

Thanks in advance...

Roberto.

Hi Roberto. Do you have some code already that we might have a look at?

If you are just looking for the xpath in the variable could you maybe try this out to seeif that works:

<xsl:variablename="sliderNode"select="$currentPage/ancestor-or-self::root/umediaSliders"/>

What the code does is taking the current node, going up to the root-node, and then going one level down to an element called umediaSliders.

/Kim A

Ya, mine is close to that:

<xsl:variable name="sliderNode" select="$currentPage/ancestor-or-self::root/*[@level=1]"/>

My xsl is rusty, so I don't know what exactly the difference is.  But it works on my site, if the slider content is on the same level as the website content.

Hi all...

I understand that razor new syntax can replace xslt so why not convert the whole thing to razor version and put an end for the suffering with xslt. I hope my sugestion is relevant though.

Tarek

Thank you, 

The problem was the sliders were hardcoded on the homepage template, so I just replace them with the umediaSliders macro. And that's it.

So, there was no need to change any xslt code... ;-)

Thank you again.

Roberto

Great to hear that you got things working Roberto :)

/Kim A

I am new too, so what are all the steps needed to get the sliders to work?

Hi Bill, and welcome to the post :)

First of all you need to have a macro, that points to a XSLT-file. Then you need to replace the static content that renders the slider, with the macro.

In the XSLT-file you need to have some code that looks pretty similar as the code shown on page 1 of this thread. When these steps are done you can be lucky that it just works, but I guess that we have to make some small changes.

Try going through the steps I just provided, and then maybe return in hereto tell us how far that get's you.

/Kim A

What Kim said.  The default template the slider is hardcoded in the template.  It's not using the macro template.  I make a package for myself....I think.  I know I had some other issues because I changed the templates around a little.  

Does anyone know where it get's the starter packages so we can fix them?

I have read through this thread. Unfortunately I am a complete beginner and can not figure it out. 

I went to settings/templates/starterkit master/business homepage to look at the code that apparently am supposed to change to be able to change the images in the frontpage sliders. 

The following is the code. Please tell me what exactly I need to change for what lines. Thank you so much for helping!

Hi Zed and welcome to our :)

So if I get your question correct you need to figure out what to change in the code above in order to be able to change the images.

In each of the <div>'s with the class "imageSliderInfo" there is an <img> tag. The value of the "src" attribute contains the path to the images. If you want to change the image displayed you can change this path to point to the image you want to have displayed instead.

So in each of the <img> tags you can change the src value like <img src="/images/mynewimage1.jpg" width="500" height="320" />.

Hope this makes sense and that I got your question correctly :)

/Jan

So, going by the details in this thread, am I correct in thinking that the 'fix' for this is to copy and paste the code from the xslt file which controls the sliders, into the template for the homepage, thus rendering the macro and the xslt file obsolete?

is working on a reply...