There's something odd going on with the site's handling of url's in comments.

For example, yesterday I posted a url for 'Pink Peace' on the Knight's Roses site. No problem. The url just displays in the comment, as you would expect. See - /gardening/l.php?l=2.4838.0

Today I went to post comments about 'Gruss an Teplitz' and 'Safrano' being available from Ross Roses. The comments would not be displayed unless I broke up the url with spaces. See - /gardening/l.php?l=2.3131.0 - and - /gardening/l.php?l=2.5580.0

Both nurseries are listed on this site, so should be acceptable as links. You appear to have a bug hiding somewhere. :)

------------------------------------------------------------
PS: Somewhat related (also to do with url's) but a feature request rather than a bug per se...

This may have been mentioned and thought about over the years, but since each comment has an ID set in the database it would be great if this was also an accessible anchor in the GUI markup. That way people could link to individual comments in discussions, instead of just being restricted to linking to the description page for the rose in question. Offhand I can't see this being a huge deal to code, and I think it's worth considering at some point. It's standard functionality for most forums.

------------------------------------------------------------
PPS: Aha! You can already do it if you know how to use the browser's document inspector. For example, under 'Pink Peace' you can grab the .threadLnk ID to link directly to a thread (example - /gardening/l.php?l=2.4838.0&tab=32#t140527) and you can grab the div.qc ID to link directly to a particular comment (example - /gardening/l.php?l=2.4838.0&tab=32&qn=1&qc=0#q48084).

So, no problem if you know a few tech tricks and don't mind messing around a bit, but a black art for the average user. And the relevant ID''s are already being called from the database, so all that is required is a minor markup change in a template or two. Then your Aunt Nelly could do direct links even after several G & T's. :)

I think I'll write a brief tutorial on this workaround. It's easy to implement on desktop* once it's explained, and it may be useful to some members.

*It's possible to do it on touchscreen too, at least on Android, but it's probably more trouble than most members would want to know about.