Applying WAUE to a form in a menu...

I'm building a page and have completed the design elements using the Foundation framework containing the following elements:

Megamenu from Pixelworkshop: http://codecanyon.net/item/universal-responsive-mega-menu/4984236?WT.oss_phrase=sticky%20footer&WT.oss_rank=8&WT.z_author=Pixelworkshop&WT.ac=search_list

bxSlider: http://bxslider.com/ (two instances, one under the header combined with a hover effect from Codrops:http://tympanus.net/codrops/2012/04/09/direction-aware-hover-effect-with-css3-and-jquery/
and another plain-jane bxSlider just above the footer.

Content is mixed static and dynamic mySQLi recordset content.

I then added a page preloader at http://tympanus.net/codrops/2014/08/05/page-preloading-effect/ and everything was working fine.

Since the mega menu has a contact form in one of the dropdowns, I applied a WAUE Server Behavior to the menu, and when I tested the page the preloader would not complete. I only got an empty page with the text elements from the menu. In troubleshooting, I found that when I reverted the menu include to use the original menu code without the WAUE Server Behavior, I was able to get the preloader to work, but my menu CSS and my bxSliders' css were whacked. I have a backup of the site on another computer that works fine (pre WAUE) and I've continued troubleshooting by removing the form and replacing it with a WA Form that uses Validation Toolkit and Universal Email and I'm still getting the preloader problem. When I revert to the original menu file, the preloader works but the menus are misaligned and the bxSliders don't appear properly.

Can you give me some pointers on how to fix this?

Thanks!
Mark

I'll need to troubleshoot directly, see the private message section.

Originally Said By: Jason Byrnes

  I'll need to troubleshoot directly, see the private message section.  

Thanks so much Jason! I've posted the database and the prototype site to our server and have posted the links to both the broken page and the page before applying WAUE so you can see a before and after version.

Heres a thought for you Mark, set the action of the contact to post to another page.

Apply the UE Behavior to the action page, that way you won't have to apply it top the include page and can bypass whatever is causing the problem.

Originally Said By: Jason Byrnes

  Heres a thought for you Mark, set the action of the contact to post to another page.

Apply the UE Behavior to the action page, that way you won't have to apply it top the include page and can bypass whatever is causing the problem.  

Hi Jason:

There appears to be some kind of validation that is CSS triggered which causes the form to display "Something went wrong. try refreshing and submitting the form again." I've contacted the author of the Mega Menu code to see what's going on there. I did try creating a menu with the WA CSS Form Builder. More notes in the Private Message area....

Clearly the web assist form is conflicting with the mega menu script, that is why I suggesting separating them out rather than use a web assist form. Most likely the mega menu uses a version of jQuery that conflicts with the jQuery validation from form builder.


any validation issues with the mega menu form you will need to address with them.