A new Symphony page returns an XSLT error
A for , submitted by nickdunn on 23 March 2010
Announcement
Symphony's issue tracker has been moved to Github.
Issues are displayed here for reference only and cannot be created or edited.
Browse
Closed#281: A new Symphony page returns an XSLT error
-
-
- nickdunn
- Comment #1
- 23 Mar 10, 3:31 am
-
-
- czheng
- Comment #2
- 23 Mar 10, 4:20 am
Yeah I kind of agree with this. For 2.1 we’ve introduced the ability to override the default XSLT for new templates and utilities, so might be a reasonable time to make that tweak… The default could be something a bit more user-friendly, and then more experienced devs could override that with their barebones stylesheet.
-
-
- nickdunn
- Comment #3
- 23 Mar 10, 5:44 pm
All it needs is something inside the default template, and the error disappears. That could be a call to another template, some static text, or a value-of the $website-name parameter.
-
-
- Alistair
- Comment #4
- 29 Apr 10, 5:05 pm
Good idea. Using $page-title.
http://github.com/symphony/symphony-2/commit/cf2d380dc479563eec5586bbb1c69849aefccff9
This issue is closed.
Symphony creates a page with the most basic XSLT possible, which is a good thing (keeping it lean). But I’ve always thought it a bit odd that a new page triggers an XSLT processing error by default.
While the error message encourages the developer to change the XSLT immediately, it also means that for a first-time user who has excitedly created their first Symphony page, they are greeted with a processing error implying they’ve done something wrong. To me this is a negative user experience.
One for 2.1?