Hi Jim,
Thank you for your post.
Upon receiving your post we upgraded to Joomla 1.5.22 and performed some tests to see if there were any incompatibly issues. Unfortunately, we were unable to reproduce your issues; in fact it worked straight out-of-the-box for us!
In being prudent we have also taken time to carefully observe the Joomla change logs from 1.5.20 up to 1.5.22 and can confirm that no disrupted changed have been introduced.
What to do:
(1.)If the change occurred after upgrading then many the first place is to test that it is not a cache issue.Please see the following link for more information on how to perform:
www.wikihow.com/Clear-Your-Browser%27s-Cache.
(2.)If you are a Firefox user, would you be so kind to install Firebug (which is a 3rd party extensions for Firefox - addons.mozilla.org/en-US/firefox/addon/1843/ ). Once installed would you open up Firebug > select the ‘Console’ Tab and copy and paste the ‘query’ when you received the error.
This will help us see the response from the server and hopefully help us to diagnose your problem.
