Hi,

Have you tried added a blank space?

I.e.

        <a class="thumb" name="leaf" title="Title #0">
            <xsl:attribute name="href">
            <xsl:value-of select="data[@alias='topicUploadPicture']"/>
            </xsl:attribute>
            &nbsp;
        </a>

It's a bit of a hack but it might work for you?

Cheers,

Chris

Or instead of a blank space, what I tend to do is a non breaking space:

       <a class="thumb" name="leaf" title="Title #0">
            <xsl:attribute name="href">
            <xsl:value-of select="data[@alias='topicUploadPicture']"/>
            </xsl:attribute>
            <xsl:text>&nbsp;</xsl:text>
        </a>

Oh.. well that didn't come out as it should have.. It said & n b s p ; (without the spaces!) in the <xsl:text> element.

Hi!

Thank you for helping me!

Ok, I have now tested to write:

        <a class="thumb" name="leaf" title="Title #0">
            <xsl:attribute name="href">
                <xsl:value-of select="data[@alias='topicUploadPicture']"/>
            </xsl:attribute>

        </a>

And:

<a class="thumb" name="leaf" title="Title #0"><xsl:attribute name="href"><xsl:value-of select="data[@alias='topicUploadPicture']"/></xsl:attribute></a>

None of them makes any difference to the output, stil gets <a stuff /> instead of  <a stuff></a> :(

Any more ideas?

(also I am wondering about a thing that I simply do not understand. When I use things like this gallery or jCarusel, where jQuery scripts have to be imported into the master template. FF does not seem to find the script unless it is imported directly into the xsl. In IE there is no problem. I can use the example code given, no problems. But as soon as I get the html through the xsl, FF can't find the script-tags unless they are in the xsl file.

I do not have the same problem otherwise (have a superfish menu that works just fine without importing the script to the xsl). I can generate html through xsl and then just add script-tags to the master template and it works. Are there any special rules to follow when importing script-tags? )

Thank you!

The only other thing I would suggest is using the following syntax:

  <xsl:element name="a">
    <xsl:attribute name="name">leaf</xsl:attribute>
    <xsl:attribute name="class">thumb</xsl:attribute>
    <xsl:attribute name="itle">Title #0</xsl:attribute>
    <xsl:attribute name="href">
      <xsl:value-of select="data[@alias='topicUploadPicture']"/>
    </xsl:attribute>
  </xsl:element>

HTH,
Nik

Oh, one more thing....make sure your output type is set to HTML:

<xsl:output method="html" omit-xml-declaration="yes"/>

Otherwise, the parser will lop-off empty end tags.

Thanks,
Nik

Hi again :)

Okej, now (sitting in China at the moment, so I am 7h away) I have tried to write as Nik said, but it did not work and I am not sure of how to change the XSLT output method html. It complains on the attribute - method then. So then I tried to write:

<li>
        <!-- use xsl:text to keep xslt from shortening the A tag -->
        <xsl:text disable-output-escaping="yes">&lt;a class="thumb" name="leaf" href="</xsl:text>
        <xsl:value-of select="data[@alias='topicUploadPicture']"/>
        <xsl:text disable-output-escaping="yes">" title="</xsl:text>

    <xsl:value-of select="data [@alias = 'topicTextStringTitle']"/>
 <xsl:text disable-output-escaping="yes">">&lt;/a></xsl:text>

        <div class="caption">
                <div class="image-title">
                        <xsl:value-of select="data[@alias='topicTextStringTitle']" disable-output-escaping="yes"/>
                </div>
        <div class="image-desc">
                        <xsl:value-of select="data[@alias='topicRichTextDescription']" disable-output-escaping="yes"/>
                </div>

        </div>
</li>

   That gives me the right html output :D (but somehow the discription gets <p> tags!):

<li>
    <a class="thumb" name="leaf" href="/media/8773/2_b.jpg" title="Picture one"></a>
    <div class="caption">
        <div class="image-title">Picture one</div>
        <div class="image-desc"><p>Description for picture one</p></div>
    </div>
</li>

So that is great. But for some reason it simply does not work in IE6 and Safari (in IE6 the buttons does not work and in Safari there is no image). It is a little bit hard to explain. But when I take the output given by the macro and use that instead of the macro (just to try :) ) in the template, it works in IE6, IE7, Safari and FF (have not tried in Opera, Maxthon or Crome). BUT as soon as I use the macro (even though the output is the same) it does not work!

