The solution I used for this was to remake the xmlstring.
I have learned, through trial and error, to make my xml
more parsable for the xsl.
<rootnode>
<topMenu>
<menuname>Home</menuname>
<menudescribe>Return to the Home Page</menudescribe>
<menuurl>./</menuurl>
<domain_name>localhost</domain_name>
</topMenu>
<topMenu>
<menuname>Forum</menuname>
<menudescribe>PHPro Forums</menudescribe>
<menuurl>./?ext=forum</menuurl>
<domain_name>localhost</domain_name>
</topMenu>
<topMenu>
<menuname>News</menuname>
<menudescribe>All the news that is news</menudescribe>
<menuurl>./?ext=news</menuurl>
<domain_name>localhost</domain_name>
</topMenu>
<topMenu>
<menuname>Contact</menuname>
<menudescribe>Contact Us</menudescribe>
<menuurl>./?ext=contact</menuurl>
<domain_name>localhost</domain_name>
</topMenu>
<splash>
<splash_name>splashname one</splash_name>
<splash_text>splash text one</splash_text>
<splash_domain_name>localhost</splash_domain_name>
</splash>
</rootnode>
This allows me much better control with xsl
Kind regards
Kevin
--
______
(_____ \
_____) ) ____ ____ ____ ____
| ____/ / _ ) / _ | / ___) / _ )
| | ( (/ / ( ( | |( (___ ( (/ /
|_| \____) \_||_| \____) \____)
Kevin Waterson
Port Macquarie, Australia
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list