Well, I could report a problem if you wanted, but it's totally cause I'm doing something we've not officially turned on yet and I know exactly why it's ugly!
( but I could be all "Waa Waa I turned on my s2-styled /icons page manually and it's ugly!" if it'd make you feel better )
The RSS feeds on my reading list are now displaying (identical) links to the original post both above and below the post text. Only for the updates that happened after the code push, too.
That is actually a feature, not a bug. (People asked for the links to be duplicated, so they didn't have to scroll back to the top of the entry if they wanted to click through and leave a comment/view it on the local site.)
I love this feature. I may have babbled about it already in my journal.
I wasn't surprised by this behaviour, but will this count as weird?
If the feed has broken code, so it is put behind a cut, the bottom link isn't there. Or it might be behind the cut. E.g. the second (at the time of posting)post on grauniad_tech_feed
How about blockquote tags not previewing indented?
I'm pretty sure the blockquote not being indented in previews thing is already in bugzilla! (The problem will go away as we modernize more of the code that generates the site pages, which is a project people are working on.)
Having the second link behind the cut in the event of HTML/CSS our HTML cleaner doesn't like is actually By Design, since for safety's sake we just slap a <cut> in at the point of breakage and everything past that stays behind the cut. (ie, we don't close the cut that we add). I mean, we probably could put in a </cut> tag before the second link, but it wouldn't do much good, since the second link isn't autolinkified. (Once you hit an invalid HTML error, the system stops auto-linking links.)
Hmm, I was about to mention support request 8396 (Atom feeds with duplicate xmlns attributes) but that appears to have started between 4am and 6am GMT, so at least 6 hours before this push. Did anything get updated early?
Just noticed now but a lot of previously deleted/renamed tags have suddenly shown back up again. Could that be a result of this? Because I'm not sure how to explain it otherwise. o_O
Out of curiosity, did you just do an import from another journal system? Imports will import deleted tags too -- this is due to how the data gets sent to us, and it isn't something we can fix.
No, I haven't, not recently. :) Just suddenly there were lots of zeros by tags and first there was panic wondering *why* there were zeros there - where did all my stuff go?! - before I realised they were tags I'd renamed/deleted and then I was just confused all over again. :)
Okay, that is officially weird! If you don't mind re-deleting and re-merging them, just go ahead and do so -- about the only thing support could do is confirm that yup, that's weird, since I don't see anything on your account that might make sense/cause it. We will keep an eye out for any other reports of this, which might indicate a wider problem, though, and if it crops up again, I will come back and poke you to come troubleshoot with us, if that's ok!
no subject
no subject
( but I could be all "Waa Waa I turned on my s2-styled /icons page manually and it's ugly!" if it'd make you feel better )
no subject
Well, there was this squadron of purple flying pigs passing by my window in formation this morning...
Dear YouTube: PLZ work.
You asked for something weird, did you not?
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
Re: Dear YouTube: PLZ work.
no subject
no subject
no subject
no subject
no subject
Two, count 'em, two weird things
I wasn't surprised by this behaviour, but will this count as weird?
How about blockquote tags not previewing indented?
Re: Two, count 'em, two weird things
Having the second link behind the cut in the event of HTML/CSS our HTML cleaner doesn't like is actually By Design, since for safety's sake we just slap a <cut> in at the point of breakage and everything past that stays behind the cut. (ie, we don't close the cut that we add). I mean, we probably could put in a </cut> tag before the second link, but it wouldn't do much good, since the second link isn't autolinkified. (Once you hit an invalid HTML error, the system stops auto-linking links.)
i'm sorry, i couldn't resist.
Fu is fantastic!
no subject
no subject
Will look into it!
no subject
no subject
no subject
no subject
(If not, then carry on!)
no subject
no subject
Okay, that is officially weird! If you don't mind re-deleting and re-merging them, just go ahead and do so -- about the only thing support could do is confirm that yup, that's weird, since I don't see anything on your account that might make sense/cause it. We will keep an eye out for any other reports of this, which might indicate a wider problem, though, and if it crops up again, I will come back and poke you to come troubleshoot with us, if that's ok!
no subject
And sure, that's fine, although I don't know how much help I could be. :)
no subject
no subject
no subject
no subject