You have javascript conflicts on your site
From Jomres v4 manual
You may be been guided to this page by the Jomres staff because you're experiencing JavaScript problems on your site where some other scripts are preventing the Jomres JavaScript functionality from working.
Every day we get numerous questions and tickets asking why certain elements of Jomres JavaScript functionality (particularly the booking form) doesn't work. We know that Jomres doesn't work in a vacuum and right from the very start we coded Jomres JavaScript so that it would work in a "noConflict" mode, meaning that it shouldn't interfere with other JavaScript libraries on the same page.
That said, there are often still problems where some other code on the site doesn't play nicely with the Jomres JavaScript. There isn't much we can do about this as it's utterly impossible to test Jomres against all possible plugins. The only thing we can do is test Jomres on a default installation of Joomla in a selection of browsers.
If you've installed another template or module/component/plugin that introduces JavaScript errors into a page, there's not a lot we can do about it. You can prove that the plugin you've installed is responsible by changing your default template and disabling any plugins/modules etc that you may have installed that could also cause the problem. Additionally, it's not unheard of for some cheap hosts to inject advertising direct into your page, this can also insert html into the data returned from an ajax call an break the booking engine.
If you suspect a conflict is causing problems then first you'll need to install some tools to help you analyse these issues. Our preferred tools are Firefox combined with Firebug. Once you install the Firebug extension you'll be able to view your site (make sure you've enabled firebug in it's configuration settings) in Firefox and if there are Javascript errors you'll see them in Firebug's console.
Once you've identified the problem, you're then advised to contact the suppliers of that software and ask them why it doesn't work with jQuery running in noConfict mode.
