A big issue after upgrading WordPress installations is the matter of apostrophes appearing as ‘â€TM’ –stupid junk characters. Most of the time there is a simple solution, at least in cases I’ve dealt with.
To fix this, just jump into your wp-config, and comment out two lines:
define(”DB_CHARSET”, ”utf8”);
define(”DB_COLLATE”, ””);
If you don’t know what I mean when I say “comment out,” it is the use of “#” or “//” which simply tells the interpreter to block everything that is on same line to the right of the comment.
So you endup with:
#define(”DB_CHARSET”, ”utf8”);
#define(”DB_COLLATE”, ””);
Very effectively written information. It is going to be worthwhile to anyone who usess it, including myself. Sustain the nice work – for certain i’ll take a look at extra posts.
Thanks a bunch for making the effort to explain the terminlogy for the newbies!
Thanks Luis, can you give us any information as to why this works?
The simplest answer is that WordPress added two new lines to the wp-config.php file in version 2.2, so if you upgrade the installation (and not use a new wp-config file,) the useless lines get tossed in. Deleting them would work just as well as commenting them out, I just try avoiding people deleting the wrong lines and screaming at me when things go wrong, commenting the lines out can leave room for mistakes/adjustments.