Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Forum: Plugins
    In reply to: Xanga import?

    Currently the only fix I am able to find for this problem is to manually remove all the non-breaking-spaces.

    I am working on the date thing. Also, the current xanga importer leaves in the “<font>” tags, screwing up WordPress’ theme. Working on that one too.

    Forum: Plugins
    In reply to: Xanga import?

    This has been a dead topic for a while. I’ve been trying to do the same thing, but the community really hasn’t been stepping up to help.

    I’ve got a copy of the current “Xanga Archive Importer” and am trying to correct a few of the errors I’m encountering:

    1) All spaces at the end of sentences are replaced with a “?”
    2) All posts are imported to Jan 1, 1970

    If you could run the current importer on her archives and see if you get the same errors, that would really help me.

    Thread Starter everglow

    (@everglow)

    Got it fixed — I used the XML export plugin for my 2.0.1 install and then just imported the XML into my new 2.1 install using the WordPress Import option. Worked wonderfully!

    Since this has solved my problem, I have no reason to check the character encoding logs, although it’s very likely that was the issue.

    Is there a way to format an XML document for different encoding? I was having this exactly problem with a Xanga plugin. Would I just edit the character encoding name at the top of my XML document?

    Forum: Fixing WordPress
    In reply to: Xanga Import

    Except it no longer works.

    Forum: Fixing WordPress
    In reply to: import from xanga

    You have to go through your archive files and replace all of the ” ” with ” “. The importer reads all these Space tags as a ?.

    @dinkumator: That script no longer works. It screws up the formatting and reads spaces as “?”. Update?

Viewing 6 replies - 1 through 6 (of 6 total)