Posts Tagged ‘wordpress’

WordPress Archive Permalink Problem — no solution

Thursday, August 7th, 2008

Update: SOLVED! Dagnabit! Apparently, disabling ONLY my Robots Meta plugin did the trick! Db0 is my lifesaver!

ahhhh!!

A warning by Google Webmasters alerted me to a problem I didn’t realize until quite recently. I have tried for the past three days to figure out why my monthly Archives link stopped working the way it suppose to. Have a look at my sidebar, scroll down until you see my Archives section, and click on, let’s say, my March 2008 posts archive. You’ll notice that it does a redirect to my main index page, instead of listing out the posts for March 2008. Strangely, my Categories and Tags permalinks are working as normal.

I’ve tried the following fixes that I found when scouring the Web to solve this:

  1. Adding “/category” and “/tag” in the Categories and Tag permalink setting. I did that, but the problem didn’t run away.
  2. Resetting the Permalinks to default. Nope, that didn’t repair the Archives, either. Again, Categories and Tags, as well as single posts and pages reflected the default setting and worked.
  3. Inserting “/index.php” before the custom and default permalink. Didn’t work, either. Besides, I’m using a Linux hosting, and index.php is usually used as a fix for those hosting under Windows.
  4. Disabled all my plugins. Every last one of them. That didn’t work.
  5. Reset my .htaccess file. I backed up my original .htaccess file, emptied out the one in the server, and got the WordPress Permalinks do a fresh rewrite on the server’s .htaccess.Though the fresh Permalinks setting appeared in the .htaccess files, my Archives links still didn’t work.
  6. Overwrite wp-includes/rewrite.php to those in versions WP2.3.3 and WP2.5, fixes and otherwise. That just caused my blog to be ridden with so much call function errors, so obviously that didn’t work, either.

I’m at a loss. I’d like to downgrade to WordPress 2.3.3, but I didn’t have my version 2.3.3 database backup, and I dread what happens if I do downgrade. I expect it will break everything in my blog.

Sheesh. I made it clear here and here how much I disliked these recent “improvements” that were done since WordPress 2.5, and I should have stuck to my guts on staying with WP 2.3.3 if I were not so worried about missing out on all those security patches.

What frustrates me the most is that I tried to recreate the problem in my local sandbox to no avail! Don’t tell me that after all these while I thought I was expert enough in WordPress, my brain has now regressed to a WP level n00b!

HELP!

One favourite time-saving plugin: Instant Upgrade

Thursday, January 17th, 2008

Instant Upgrade: Upgrade your WordPress-Installation with one simple click.

This is one of the plugins in my blog I could never live without. I installed it just before I went into a blog hiatus about 3 months ago. I used to do my WordPress upgrades manually, by FTPing to and fro my server. Instant Upgrade helps me to do that in about 0.001 seconds. The interesting part about this plugin is its ability to downgrade to a lower version of WordPress should you choose to do so, although I haven’t personally tested it myself for fear of a database screw-up.

Alex Günsche did a good work on this simple plugin. I’m sure there’s a few more WP upgrade plugins out there that works as well or better than Instant Upgrade, and I have tried two others, both didn’t work at all.

A smart and foolish move with WordPress plugins

Wednesday, October 10th, 2007

I have been working on two main things for the past two months — frantically doing sponsored posts, and fiddling with more WordPress plugins.

Installing the Math Comment Spam Protection has definitely been one of the smartest moves I’ve made with my blog. Not only was it easy to install, but the spam comments Akismet captured made a staggering drop from 50ish a day to only one every other day! Another good thing that comes with installing this plugin is that I don’t have to moderate my comments anymore, and my commenters can get the instant gratification of immediately seeing their comments posted. Now I have more time to bloghop and make more dough.

I didn’t pay much attention with the new features that were to be in WordPress 2.3, so I couldn’t help but curse myself when I found out — after upgrading to WP 2.3 — that the new version comes with a built-in tagging support. Sheesh, if I had known, I wouldn’t even bother installing Ultimate Tag Warrior two weeks prior. For the sake of supposedly improving my blog SEO, I had to endure some temporary brain cramps as I tried to understand why in the world I would need to activate three UTW plugins in my dashboard, and looked through the unending options I had to go through. I just find UTW to be a hassle, and ultimately my bad experience with UTW prompted me to remove it, and to stick to the simple tagging option.

I’ve only slowed down in my WordPress plugin tinkering this week (due to my next big plan on making money) — I should update the WordPress Plugin I Use page after this.

My Top Commentators Widget: Quick & Dirty

Thursday, February 8th, 2007

Updated 24/Jul/2008: Download Top Commentators Widget v.1 (refer to the README for customization). And, yes, it works with WordPress 2.6.

Holy Molly, I never thought I’d make one so soon, but it’s true! I’ve created my very first WordPress Widget!

Yeah, well, not exactly. I adapted this Top Commentators Widget from the actual Show Top Commentators (hereto known as STC) plugin by PFA. Here’s actually what happened:

  1. Went to Giuk.Net as usual, saw MrBadak talking about his newly installed plugins, and I hopped by.
  2. Excitedly surfed into Personal Financial Advice to download the STC plugin.
  3. Followed the instructions to the dot, only to find out later that it won’t work if you have Sidebar Widgets activated.
  4. Googled for a widgetized version of STC, only to find that the download links don’t work.
  5. Desperately needed to install it, so I did the next best thing a desperate grrrl would do — build one.
  6. Accidentally sacrificed a few other widgets due to carelessness, but nevermind as I always back-up.
  7. Destabilized my site with countless access error messages and loads of SQL warnings.
  8. Trying so hard to stay true to the original codes, only to surrender at the last minute and decided to strip down most of the original codes off, therefore FINALLY COMPLETING MY MISSION!

But wait…. (more…)