The upgrade to WordPress 3.0 doesn’t appear to have broken anything? Good.
It pointed out my Tarski theme was a point revision behind. That has also been upgraded. No apparent problems.
No need to go mess with code. That makes me verrrry happy.
You are currently browsing the archive for the Wordpress category.
My hosting service, Dreamhost, announced they would be upgrading every one off PHP4. Only people using old software would get bitten. I’ve kept my software current, so I wasn’t worried.
Only this of all eight domains started showing an HTTP 500 error (Internal Server Error). I dreaded having to go through and determine why. Turns out it was easier than I thought…. In Dreamhost’s panel, the domain was still configured to use PHP4. When I changed it to use PHP5, the WordPress started working again.
I would have thought part of an upgrade would be to change this configuration. At least it was just a simple change and not digging through code and logs.
Related posts
I noticed today comment spammers are getting craftier. Some of the comments I approved I now believe to be comment spam. Perhaps they are probing to later deliver the real deal?
They use the name of people who legitimately commented. Because the scammer cannot see the real email commenter’s address, they use a different one but nothing drastically obvious as spam.
The IPs are 74.63.104.125 and 74.63.104.121. The legitimate comments have different IPs. These IPs belong to FDCServers, who provide colocation and dedicated servers. I’m tempted to send a message to the abuse email address for the company.
For now I’ve renamed the spam comments as ” (Fake)” and removed the web site. I’ll have to be more vigilant.
Related posts
I imported all my LiveJournal posts here. Other than posting pictures to there from Flickr, I don’t really use LJ anymore. I rarely even read my friends’ blogs there. Too bad. I still have the teeshirt.
Most of my LJ posts are protected. For this site, I’d rather have them set to private. So the section of WordPress (Tools > Import > LiveJournal) saying this seemed relevant:
If you have any entries on LiveJournal which are marked as private, they will be password-protected when they are imported so that only people who know the password can see them.
If you don’t enter a password, ALL ENTRIES from your LiveJournal will be imported as public posts in WordPress.
Password protected seemed better than not, so I set a 30 character long password, and the form accepted all 30. When the password didn’t work, I logged in as the administrator user and looked at Publish > Visibility >
In my opinion, web forms in general should prevent the user from entering more characters than the application or database will take. Passwords are very exact, so forms for creating them definitely should not allow extraneous characters.
Related posts
Followed Andy Fore’s instructions on adding WP 2.9 to the whitelist.
The only problem I have so far discovered is Tag the Net doesn’t appear to work. The error:
Fatal error: Cannot redeclare class services_json in /home/path/wplog/wp-includes/class-json.php on line 115
Looks like WordPress distributed a new class-json.php. Back in Simple Tags 1.6.5, this specific error was supposedly fixed. My guess is something about WordPress 2.9 re-broke it.
Related posts
At the request of my boss, I added this disclaimer. Positive things I say here about Blackboard are okay. Negative things require distancing my employer from me so the defamation lawsuit comes to me not them.
This is a personal weblog. The opinions expressed here represent my own and not those of my employer.
Related posts
Blog
Upgraded to the Tarski 2.5 theme. Previously I was using the Tarski 2.4.
One of the reasons I like Tarski is the opportunity for a custom header image. Something I can use of my own. However, like the moo.com cards, finding a photo whose crop to this narrow 720×180 window isn’t so easy. At the moment I am using the train photo. Through the weekend I might try new photos.
Original Tarski Custom Header
Consideration one from my train photo.
Consideration two from my Queen Anne’s lace photo.
Consideration three from my mushroom photo.
Consideration three from my phlox photo.
Leave a comment if you see something you like.
Splash
I’m thinking of putting the above photo into the splash page as well.
The tacky Facebook profile widget got tackier. So now I have a Flickr widget for a slide show of my Most Interesting 60 photos. So, ya’ll visit the set of the strobist shoot to increase the Interestingness of your favorites into the top 10.
Related posts
Purely for fun. Typealyzer gives a Myers-Briggs Type Indicator result from analyzing the text in your blog. I find it interesting this blog scored an ISTP and another INTJ. Prior to working in IT, I was always an INFP. Then I started getting INTP and lately INTJ. So the ISTP is a little odd to me.
ISTP – The Mechanics
ISTP: The Mechanic
The independent and problem-solving type. They are especially attuned to the demands of the moment are masters of responding to challenges that arise spontaneously. They generally prefer to think things out for themselves and often avoid inter-personal conflicts.
The Mechanics enjoy working together with other independent and highly skilled people and often like seek fun and action both in their work and personal life. They enjoy adventure and risk such as in driving race cars or working as policemen and firefighters.
UPDATE 2010-MAR-06: In retrospect, this makes quite a bit of sense to me. Since my profession is a technician, the mechanic, is a perfect archetype for my work. This blog mainly reflects my work, so the mechanic is the best archetype to achieve.
Related posts
Problem PHP in Yet Another Photoblog causes “Warning: Division by zero in exifReader.inc on line 859” (the problem line is in bold):
case TAG_SHUTTERSPEED:
// More complicated way of expressing exposure time, so only use
// this value if we don’t already have it from somewhere else.
if ($this->ImageInfo[TAG_EXPOSURETIME] == 0){
$sp = $this->ConvertAnyFormat($ValuePtr, $Format);
// Temporary Workaround for divizion by zero problem
if (!empty($sp[0])) {
$this->ImageInfo[TAG_SHUTTERSPEED] = (1/exp($sp[0]*log(2)));
} else {
$this->ImageInfo[TAG_SHUTTERSPEED] = 0;
}
}
break;
Looks like YAPB is attempting to create a value if one doesn’t exist for TAG_EXPOSURETIME by inventing a new value. In my problem picture, the exposure time is 0.003 seconds which != 0. So why is the ($this->ImageInfo[TAG_EXPOSURETIME] == 0) condition evaluated as true?
Interestingly, just prior to this is some code dealing with TAG_EXPOSURETIME which seems to be affecting this. Changing the 0.5 to 0.0005 (less than my current value removes the problem.
case TAG_EXPOSURETIME:
// Simplest way of expressing exposure time, so I trust it most.
// (overwrite previously computd value if there is one)
$tmp = $this->ConvertAnyFormat($ValuePtr, $Format);
$this->ImageInfo['h']["exposureTime"] = sprintf(“%6.4f s (%d/%d)”,(double)$tmp[0],$tmp[1][0],$tmp[1][1]);
if ($tmp[0] <= 0.5){
$this->ImageInfo['h']["exposureTime"] .= sprintf(” (1/%d)”,(int)(0.5 + 1/$tmp[0]));
}
break;
With this conditional, the exposure time is “0.003 s (1/400) (1/400)” without “0.003 s (1/400)”. Didn’t see a reason to have it twice, so I’ve dropped it.
Also, I figure it would be better to call ImageInfo['h']["exposureTime"] instead of ImageInfo[TAG_EXPOSURETIME]. With this change, it seems to have resolved the issue for me.
Related posts
FeedBurner
Blog:
Comments:
Comment Spam Resumes
May 30, 2009 in Wordpress by Ezra S F | 2 comments
Have spammers figured out how to pick reCAPTCHA‘s lock? All of a sudden I am getting hundreds of comment spam blocked by Akismet. When I added reCAPTCHA, it dropped to a few a month. Now 409 in a week.
Guess this is why layers of security are good.
UPDATE: Scanned through for false positives. The first word of many of them were Xanth characters: Bink, Chameleon, Dolph, Iris, Smash, Goldy, Grundy, Cherie, Chester, Roogna, Imbri.
Related posts