Canalplan Bug Tracker

Anonymous Login
2019-07-22 11:40 BST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000403Canalplan [All Projects] Bugpublic2019-05-18 22:30
ReporterStephen Atty 
Assigned ToNick Atty 
PlatformGenericOSN/AOS VersionN/A
Product VersionProduct Build 
Target VersionFixed in Version 
Summary0000403: RSS feed for new contributions invalid
DescriptionWe seem to have the old issue with & back:

This feed does not validate.

    line 87, column 15: link must be a full and valid URL: (5 occurrences) [help]


    line 101, column 41: guid values must not be duplicated within a feed: place: (4 occurrences) [help]

                 <guid isPermaLink="false">place:</guid>

    line 3611, column 43: XML parsing error: <unknown>:3611:43: not well-formed (invalid token) [help]

                 <title>Discussion about Dartford & Crayford Navigation (Dartford Cr ...

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

    line 15, column 101: Self reference doesn't match document location [help]

        ... rel="self" type="application/rss+xml" />

    line 38, column 19: description should not contain relative URL references: // (302 occurrences) [help]


TagsNo tags attached.
Attach Tags (Separate by ",")
Attached Files




Nick Atty (administrator)

That's the discussions - hence not picked up by the automatic escaping. Will fix. I'll look at the other validation points another time.


Nick Atty (administrator)

Try it now. You can always edit a comment on a suitable place if they've all aged off.


Nick Atty (administrator)

[Valid RSS] This is a valid RSS feed.


Stephen Atty (administrator)

Now its over escaping

Discussion about Varney's Lock Field Bridge edited


Stephen Atty (administrator)

Its now over escaping some stuff


Nick Atty (administrator)

The real question is why it wasn't escaping the '&' in the first place - both names go through exactly the same code.


Autoclose (administrator)

Closing automatically, stayed too long in feedback state. Feel free to re-open with additional information if you think the issue is not resolved.

-Issue History
Date Modified Username Field Change
2018-02-25 13:35 Stephen Atty New Issue
2018-02-25 13:35 Stephen Atty Status new => assigned
2018-02-25 13:35 Stephen Atty Assigned To => Nick Atty
2018-02-27 07:38 Nick Atty Note Added: 0001580
2018-02-27 07:43 Nick Atty Note Added: 0001581
2018-03-03 12:33 Nick Atty Status assigned => resolved
2018-03-03 12:33 Nick Atty Resolution open => fixed
2018-03-03 12:33 Nick Atty Description Updated View Revisions
2018-03-03 12:33 Nick Atty Note Added: 0001585
2018-03-03 21:40 Stephen Atty Note Added: 0001588
2018-03-03 21:40 Stephen Atty Status resolved => assigned
2018-03-03 21:40 Stephen Atty Note Added: 0001589
2018-03-04 06:06 Nick Atty Note Added: 0001590
2019-04-18 21:40 Nick Atty Status assigned => resolved
2019-05-18 22:30 Autoclose Note Added: 0002464
2019-05-18 22:30 Autoclose Status resolved => closed
+Issue History