XF Move To-Do List

alethiophile. See if any of these fixes for us might help. Or failing that a similar topic for us on the XF board.
https://xenforo.com/community/threads/help-optimizing-mysql-high-server-load.75790/

 

Not acceptable by any means. That would leave huge swaths of content which would never get fixed because the authors either don't care or aren't even around anymore. I'd rather move back to the old software if we can't fix it.


Problem with the new rich-text editor: it's using server calls for operations that should be entirely local, like the insert-link dialogue, or the insert-spoiler dialogue. If you're on a slow connection, or the server's being laggy, this can be quite painful. I know this is fixable; it's been fixed on SB.

 

Fair enough: Though again that is determined by how endemic it is. I have not seen much in the way of this issue prior to @Ampersandwich mentioning it. If its only a few occurrences with regards to the massive fuck-ups then it should not be an issue. 'Huge Swathes' is a problem. Small occurances here and there is not exactly a major emergency, though one worthy of a fix. And I believe that alethiophile stated that the line-break issues should be able to fix via scripts, which is the big one I noticed.

Will talk to someone who may know how to fix this then. If its been done, then its possible and thus a simple matter of figuring out the 'how'.

 

Fine, but I propose we define the boundary between 'small occurrences' and 'huge swaths' as 'exactly as many instances as Vanathor is willing to go through and fix manually so the authors don't have to'~

Is it likely to be fixed any time soon? Because I stand by what I said before: if we can't fix this, better to roll back to the old software than to have parts of the archive unreadable. And if we do roll back, the sooner the better.


Another request: can we get a better plaintext BBcode editor? Or, well, any plaintext BBcode editor? Because what we have right now isn't really an editor at all; it's just a HTML text box. No formatting buttons, no colour selector - I get the distinct impression that whoever designed the XF editor only thew it in as a pro-forma alternative to the rich-text editor, without ever expecting anyone would actually use it.

 

Hey question I was just flipping through Alexander's Exalted/DxD quest when I noticed. All his smut isn't in the NSFW forum. It and a few other works seemingly didn't get transferred are they now lost?

 

Could you do something about the forum loading slowly?

I'm pretty sure all of it did get transfered.

 

Hm, how easy is it to upgrade this server again (hopefully without IP change^^)? And how well would that be covered by the subscriptions?

 

Nope even tried Searching for it by hand and through Alexander's name in Search neither shows up.

 

It's there. Go to page three of the nsfw board and it's right there.

 

Yes, like the one we had in SMF, basically. Right now, you can either use the WYSIWYG rich-text editor, or use the plain-text 'editor' and type every single BBCode by hand.

Can we do a global find/replace on the archives to fix all past instances of [hr]?

 

Need to reimport, then, without that 'feature'.

 

Find all threads by * in the information tab on the profile pages don't work.

 

If I had to guess it'd probably be something about the older threads not being indexed. I can find my new thread via the above method just fine.

 

I meant import-replace. If that's not possible, wipe everything in the current database older than the changeover, then reimport. Any edits made to posts older than that would have to be redone, but better working through a few days of edits than an untold number of errors.

 

No, just wipe out the stuff older than the move. Leave anything created since then intact.

 

No, it's not that. Or at least it's not just that. Those masses of extra added "[/color]" tags are corruption, as well; they weren't present in the original at all. (Never mind the "[color=#A4A77F]", etc, following that, or the mass of irrelevant closing tags at the trailing end of the post.) Additionally, SMF's [code] and [tt] tags appear to have been merged, which is very wrong: the latter should have been changed to [font="Courier New"] tags or somesuch.

And, as you noted later, the [hr] tags have been lost. It should be almost trivial to add [hr] support with a plugin; at the very least unknown tags should be left in place, untouched, rather than stripped entirely. (As was done for the [nobbc] tag, which XF could sorely use an equivalent to.)

No, that's not right at all. Nesting a [color] tag does make sense, if (say) you want a single bit of red text in the middle of some cyan, and I'm pretty sure SMF and XF will handle those cases identically: basically like this, open open close close. What I remember doing on SMF wasn't just to nest and close color tags, though; there was another tag (explicit default size, maybe? I've forgotten) that I used to surround the whole shebang, implicitly closing all the "color" tags when I closed that outer tag. That's what SMF did that XF doesn't do: in XF, unclosed interior tags leak out of the enclosing tag.

SMF's code needs to be properly parsed and restructured in order to translate it to legal XF code, and the importer simply did not do this.

It totally is to the point of illegibility. See the first link I provided, and scroll down. Highlight. That text shouldn't be transparent.

I don't see why you think the fix would entail loss of data. It should be possible to import only unchanged posts.

 

It has one: [plain]

 

That would have been helpful to know when writing that post. Well, add to the complaints list that [nobbc] isn't properly converted to [plain], then.