Meanderings and punditry by a computer scientist with penchant for journalism, education, and politics
I’m having some issues with WWL and mightyadsense javascript showing up in feeds. I’m gonna troubleshoot it this weekend when I’ve got a spare hour or two.
Worse case scenario: I disable both and find a replacement for mightyadsense. I’d re-enable WWL when the problem is fixed in the new version.
Update: I’ve fixed at least the WWL problem. The mightyadsense problem occurs far more infrequently, so it might take a while.
Since I fancy myself a linguist of sorts, I’ve added the Worldwide Lexicon plugin to my WordPress installation. It adds a small, dynamically-loaded bar to the beginning of every post allowing people to translate it or see a version of the post in their own language. I’d like to see this plugin become more customizable, as I don’t particularly care for the placement or look of it. Substance >> style.
WWL needs to add Esperanto, too.
Esperante:
Ĉar mi imagas min esti lingvisto iom, mi aldonis la «Tutmonda Leksikono» kromsoftvaron al mia Vortpresilo instalaĵo. Ĝi aldonas malgrandan, rultempan trajton antaŭ afiŝoj permesi uzantoj traduki ĝin aŭ legi version de afiŝo en ilia lingvo. Mi ŝatus vidi uzantojn povas agordi ĉi tiun kromsoftvaron ĉar mi ne zorgas por loko aŭ apero de ĝin. Substanco >> stilo.
TL (WWL) bezonas aldoni Esperantan lingvon, ankaŭ.
If you haven’t heard already, WordPress’s production server got hacked a couple days ago, and they discovered it today. The cracker put a backdoor into some of the administrative files.
Anyway, it’s been fixed in the newest release, so you should go get it now.
Oh, and thanks to John Chow for pointing it out.
Aaron Brazell of Technosailor posted a brief overview of the new features in and other things to merit upgrading to WordPress 2.1, which is to be released tomorrow.
$tableposts, $tablecomments, etc.I noticed just now while reading John Chow‘s blog that WordPress 2.0.7 has been released. It’s only a couple of files:
Run along, my blogging bretheren, and get it!
Dear WordPress developers,
Please make it so that my posts don’t disappear if I accidentally click on a link or browser bookmark and then hit the back button.
Love,
A blogger who just lost a three-page post because he accidentally clicked on a bookmark
A new release of WordPress is out. There’s quite a new security fixes, so you should probably get it ASAP. I’ve already upgraded—no problems here.
I had a serious problem with this installation of WordPress because I was getting blank pages while using wp-cache2.
The fix is to change ob_end_clean(); to ob_end_flush(); on or around line 220 of wp-content/plugins/wp-cache/wp-cache-phase2.php.
This simple sed script will do it for you if you can access your WordPress installation at a command line: sed -i 's/ob_end_clean/ob_end_flush/g' wp-content/plugins/wp-cache/wp-cache-phase2.php. Make sure that you’re in the base directory of your WordPress installation.
I found the fix for this at the WordPress support forums.