This is how the whole xsl looks now:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:stylesheet [
  <!ENTITY nbsp "&#x00A0;">
]>
<xsl:stylesheet
    version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:msxml="urn:schemas-microsoft-com:xslt"
    xmlns:umbraco.library="urn:umbraco.library"
    exclude-result-prefixes="msxml umbraco.library">

  <xsl:output method="xml" omit-xml-declaration="yes"/>
  <xsl:param name="currentPage"/>
  <xsl:template match="/">

<xsl:value-of select="umbraco.library:AddJquery()"/>
<xsl:value-of select="umbraco.library:RegisterJavaScriptFile('', '/scripts/jquery.galleriffic.js')"/>
<xsl:value-of select="umbraco.library:RegisterJavaScriptFile('', '/scripts/jquery.opacityrollover.js')"/>

<!-- some code given in the template, but FF does not see it if it is not in here -->

<xsl:value-of select="umbraco.library:RegisterJavaScriptFile('', '/scripts/gallerifficExtra.js')"/>   
   
 <xsl:choose>
      <xsl:when test="count($currentPage/node [@nodeTypeAlias='sdeerTopicItem']) &lt;= 0">
        <div id="noTopicImages">
          There are no beautiful photos to show yet...
        </div>
      </xsl:when>
      <xsl:otherwise>                     
        <xsl:for-each select="$currentPage/node[@nodeTypeAlias='sdeerTopicItem']">

    <li>
        <!-- use xsl:text to keep xslt from shortening the A tag -->
        <xsl:text disable-output-escaping="yes">&lt;a class="thumb" name="leaf" href="</xsl:text>
        <xsl:value-of select="data[@alias='topicUploadPicture']"/>
        <xsl:text disable-output-escaping="yes">" title="</xsl:text>

    <xsl:value-of select="data [@alias = 'topicTextStringTitle']"/>
    <xsl:text disable-output-escaping="yes">">&lt;/a></xsl:text>

        <div class="caption">
                <div class="image-title">
                        <xsl:value-of select="data[@alias='topicTextStringTitle']" disable-output-escaping="yes"/>
                </div>
          <div class="image-desc">
                        <xsl:value-of select="data[@alias='topicRichTextDescription']" disable-output-escaping="yes"/>
                </div>

        </div>
    </li>
        </xsl:for-each>
      </xsl:otherwise>
    </xsl:choose>
  
  </xsl:template>
</xsl:stylesheet>

(I have the script import in the xsl because for some reason FF does not find the script otherwise. Do not know why... )

Thank you and HAPPY NEW YEAR! :D

You are really close!

The <p> tag is probably coming from the richtext editor. I assume you're using a richtext editor because of the document type alias name.

<xsl:value-of select="data[@alias='topicRichTextDescription']" disable-output-escaping="yes"/>

There are a couple ways to handle this depending on your needs.

1. Change the docType property to be a 'text multiline' rather than a richtext editor. You won't have wysiwyg editing but you also won't get extraneous markup. (you'll want to review all the pages with a topicRichTextDescription field to clean out any 'extra' markup)

2. Strip off the surrounding <p> tags with the umbraco.library:RemoveFirstParagraphTag() function, like this:

<xsl:value-of select="umbraco.library:RemoveFirstParagraphTag(data[@alias='topicRichTextDescription'])" disable-output-escaping="yes" />

3. Strip out all html tags with the umbraco.library:StripHtml() function, like this:

<xsl:value-of
select="umbraco.library:RemoveFirstParagraphTag(data[@alias='topicRichTextDescription'])"
disable-output-escaping="yes" />

cheers,
doug.

Hi,

Just to add in my example at the top I also put a:

 & n b s p ;

( Without the spaces )

But as with Sebastian's example the forum removes it ;-)

Cheers,

Chris

Or, if you want to retain the paragraph tag, you could eliminate any margins or padding by applying the following style rule:

.image-desc p { margin: 0; padding: 0;}

Of course, you may have other reasons for not wanting the p tag in there. If so, I would vote for Dougs 1st suggetion in the above post, change the property on your docType (since you don't want/need the author to apply any style or markup to the content). 

HTH,
Nik

Hi! Thank you for all your answers! I have been away to Beijing over the new year, so I am sorry for not writing until now.

Once I got the xsl to do what I wanted the slideshow stil did not work in IE and Safari. But we had placed the jQuery script tag in two locations to make FF find it (in the xsl and in the template). So just now I commented the script tag in the template and now it works in Safari, IE 6 and 7, FF and in Maxthon.. woohoo!! :D

Thank you again!

is working on a reply...