Form insert alters Default Page Layout

Do you mean that when you use a Gravity Form, your sidebar widgets are pushed to the bottom of the page? If that's the case, it's probably worthwhile to validate the XHTML and see what you find.

http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.neuroknowhow.com%2Fservice-feedback%2F
and
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.neuroknowhow.com%2Fdsa-at-booking%2F

I suspect there is a missing < div > or closing < /div > missing which is causing you the trouble. Please correct the XHTML markup and see if that resolves your layout issue.

Regarding AJAX, you have a few JavaScript errors on the pages:

http://www.neuroknowhow.com/service-feedback/

Timestamp: 7/29/2012 1:07:54 AM
Error: SyntaxError: syntax error
Source File: http://www.neuroknowhow.com/service-feedback/
Line: 138, Column: 21
Source Code:
   delay           : , 

Timestamp: 7/29/2012 1:07:54 AM
Error: SyntaxError: syntax error
Source File: http://www.neuroknowhow.com/service-feedback/
Line: 172, Column: 24
Source Code:
   transition_interval: ,

Additionally, on this page http://www.neuroknowhow.com/dsa-at-booking/

Timestamp: 7/29/2012 1:09:03 AM
Error: TypeError: jQuery(".uam_group_info_link").tooltip is not a function
Source File: http://www.neuroknowhow.com/wp-content/plugins/user-access-manager/js/functions.js?ver=3.4.1
Line: 47

You should correct those errors before trying to troubleshoot anything related to AJAX. Thank you.

Please post back if you need additional assistance. We'll leave this topic open.

One conflict is definitely coming from the User Access Manager plugin. Another problem is coming from the AG Custom Admin plugin. I would start by disabling those two plugins temporarily. That might take care of the AJAX errors.

However, the 109 XHTML validation errors are going to require more work from you. If you're not sure where to start you may need to find someone local to help you with this. When the sidebar and widgets drop to the bottom of the page like this, it's usually due to invalid markup, a missing closing < /div > usually.

Glad you found it. Invalid HTML will do all sorts of strange things.