Posted 1 year ago #
I got a big problem
I have upgrade 3 weeks ago my blog - all good !
I have updated my personnal blog today - BAAAD !
-- The database got updated... that have made me lose all ma french accent caracter. Ex: Journée is now Journ@#$e
-- Plus I cant login anymore, no admin section for me anymore. The password xxxxxx dont seem to help more
HELP !!!
Clear your cookies. Also try a different browser.
Posted 1 year ago #
that doesnt do nothing
maybe the process did touch my DB ??
Here's some things to try:
1. logout or logout with http://www.yourdomain.com/wp-login.php?action=logout
2. disable all plugins--if necessary read How to deactivate all plugins when not able to access the administrative menus?
3. clear cookies
4. exit browser
5. make sure local firewall is not causing problem
6. login with http://www.yourdomain.com/wp-login.php
If WordPress is installed in something other than the root folder please take that into account for the above url examples
Please let us know what does solve your problem.
Posted 1 year ago #
Thanks MichaelH
I did whats you wrote. No I am able to login inside my blog CP as admin. THANK YOU !!
1 on 2 is solved.
But still have this caracter corruption problem... What is this ? How can I go back in the process and get rid of all those weird replacement caracters like showned post above ?
Those caracters replacing my french accent appears inside my blog posts/textes AND inside my admin control panel when I go to Manage-Posts.
If you upgraded from a pre-2.2 blog you may need to delete the following lines in your wp-config.php file:
define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');
Posted 1 year ago #
ok, good to know (really, i wish i knew that before. I didnt saw this written)
So how can I go back and correct this ?
Do i just re-upload the config.php and retype the url for upgrade.php ?
Or do i need to do something else ? Maybe something wiht my database...?
If that was a pre-2.2 upgrade then you should be able to just delete those lines from your wp-config.php file.
Posted 1 year ago #
yes, i did deleted them easily on my computer... but now, what do I do ?
A -- Do i just re-upload the config.php and retype the url for upgrade.php, and eveything will get i place by itself ?
B -- Or do i need to do something else. Maybe something with my database... wich is the one that seams affected ?
If your blog was created before WordPress 2.2 then you should not have those two 'define' statements in your wp-config.php file, so you should be able to just delete them and that's it.
Resources:
Database character set discussion in Editing wp-config.php
Database collation discussion in Editing wp-config.php
Posted 1 year ago #
thanks a lot for helping me here MichaelH, but the part i need an answer is now that it is already done, already messup, those funky caracteres are alreday there in my blog for my past posts... what do I do to go back in time and fix that bug ? As I read your text, i see that you are talking like if i don't have this bug yet, like a prevention... wich i do have presently, look : www.polarmedia.ca/blog
yes, i did deleted them easily on my computer... but now, what do I do ?
A -- Do i just re-upload the config.php and retype the url for upgrade.php, and eveything will get i place by itself ?
You definitely have to upload the file you deleted the 2 lines from - to your wordpress root.
Posted 1 year ago #
thanks guys. I never wrote those lines by the way, they where there alreday. Maybe it happened because my original version (auto-installed by the host) was to old, who knows...
Ok, so i will reuplaod the wp-config file and rerun the update and my database will get fixed that way. I will put a note here after this action.
Posted 1 year ago #
Thank You so much MichaelH and the others !!
All that time I was understanding that the problem was "inside" my database, that the upgrade, when WP says DB upgrade, had corrupted my DB, and so that's why I was trying to resolve "that" problem... wich was not that one at all but only :
open wp-config.php (downloaded form your ftp)
delted those two lines (define('DB_CHARSET', 'utf8');
define('DB_COLLATE', '');)
re-upload by ftp
refreshEverything got back on place by telling the good caracter set, lol.
This topic has been closed to new replies.
