Release 87

Nov 09, 2011 21:16

Release 87 is now live!

We don't have any new features to announce, but we do have some bug fixes:

  • Errors when exporting journal entries and comments via XML should no longer occur. (LJSV-1734) [Edit] Looks like we're still having problems here, although it's a different problem than before. We're working on it!
  • The font in the HTML editor has ( Read more... )

r87

Leave a comment

Comments 173

surrey_sucks November 10 2011, 05:22:29 UTC
I can read the font!

Reply


cloex_brosluvr November 10 2011, 05:27:42 UTC
The font in the HTML editor has changed. It is now the same as the default option in the Rich Text Editor (RTE).

OH THANK GOD! That was such a pain in the ass to have to see every single time I wanted to update my journal.

Reply

Seconded centauris_dream November 10 2011, 06:09:21 UTC
Yes, it looks great! Thank you bug fixing team!!

Reply


softpaw November 10 2011, 05:28:40 UTC
I'm still getting this error

System.Xml.XmlException: '<', hexadecimal value 0x3C, is an invalid attribute character. Line 108, position 99.
at System.Xml.XmlScanner.ScanLiteral()
at System.Xml.XmlTextReader.SetLiteralValues(XmlAttributeTokenInfo fld)
at System.Xml.XmlTextReader.SetAttributeValues()
at System.Xml.XmlTextReader.ParseElement()
at System.Xml.XmlTextReader.Read()
at EF.ljArchive.Engine.Sync.ExportCommentsMeta(OptionsRow or, ILJServer iLJ, SessionGenerateResponse sgr, Int32& serverMaxID, UserMapCollection umc)
at EF.ljArchive.Engine.Sync.ThreadStart()

When I try to download comments with LJarchive. Is this a different issue then the one you fixed?

Reply

markf November 10 2011, 05:39:22 UTC
Looking into this now... at a glance, I think it's a different error than it was throwing before and may be a new issue.

Reply

softpaw November 10 2011, 05:40:03 UTC
Just my luck!! Thank you for working to fix this.

Reply

bandicoot November 10 2011, 06:21:16 UTC
Are you saying that you thought you'd fixed the comment export issue with LJArchive, et al? If so, you didn't. If not, I'm still waiting patiently ;)

Reply


raemia November 10 2011, 05:32:28 UTC
The font in the HTML editor has changed. It is now the same as the default option in the Rich Text Editor (RTE).

YESSSSS! Thanks so much, it looks a lot better!

Reply


fencer_x November 10 2011, 05:46:17 UTC
I thought the prevailing wish was that the font be changed back to the way it was BEFORE you went about mucking with the fonts (i.e. the same font in the comment boxes).

Now I have to check and make sure I'm not accidentally writing in the RTE when I make a post. What gives??

Reply

rhymephile November 10 2011, 06:06:16 UTC
I thought this is what we have been bitching about too. It's nice the html and the rt editors match, but we want it back to the original font, like the one still used in comments.

I still have trouble telling the difference between periods and commas in the new font!

Reply

markf November 10 2011, 06:17:33 UTC
There's still a patch planned to get it back to the original font/what shows up in the comment form (it's not as easy to fix as it sounds, unfortunately), this was done more as a quick temporary improvement over what's been showing since the last release.

Reply

rhymephile November 10 2011, 06:28:47 UTC
Hey, all right then! I can be patient as long as there is indeed a fix in the works. I know it's not only me, as it seems everyone has been complaining about the poor font readability and size. I will keep squinting until the repair comes through.

Reply


Leave a comment

Up