Forum Replies Created

Viewing 3 replies - 31 through 33 (of 33 total)
  • I’m getting the same error, though it comes from line 1331 in http.php.

    I have chased down all the suggestions in other threads, such as bumping WP_MEMORY_LIMIT in wp-config (no change) and adding “php_value memory_limit 64M” to .htaccess (generates a 500 internal error). Also disabled all plugins aside from auto-update.

    I’m stuck on auto-update. I can do a manual, but would like an elegant fix as opposed to the manual process.

    Thanks to esmi for replies as useless as a politician’s promise.

    After a fair bit of web scanning, the problem was identified as the MySQL 4.x to 5.x character set conversion hell. There are a few solutions offered around the web, but the best (and the one that actually worked given the added problems 1and1 creates) was found at:

    http://www.bluebox.net/news/2009/07/mysql_encoding

    Good luck to everyone else in similar migrations.

    @esmi: Yes, everything was backed-up and returned to its original condition (always, always, always).

    I don’t see how the leap from 2.8.6 to 3.2.1 would be the source of the problem. Assuming I’m correct about the MySQL issues, then it appears to be the way WP processes and displays the data extracted from MySQL. That should be an identifiable/correctable config/bug.

Viewing 3 replies - 31 through 33 (of 33 total)