It’s been awhile since my last blog update adventure and while I was expecting a smooth upgrade from version 2.2.2 to 2.5, things turned out quite differently. It’s also worth noting that I was on Brinkster’s Windows Pro hosting plan which means IIS and PHP 5.2.3.
Part 1
The first sign of something broken were the few lines of cryptic error messages appearing at the top and bottom of the upgrade.php page.
"Undefined index: PATH_INFO" in wp-settings.php
The simple fix was to comment out the lines of code in wp-settings.php (lines 71-74 if I remember correctly) that tried accessing the PATH_INFO server variable.
Now after proceeding to upgrade the database, which was successful, more cryptic error messages appeared at the top and bottom of the page:
Undefined index: REQUEST_URI in wp-settings.php
After much Googling, it finally dawned on me that Brinkster might not actually be using the PATH_INFO server variable that is used to populate the REQUEST_URI server variable. Instead, they were using ORIG_PATH_INFO, so the simple fix this time was to apply the following code over lines 71-74 of the wp-settings.php file.
I’ve also posted a solution here, which would be helpful if you want to follow a discussion on the issue and check out solutions for non-Brinkster related hosts.
Part 2
Ok, so now it seemed like everything was up and running smoothly and I was about to bask in the satisfaction of another successful, albeit long overdue, upgrade. Clicked on a link to a post, and I was hit with a 404 error. What? Clicked on some other posts, 404. My pages, 404. Categories, 404. Calendar, 404. Not only were all my permalinks were broken, everything else was too! Except, of course, the link to the Site Admin page which didn’t require any special URL rewrites.
After mucking around with permalinks and more Googling for a good 2 hours plus, it finally dawned on me that only the default yucky http://www.pagesofink.com/?p=123 style links would work. Not good, considering a lot of links to other posts in my blog and from other blogs use the http://www.pagesofink.com/index.php/archies/post-name format. No other code hacks like this one here worked and I was getting desperate to the point of considering other hosting providers like Dreamhost.
In a final last-chance attempt, I contacted Brinkster Live Support to ask if I could have my subscription migrated to an equivalent Linux package. Surprise surprise, they were very obliging and had it all done within the hour. Now, I’ve been using Brinkster for a long time now, and if there’s anything good about them, it’s their Live Support. Live Support is cool because you get to chat real-time with an operator online and they are usually very helpful and responsive. As much as I complain about Brinkster, I must admit their Live Support have pulled me out of a couple of jams in the past. Plus, it sure beats e-mail as you never know when the next response is coming.
Part 3
Now that I’m on Linux and having been given the assurances that the Linux Apache webserver comes with the necessary mod_rewrite plugin for pretty permalinks to work properly, I was full of anticipation that I would be out of the woods soon enough.
So I give my .htaccess file proper write rights using the chmod (777) command in my FTP client and browsed to the permalinks settings page (wp-admin/options-permalink.php) hoping to put my permalink misery out for good, when all of a sudden I’m faced with 500 errors. Everywhere. Even the Site Admin pages.
Argh
Now, sparing the painful details of how I narrowed this down, it appears that Brinkster does not like you to play around with the .htaccess file. Period. Contrary to what Wordpress tells you, do not go and manually put the following settings into the file:
# BEGIN WordPress
<ifmodule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</ifmodule>
# END WordPress
The Brinkster default .htaccess file looks like this:
# -FrontPage-
#IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<limit GET POST>
order deny,allow
deny from all
allow from all
</limit>
<limit PUT DELETE>
order deny,allow
deny from all
</limit>
AuthName inkyneil.brinkster.net
AuthUserFile /sites/blah/inkyneil/home/public_html/_vti_pvt/blah.pwd
AuthGroupFile /sites/blah/inkyneil/home/public_html/_vti_pvt/blah.grp
You simply need to change it to:
# -FrontPage-
#IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<limit GET POST>
order deny,allow
#deny from all
allow from all
</limit>
<limit PUT DELETE>
order deny,allow
#deny from all
allow from all
</limit>
AuthName inkyneil.brinkster.net
AuthUserFile /sites/blah/inkyneil/home/public_html/_vti_pvt/blah.pwd
AuthGroupFile /sites/blah/inkyneil/home/public_html/_vti_pvt/blah.grp
So, it’s one last trip back to the permalink admin page to update the permalink structure. Lo-and-behold, everything finally works and is back to normal.
Seriously, that was way too much work just to upgrade Wordlress. Now, to get email working (Brinkster has got certain restrictions with phpmailer), upgrade my plug-ins, find a new theme, and I’m all set!
Popularity: 30% [?]
Entries (RSS)
Wow, so geek!! Do u website supports RSS?
I also have Brinkster IIS hosting package and I\’m working on Wordpress 2.5. I\’m a pretty big beginner with php and wordpress (although I\’ve doing a wordpress blog for a year). I also really wanted pretty permalinks. Thanks for the info for getting it to work. Here\’s my question for you: is it worth swtiching to a linux server? I also have that option, but the htaccess changes sounds like a lot of work, and I really don\’t want to mess up the blog.
Soo Guan - Yup! If you scroll all the way down to the bottom of the page, you will see a link to subscribe by RSS.
Rebecca - I held back from switching over to Linux because I thought I’d like to host a bit of ASP or ASP.NET stuff but it’s been 2 years and after hitting so many issues with Windows Hosting and Wordpress, I decided to just make the jump. So far so good I must say! The biggest benefit is that pretty permalinks just work without having to rely on php.ini hacks like before. The .htaccess change is really straightforward and you only have to do it once. I’ll be more than happy to help out if you find it daunting.
Thanks for the info….Since my husband also uses the same domain and he doesn’t care about pretty permalinks and the wp-settings tweaks, it looks like we’ll stay with Brinkster IIS for now….but we’re still looking for a new host for the long run!
I was writing my latest article and I found your most loving pictures of your daughter!
I’ve since moved to a new web host this month and I don’t have too much problems technically on my part, except that for the host, I need to make them work hard to resolve some issues that shouldn’t have exist because of their misconfiguration.
I’m very particular about security so I keep regular updates, backups and all kinds of upgrades.
I’ll be exploring new web host again soon. Let me know if you like some updates so that I can do some write ups when I’ve gotten new findings.
PS: CAPTCHA has already been cracked and there are reports of botnets exploiting that property for their lucrative spamming activities.
Rebecca: Do let me know how your experience goes if you ever decide to change! I’d be pretty curious as I was tempted to try Bluehost and Dreamhost at one point with only the lack of Live support putting me off.
Wai Loong: Thanks for visiting! I found your post on what’s inside the Istana very interesting too as I’ve never gone in myself. I must make it a point to visit one of these days. Just curious, did you see anyone else inside taking pictures with a DSLR? I’m just wondering if that’s allowed considering how paranoid people are today about security.
As for that “special DSLR lens”, I was using an 85mm f/1.4 which is really suitable for portraits as the large aperture (f/1.4) and moderate focal length (85mm) really help to isolate the subject from the background, thus making the photo “pop”. Let me know if you’re curious to know more and I’ll be glad to elaborate.
Oh, and yes, I’d love to hear about your experiences with other web hosts if you do decide to switch. I’ll probably be making some updates on how the Brinkster Linux hosting is getting along too though no news is good news! On the CAPTCHA, it’s been surprisingly effective for me as I don’t get any spam at all with this plug-in enabled. I guess if my blog were really popular, I’d have to beef up security.
So, I currently am having trouble tracking down the .htaccess file. Where might this be?
Alright, I got it worked out
I had to create an .htaccess file in the root wordpress directory. Brinkster support informed me it needed to be in the public_html directory, and thus my issues. Thanks for the help!
Nathaniel: Glad you got that worked out!
Well, to soon to say if it’s good, but at least it’s well designed.
I mean I thought I would be blocked after adding some interests, but the site helps you to add more.
Cheers
wholesale watches
wholesale watch
replica watches
watches replica
replica watch
watch replica
fake watches
fake watch
cheap watches
rolex replica
replica rolex
replica rolex watches
replica rolex watch
fake rolex
breitling replica09.07.03T