Testing WordPress for Blackberry App

I’ve been testing the official app for blackberry phones from automattic for a day or so now. This post serves as a way to test the posting functionality of it as well as to give a preliminary review.

Some initial thoughts. The downloading and installation went very smoothly. Setting up a blog (or blogs) was pretty simple as well. I did run into an issue because the app automatically defaults to use the device memory instead of a memory card. Maybe that’s necessary, but my device memory filled up before I could really do anything of value. Also, once I figured that out, I had to completely redo the setup as the app didn’t move the data over to the media card.
As yet, I haven’t really seen the auto update part work. Whether that’s due to some slow weekend days, or the app is unclear at the moment.

So far, I see the app as something that will likely be sticking around my blackberry. Its nice to have when waiting someplace. I can just type a draft or publish. It also gives me abilities for comment moderation, which could be super handy.

Added/Update: the posting of a post isn’t very intuitive, but I was able to figure it out. Formatting isn’t all that great either. Still worth using though.

WordPress 2.8.5 Available, May Break Some Sites

The newest release of WordPress is now available.  After the hullabaloo that surrounded the 2.8.4 release, I figured it would be a good idea to upgrade asap and get it over with before some exploit or another decided to rear it’s ugly head.  I dislike upgrading.   Mostly because the super-uber convenient auto-update feature in WordPress only works in about half of my blogs.  Why?  I don’t know for sure, but my guess would be that it has something to do with the hosts.

In any case, I normally have to download the files and upload them for at least a few of the sites, so I usually just do it for all and have one procedure instead of two.  Easier? No.  But easier on my mind. 😉

Long story short, a fair warning for those of you that haven’t upgraded yet.  It may break your site.  It broke this one for a little while.  In my case, the breakage was due to my storing the WordPress files in a subdirectory and having the actual site in the main directory.  WordPress didn’t update the index.php in the main directory and since there were some changes to the index.php file this go ’round, it wouldn’t load.  After manually replacing the index file with the new one, I then got some nice “file not found” errors from WordPress/PHP.  It was an easy enough fix as well, as all I needed to do was add the subdirectory into the path that it was looking for the files in.  And viola!  One working site done.

Luckily, this is the only site I run that I have set up this way, so I shouldn’t have that problem with any others.  But, for those of you that have sites like that, there’s the fix.  Or, at least, a workaround.

Mysterious Truncated WP Files

Early today, I noticed that one of my sites that gets 600-1000 hits a day had barely gotten to 20.  I didn’t think too much of it as most of the traffic is from search engines (read: The Great Googely-Moogely.) and the site has been de-indexed before.  It happens.

However, tonight, I tried to go to the site to check a few things and all I got was a nice WP PHP error.  If you run WP, you know exactly what I’m talking about.  So, being the amateur coder that I am, I did a quick FTP download of the file that was spitting out the error and went a looking.

I’m not entirely sure how this happened, but the file had been truncated.  The file, in this case, was the wp-load.php file.  Normally, it has about 50 lines.  The copy that I downloaded from my site had only 48.  The last couple of lines weren’t there.  I know they were there yesterday, because the site got about 600 hits.  But, all of a sudden, they just up and disappeared in the middle of the night.

I’m hoping it isn’t some perverted way of hacking the site, but I didn’t see anything funny once I got the site back up.  Which I did by just re-uploading all of the files except the wp-config.php file back into the index directory.

Has anyone experienced this?  It’s quite strange.  How about a good explanation of what might have happened?  I’m scratching my head here.

alinks plugin and wp-admin issues

Since about Thursday afternoon, I’ve been unable to log into my admin side of this site in order to approve comments or write articles.  After much looking and troubleshooting, I’ve figured it out and am back in.  It would seem that the alinks plugin was having issues.  I’ve deactivated it and now everything works as would be expected.  I haven’t been using the alinks plugin all that much, so I probably won’t miss it too badly, but if anyone has a fix for the issue, let me know.

It doesn’t seem to be related to the wordpress version as I believe it may have been the same issue that I was having back in March while still running 2.3 and now with 2.5 and 2.6.  It also doesn’t seem to be an absolute thing either as there were no changes made and then it just all of a sudden stopped letting me log in.  Freaky.  Now I’m wondering if I should preempt the issue and pull the plugin from my other sites as well.  Oh, and to top it all off, the homepage for the plugin seems to be gone or at least doesn’t load, so it may be the end of the road for alinks.

Off to search for a replacement plugin.  Got any good ones?