|
Welcome, new forum! Strange issue: When trying to edit a question/answer, the edit box shows the previous contents as HTML. That makes it hard to edit the contents:
That hasn't been a problem in SQLA nor in the beta, AFAIK. |
|
This looks like an artifact of the migration from sqla to sqlanywhere-forum. I believe StackExchange stores two versions of the text - the HTML for display and the markdown for editing. This is so that they don't have to run through the markdown stuff every time you view anything. I don't think OSQA does this, so it likely just imports the HTML from StackExchange. But then why hasn't that issue shown up in the beta phase? (I'm very sure I had edited imported postings from SQLA then without noticing this behaviour.) - Looks like this is happening for all imported postings. Editing fresh postings works as expected (err, say, the display is correct - haven't really edited yet.)
(11 Mar '11, 12:10)
Volker Barth
Replies hidden
Yeah, I wondered that too. None of the import code has changed at all, so perhaps StackExchange made some kind of change to their database or export in between the last two exports.
(11 Mar '11, 12:25)
Graeme Perrow
FYI I reloaded the beta database into a test instance and the same problem occurs there - only for some questions/answers though. I guess nobody tried to edit the buggy ones during the beta period.
(15 Mar '11, 07:18)
Graeme Perrow
|
|
Just a further question: Is this an issue to be fixed, or are fixes to the SXImporter stuff out of reach? I just tried to edit an imported posting, and it was hard. - Well, I could say I've learnt about the way the markdown syntax is mapped to HTML code but that is not what I'm eager to have to learn to:) I am investigating but I suspect that those changes are there to stay. The only alternative would be to fix the importer (don't know how long that would take) and then re-import the sqla database, which would wipe out all users, questions, answers, comments, etc. from last Friday to whenever the importer is fixed. Editing an existing posting is fairly rare, and as time goes on there will be much more new postings than imported ones so it will be less of a problem.
(15 Mar '11, 07:16)
Graeme Perrow
Replies hidden
Well, if there's no chance to fix the already imported stuff (as I conclude from your statements), then I'll cope with the situation. A re-import definetely is a no-go IMHO. I hope (and am quite sure) the NNTP import won't have such a problem - due to the overall lack of formatting:) (Yes, and won't use the so-called StackYaddaYadda importer).
(15 Mar '11, 07:35)
Volker Barth
|
Or have I interfered with the starting phase? Then I'm sorry:)