This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.
Please use forum.silverstripe.org for any new questions
(announcement).
The forum archive will stick around, but will be read only.
You can also use our Slack channel
or StackOverflow to ask for help.
Check out our community overview for more options to contribute.
Thanks so much to willr, Hamish, LeeUm and all the others for giving up your valuable time to help us on the forum...
Got my first SS site up and running http://www.search4pharma.co.uk
Couldn't have done it without you!
Even with all the teething problems, I have to say Silverstripe ROCKS!!! And I voted for you!
Thanks again
Michelle
Hey Michelle, no worries.
Just by the way, FF3 is throwing an XML parsing error on your site:
XML Parsing Error: mismatched tag. Expected: </div>.
Location: http://www.search4pharma.co.uk/
Line Number 202, Column 3:</body>
--^** OK figured out what this means and have fixed it **
Think I will have to stop asking you guys and figure these errors out for myself! Makes for a better learning experience :-)
-----------------------------------------------------------------------------------------------
Okkkkkkk haven't tested it across multiple browsers yet, ooooops.
Ummmm, what is an xml parsing error and any advice on how to fix it please?
:-)
Not a problem at all. Just doing my small part to help the SS userbase grow.
Site looks good, though I still get the xml error on sub pages. Front page is fine, so whatever the fix for that was, needs to be implied on sub pages.
SilverStripe by default sends templates as suppperrr strict XHTML (which some people like, some don't) but this means it complains about every little detail. By the looks of the error hamish provided you are missing a </div> in the template
@Michelle - keep asking those questions! I learn a lot from reading other peoples' responses too.
@Will - it's great that SS almost always validates as XHTML strict (if not, it's usually because of a templating issue), but might be worth reminding people, especially if you're working with (say) IE7 that hides the errors.
There is another downside - I've reported a bug where random characters are appended to the beginning of the stream. IE7 handles it, but it breaks FF3 because it's not correct XML. Until that's fixed, I'll make a point of validating the site, then switch strict XML off.
