1.0 Problems posting

  • dbowen

    (@dbowen)


    22 years, 4 months ago

    Okay, have been rolling along nicely (build from 2004/01/07), but have struck a problem when saving a particular post. This is the text:
    http://www.toxiccustard.com/stuff/wp/tintin2.txt
    But each time it’s Saved in WP’s post screen (including Save as draft, Publish – any option), the end of it gets corrupted, so after a couple of saves, it looks like this:
    http://www.toxiccustard.com/stuff/wp/tintin-afterSave.txt
    I tried removing all formatting and hyperlinks from the piece, and it seemed to work okay… but this is something I can’t post without the appropriate “em” around the quotes 🙂
    Can anybody else copy this text into a post and see if it does the same thing? Or has this been fixed in the builds of the last few days?
    Thanks,
    Daniel

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    PS. Have turned off all fancy HTML options such as BBCode, GMCode, QuickTags, HtmlTrans, BalanceTags and Smilies.

    Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    Thanks. Okay, time to fiddle with the versions I think. I assume something went askew with post.php

    Anonymous

    22 years, 4 months ago

    Perhaps it’s not post.php but some other bit of code, since substituting the latest build or the 1.0 versions didn’t help. Odd. It hasn’t occurred on other posts, and I’m guessing it had a problem with something in the embedded tags.
    I’ll keep playing with it as I get time. In the mean time I got around it by manually copying the text into the table via PhpMyAdmin!
    Daniel

    Anonymous

    22 years, 4 months ago

    I have forrowing error in 1.0.
    in new install, if there is only one entry, no error but multiple entries, then this error.
    SQL/DB Error:
    [<span style=’color: #007;’>Out of memory. Restart daemon and try again (needed 65528 bytes)</span>]
    SELECT DISTINCT * FROM b2_posts WHERE 1=1 AND post_date <= '2004-01-12 20:35:27' AND (post_status = "publish") ORDER BY post_date DESC LIMIT 20

    Anonymous

    22 years, 4 months ago

    the above trouble Posted in Jan 12, 2004 05:39:12 is solved by 1.0.1.thanks.

    Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    Cool.
    Well I’m still having my issue – it showed up on another post. Seems to be length and/or HTML related, as when I put in an <img> tag, it corrupted it, but removing it again seemed okay. I did check the tag itself, and it seems okay.
    Haven’t had time to do more fiddling, but at this stage I will probably wait for the 1.01 release and see if that resolves it.

    NuclearMoose

    (@nuclearmoose)

    22 years, 4 months ago

    Try a nightly build.
    Craig.

    Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    Okay, well here I am now running 1.01 RC1. And yes, the problem’s still around. Basically if the post goes over a certain size (and evidently particularly if it has HTML tags) it gets corrupted as above, with some of the last part of the post being duplicated.
    Could it be some weird bit of my web server’s PHP version perhaps? (See http://www.toxiccustard.com/diary/phpinfo.php )

    Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    Okay this appears to be an issue with my server. Chasing it up with administrators.

    Thread Starter dbowen

    (@dbowen)

    22 years, 4 months ago

    Okay dudes, I’ve nailed it. I’m guessing it’s an obscure PHP bug, but basically if you have a line like this in your .htaccess
    AddType application/x-httpd-php .php .html
    …then posting does funny things. With upgrading my diary to WordPress, I didn’t need that line anymore anyway, so it’s all happily working now.
    Daniel

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

The topic ‘1.0 Problems posting’ is closed to new replies.