Tag Archives: bug

jQueryUI Datepicker Calendar Control Visible at the Bottom of the Page CodeUnit 24 JUN 2011

For some or other annoying reason, my jQueryUI datepicker controls start exhibiting a weird bug where on page load, the normally hidden control calender was appearing right at the bottom of the page. Clicking on the launch control would then bring up the calendar correctly, and on selection or unfocus would then hide it again correctly. So only on page load then.

Luckily the fix to this annoying problem is actually nothing more than a simple CSS rule which you can add to the top of the affected page. (Note that this is after I spent a fair amount of time updating all my javascript plugins and trawling through the code to try and find the problem).

To solve, simply add:

#ui-datepicker-div { display: none; }

Yup, nothing more than that and your unwanted extra space at the bottom of the page is done for.

Nifty. (And yes, I still regard the jQuery and jQueryUI combo’s datepickers as one of the best ones currently available to website designers!)

Related Link: http://jqueryui.com/demos/datepicker/

jQuery Draggable, Droppable and Sortable User Interface not working in Internet Explorer 9 (IE 9) CodeUnit 18 APR 2011

I received a bit of a nasty shock when by sheer chance, one of the project managers updated their machines and got Internet Explorer 9 installed in the process, only to instantly come back to me and announce that the drag and drop features on our web project no longer worked – at all.

A quick look around, and indeed all the draggable, droppable and sortable interfaces that come with our use of the awesome jQuery and jQuery UI libraries were all of a sudden not working under IE 9. The other browsers, IE 8 included, still worked fine, but not this new beast of a browser.

Thankfully though, a quick look about on the jQuery UI support forums yielded the fact that a) this was indeed a bug that has long been identified, and b) that the bug fix ticket around it has since been resolved and closed.

See http://forum.jquery.com/topic/jquery-ui-does-not-work-on-ie9 .

So how do you sort out the problem then? Well if you can, you need to upgrade to the latest version of the jQuery UI library. The fix has now been in since version 1.8.6, so anything higher will resolve the issue.

And now for a big sigh of relief :)

Related Link: http://forum.jquery.com/topic/jquery-ui-does-not-work-on-ie9

Why Does FOUND_ROWS() Keep Returning 1? CodeUnit 16 MAR 2010

MySQL comes with the handy little function known as SQL_CALC_FOUND_ROWS which can be used in normal LIMITed SQL statements to force the DBMS to calculate the number of rows fetched had the LIMIT statement not been applied and leave the result for a later FOUND_ROWS() call to be applied.

Quite useful for pagination really.

Anyhow, if you are using PHP and connecting to MySQL, you’ll sometimes find that using the FOUND_ROWS() call after running a SQL_CALC_FOUND_ROWS statement previously will continuously bring up the result of 1 – which is obviously utterly incorrect.

It turns out that there exists an acknowledged bug that if the PHP .ini setting of mysql.trace_mode is set to true, i.e. on, FOUND_ROWS() will always return 1.

So the solution? Well considering that mysql.trace_mode simply controls the display of warnings for table/index scans, non free result sets and SQL errors, you could probably just turn it off I suppose.

Related Link: http://bugs.php.net/bug.php?id=33021

Use Trash? WordPress 2.9.2 Upgrade Time Then! CodeUnit 17 FEB 2010

Do you make use of the nifty little trash feature recently introduced in WordPress 2.9 that allows you to “delete” or “trash” posts to a recycle bin from which you can then choose to permanently delete or restore at a later date?

Well if the answer is yes then it is probably a good idea to quickly update your installation version to the newly released 2.9.2 version in order to protect yourself against a nasty little bug introduced with this great new bit of functionality!

The problem is that in introducing this new core bit of functionality, developers somehow forgot to properly integrate it within WordPress’ security framework and as such were left with a situation whereby any authenticated user, no matter what rights they have (e.g. they could even be a simple subscriber), can access the trash of any other user – meaning that if you have any sensitive posts that you previously trashed, they would have in fact still pretty much been open for anyone to see.

If you still aren’t on the same page with me as to why you need to upgrade to this patched version ASAP, let me put it to you a little differently. Let us say for example you work for a boss, but being a disgruntled employee, you type up a post on the company blog revealing to the world all the naughty kinkiness you got up to your boss’ daughter. Thankfully though, a moment of sanity prevailed and you trashed the post before publishing it, so it never saw the light of day – whew! However, if the bug was still active and your boss entered the blog to add a new post or such, he would be able to read what you had previously trashed and make no doubt about it – you would now be standing out there in the cold in the unemployment line.

So do yourself a favour. Upgrade to WordPress 2.9.2 today! :)

Related Link: http://wordpress.org/development/2010/02/wordpress-2-9-2/

Novell GroupWise CCSW32.DLL Error Software & Sites 08 JAN 2008

GroupWiseAnyone using an automatically installed copy of GroupWise as their mail client (like us here at UCT) might occasionally come across the following error message on startup:

This application has failed to start because ccsw32.dll was not found. Re-installing the application may fix this problem.

Of course, re-installing GroupWise achieves squat, so I had to look up the cause and solution for this error before it drove me nuts. Thankfully though, the guys at Novell Technical Support have pinpointed the problem and let us in on the fix.

Firstly, the problem crops up with Novell GroupWise 6.5 and Novell Client v4.91 for Windows 2000/XP. The problem appears to be that the NMAS component is only partially installed by the NW Client, which means that not all the files were correctly assigned on install. The solution? Pretty simple actually.

Rename the C:\WindowsSystem32
wsso.dll
to C:\WindowsSystem32ccsw32.dll.

That’s it. Simply start up GroupWise once more and you’ll be happy to find that the annoying error message is now lost forever.