We have a special deals section where I created some customized pages to present deals available to our readers. I just noticed that there was a problem with one of the pages. The pagination does not work any more. Here is a screenshot of the pagination of my page.

When I created these pages, I used “page” as a variable in the query string. For example, to go to the sale page #2, I have this as the URL:

http://www.kombitz.com/sale/?page=2

This stopped working after I upgraded to WordPress 3.4. This puzzled me for a while, until I noticed whenever I click on the URL, the system changes the URL to

http://www.kombitz.com/sale/2/

This, of course, does not work with my script. The workaround is actually quite easy: just don’t use “page” as a variable in the query string. I changed the variable from page to page_number, and my scripts are working once again. The updated query string is like this one:

http://www.kombitz.com/sale/?page_number=2

When I came back from my vacation last week, I found that I can no longer log on to the wp-admin of my site. I was freaked out at first and I thought the site got compromised or something. Google search did not find anything useful.

I finally contacted my hosting company, Blue Host, for support. They fixed my problem quickly. The culprit is the Supercache plugin. The plugin created rewrites on the .htaccess file. One of the rewrites caused the domain to redirect to a 404 error instead of loading the wp-admin page.

Earlier I had some issues with Blue Host’s support, but after this incident I am a loyal customer again.

WordPress 2.8 is out and I first tested it on my test site. The automatic upgrading was fine on my test site. I then tried to upgrade my production site. I got this message when I tried.

Fatal error: Allowed memory size of 33554432 bytes exhausted

It seemed like WordPress uses too much memory and it cannot do the automatic upgrade. I figured that it’s possible I have too many plugins running. I tried to de-activate some of non-essential plugins and I was able to upgrade it afterwards.

The other way to fix this problem is to edit the php.ini file in the wp-admin directory if you have one. If you don’t have a php.ini file, ask your web hosting company to create one for you. Edit it and find the line like this.

memory_limit = 64M ; Maximum amount of memory a script may consume (32MB)

The default is 32MB, I changed it to 64MB.

I recently upgraded my AdRotate plugin from 2.1 to 2.2. After upgrade, I found that the ads were not showing  up any more. I thought there might be some conflicts between plugins. I tried to de-activate and re-activate the plugin, but it didn’t help.

Checking the author’s web site and I found that the way to embed it in the php files has changed. The old way of embedding it is:

<?php adrotate_banner('1'); ?>

This does not work anymore in 2.2. You have to code it this way.

<?php echo adrotate_banner('1'); ?>

I have been using WordPress Automatic Upgrade plugin to upgrade my blog. It has worked perfectly up until 2.7 upgrade. Ever since the upgrade to WordPress 2.7, I found that some of the new features do not work, like the flash based image upload and the ability to install plugin directly from within WordPress dashboard. I didn’t pay much attention to it, because there are workarounds.

When the WordPress 2.7.1 came out, I tried to use the WordPress Automatic Upgrade plugin again, but this time it cannot dectect there is an upgrade needed. I also noticed there is another automatic upgrade option on the dashboard. It seems like the automatic upgrade is a bulit-in function now. I used the built-in automatic upgrade function to upgrade my blog from 2.7 to 2.7.1 without a problem. I also de-activated the WordPress Automatic Upgrade plugin. After the de-activation of the plugin, I found that I can now use the WordPress 2.7′s new features. If you find there are something strange about your WordPress 2.7 installation and you also have the Automatic Upgrade plugin installed, try disable the plugin and see if it helps.