Commenting Fixed
May 25, 2007 | 4:39 pmI upgraded to Wordpress 2.2 a few days ago and thought I didn’t break anything. Rob, however, pointed out that I broke something(as usual): I broke my comments. Thankfully, without having to get me to tear out a lot of hair so as to why the heck on earth I was getting duplicate primary key fields in the database, Rob also pointed me tothis articlee to fix it. Works like a charm.
So, if you’ve tried to leave a comment over the past few days, I’m sorry for the abusive page containing obscure words that you encountered. It should be fixed now.
So, well, uhm, Thanks Rob!
[...] YuviSense: Kid in Tech » Blog Archive » Commenting
STUFFLEUFAGUS » Blog Archive » YuviSense: Kid in Tech » Commenting Fixed | May 25, 2007 | 4:46 pm[…] YuviSense: Kid in Tech » Blog Archive » Commenting Fixed digg_url = ‘http://lagesse.org/index.php/2007/05/25/yuvisense-kid-in-tech-commenting-fixed/’; […]
With Subscribe on.
Rob La Gesse | May 26, 2007 | 1:07 pmWith Subscribe on.
And did you recieve this email?
yuvipanda | May 26, 2007 | 1:08 pmAnd did you recieve this email?
[...] to update to Freshy 2.0 theme. Went awry (as
YuviSense: Kid in Tech » Blog Archive » Theme update gone awry | May 27, 2007 | 4:16 pm[…] to update to Freshy 2.0 theme. Went awry (as usualy). I can never seem to upgrade anything without breaking something. This time, I was unable to use any widgets: Accessing the widgets page and hitting […]
[...] instead of the correcter inevitable, and then using the
YuviSense: Kid in Tech » Theme and Blog name changed | May 28, 2007 | 1:12 pm[…] instead of the correcter inevitable, and then using the non-existant word “correcter”, breaking the comments when upgrading to Wordpress 2.2, and then screwing up a lot of things while trying to activate the […]