NextGEN Scroll Gallery on WordPress – Error on page: Warning: Division by zero

Few days back my hosting company send me a warning that disk space consumption on my server has hit 80%. I was shocked because no new client came on board. I became worried thinking if my server has been compromised or any account on the box has been hacked! I instantly logged into the server and tried to figure out the domain consuming disk space more than the allocated quota. Once I was able to figure out the domain, I instantly started analyzing it’s disk consumption folder wise. All this lead me to a error_log file which grew up to 18 GB in last 15 days time. This site has average 1500 visitors per day. I inspected the error_log to see which page is generating so many errors and to my surprise it was a page with NextGen Scroll Gallery. This gallery page was created two years ago and didn’t had an iota of any error till last 15 days. Now, the page was full of several lines showing following error:

Warning: Division by zero in nggScrollGallery.php on line 296

Of course, it had folder name etc. prepended  to the script name (which I have omitted here due to same security reason). In order to try and solve this error, I created a new gallery page but it worked fine. I compared both the gallery page (the one which was generating errors and the newly created one). Everything was same except the gallery id. I created another page with same gallery id. This time the error showed up. So, the problem was with gallery.

I went to manage gallery option and re-generated the thumbnails but this didn’t solve the problem. Then I imported meta data for all the images in gallery. The next moment the gallery was working fine. Seems, somehow the meta data information for images in the gallery got corrupted or deleted. Re-importing this information solved the issue. After that I deleted the error_log and my disk consumption status also went back to normal.

Advertisement

New exciting changes in upcoming wordpress 3.9

WordPress 3.9 is due for release in mid-April. While the RC 1 was released last week, we take a look at some improved / new exciting features of WordPress 3.9:

• Updated TinyMCE – The software powering the visual editor has been updated to 4.0 (latest version).
• Added widget management to live previews –  You can now test editing, adding, and rearranging widgets.
• Ability to upload, crop, and manage header images, without needing to leave the preview.
• Drag-and-drop images – Now, you can drag drop images directly onto the editor to upload them.
• Improved image editing capabilities – Making changes to an image after inserting it into a post is lot easier now.
• New audio/video playlists feature – More details are awaited on this.

If you are the adventoures type soul, download and use WordPress Beta Tester plugin or you can download the release candidate (Zip version) and test it on a test site. Beware it’s not final version so using it on a production site may be dangerous.

Install health check plugin to see if you are ready for WordPress 3.2

In a recent announcement WordPress team has announced that version 3.2 of WordPress will not support PHP 4 and MySQL 4. WordPress 3.1, which is due in late 2010, will be the last version of WordPress to support PHP 4.

WordPress 3.2, due in the first half of 2011, the minimum required PHP version will be raised to 5.2. The new required MySQL version for WordPress 3.2 will be 5.0.15.

Since the vast majority of WordPress users are using PHP 5.2 and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the Drupal and Joomla projects will be supporting in their next versions, both due out this year.

WordPress users will not be able to upgrade to WordPress 3.2 if their hosting environment does not meet these requirements. The built-in updater will prevent the upgrade process in case it find PHP or MySQL to be below the required version.

To determine which versions your host provides WordPress team has created the Health Check plugin. Right now, Health Check will only tell you if you’re ready for WordPress 3.2. In a future release it will provide all sorts of useful information about your server and your WordPress install, so hang on to it!

In summary: WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4 and MySQL 4. WordPress 3.2, due in the first half of 2011, will require PHP 5.2 or higher, and MySQL 5.0.15 or higher. Install the Health Check plugin to see if you’re ready!

Upgrade to WordPress 2.8 Now!

The latest version of WordPress, version 2.8 “Baker” (named in honor of noted trumpeter and vocalist Chet Baker), has been released on Wednesday, 10 June, 2009 as scheduled. It has several improvements to themes, widgets, taxonomies, and overall speed along with over 790 bugs fixed.

Visually 2.8 doesn’t look much different from 2.7, however once you start digging dip, you’ll notice and begin to appreciate the changes.

PCLZIP_ERR_BAD_FORMAT – WordPress Upgradation Problem

Recently I was asked by a client of mine to upgrade her self-hosted WordPress blog to 2.71. from 2.6. I though it to be a smooth task as this was a pretty new installation without any plugins or themes and I had upgraded at least 10 other self hosted WordPress blogs (far bigger than this one) few days back without any problem. I logged on to the blog’s dashboard and upgrade warning from WordPress was flashing on the screen. I gladly clicked on upgrade button and thought the task is taken care of. But what the hell!!!!

WordPress.com upgardes Free Space to Three Gigabytes

Today, wordpress.com made an announcement to upgrade free upload space by 6o times from 50mb to 3000mb for all wordpress blogs hosted on it. This upgrade will give its’ users freedom to blog rich media withour having to worry about storage space left in their wordpress account. To remind you 1GB paid space at a normal web hosting company costs approx. $300 per year.