Forum Replies Created

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

    (@husky)

    I know, but i was just wondering.. Someone might have made a compatibility library or something..

    If you have control over the server, you could try turning on PHP error reporting to see a little more information.

    Thread Starter Husky

    (@husky)

    I fixed it. Thanks to the suggestion of dpinna13 i started looking at my theme in a local installation and saw a fatal PHP error because of a redeclaration of a function called show_message(). I used this function in my theme, but apparently it has been created as well in the new 2.7 installation so it gave a conflict.

    The solution is pretty simple: rename all your theme functions to something that doesn’t exists in WordPress, such as puttinng your themename before the function (e.g. mytheme_show_message() instead of show_message()) and replace all calls to the function in your theme.

    2.7 works like a charm now!

    Thread Starter Husky

    (@husky)

    Tried removing everything but wp-content/ and re-installing, deleting all cookies, removing my .htaccess. Nothing 🙁

    Afaik, the upgrade.php script hangs when trying to include the upgrade.php file in wp-admin/includes/upgrade.php

    Thread Starter Husky

    (@husky)

    Nope, that doesn’t work. I get to the admin screen and i get the ‘Are you sure you want to logout?’ message. But after i enter my username and password and press login i am redirected to:

    http://www.haykranen.nl/wp-admin/upgrade.php?_wp_http_referer=%2Fwp-admin%2F

    And i get the blank screen again…

    The new Flash 10 plug-in breaks the upload button. See http://trac.ww.wp.xz.cn/ticket/6979. Try using the ‘Browser uploader’ or use an earlier version of Flash.

    Thread Starter Husky

    (@husky)

    Well, i think i fixed the bug. Here’s what i did:

    1) change the default collation and character encoding of MySQL to utf8_general_ci
    2) Export the whole wp_posts table, remove all references to latin1 (so that the db automatically uses the now default utf8 encoding)
    3) Re-import the whole thing again (make sure to DROP the table ‘wp_posts’ first)

    This lead to two problems: the ë (e with an ‘umlaut’) still displayed as ? so i did a search-and-replace across all ë characters, converting them to ë. Furthermore, the text editor i was using (Programmer’s Notepad) had some problems with UTF-8 too, so i used MadEdit instead to do the search and replace. Everything seems to be working fine now. Thanks for your input!

    Thread Starter Husky

    (@husky)

    Ok. I’m getting a bit confused now 🙂 What is the difference between a ‘collation’ and a ‘charset’ in MySQL? And which of the two relates to the character encoding in the HTML file?

    Thread Starter Husky

    (@husky)

    Moshu, i’m a bit riddled by that as well. It’s just after i exported the SQL file and stepped trough it in an editor that i noticed the differences. Some posts are encoded in UTF-8 (with weird characters), while others are in latin-1 (where the accented characters remain ok).

    Whenever i test it on a local installation of WP and set my character encoding to UTF-8, those firsts postings appear correct and the latin-1 encoded ones do not, and vice versa. It could also have something to do with a difference in how i set things up locally in MySQL and how things are set up at my host.

    And samboll, i guess that works fine for most of us (it did for me too), but it seems weird to me that the database is latin-1 and the character encoding is utf-8.. I don’t know, maybe i still don’t know enough about character encodings 🙂

    Thread Starter Husky

    (@husky)

    Yeah, i tried that. The problem is that encoding utf-8 again makes it double-encoded, meaning that every single character is encoded again, making it garbage in the process.

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