Internet Explorer 11 returns AJAX HTTP Errors usually HTTP Result Code: 500 but it also sent back a HTTP Result Code: 12019 when requesting Model Forms with Webform.
I don't know about other versions of IE.
The Modal Form with the Webform is working perfectly for Safari, Chrome and Firefox.
I switched from Modal forms 7.x-1.2 to Modal forms 7.x-1.x-dev so I could use a patch made for the development version which successfully fixed an AJAX bug on iPad and iPhone.
Unfortunately an Explorer browser problem is one I can't ignore. It's amazing how many people use it.
Anyone have any ideas?
Thanks.
-Garvin
Comments
Comment #2
garvin commentedComment #3
garvin commentedTo All,
Forgive me if I'm not using the the correct forum process here. I'm not very forum savvy.
I'm reporting a new find concerning this issue.
It seems that a URL parameter (argument) is the cause of IE11's throwing AJAX errors. Not Modal Forms!
Without the URL Argument, Modal Forms works on IE11 - works:
www.MyWebsite.com/modal_forms/nojs/webform/39
With a parameter (argument) at the end of the URL it causes AJAX to fail:
www.MyWebsite.com/modal_forms/nojs/webform/39?product_name=[A%20String%20of%20Text%20Here]
There seems to be an URL parameter encoding issue with Internet Explorer versions 10 & 11 ( IE10 , IE11 ).
This comment by openthinktech appears to head in the right direction:
https://www.drupal.org/node/1651226#comment-8773335
gk (google keys): url parameter ie11
These seem to confirm that hypothesis:
Unicode in URL changes for IE11 -
http://blogs.msdn.com/b/ieinternals/archive/2014/04/22/internet-explorer...
encoding of query string parameters in IE10 -
http://stackoverflow.com/questions/18220057/encoding-of-query-string-par...
Does anybody think my conclusion is correct….. or incorrect. Any guidance is appreciated.
If anyone knows where I can "Hook" in PHP to conditionally redirect Internet Explorer to a regular Webform node, it would help.
I'm using the URL parameter to pre-populate a Webform form text area with a string of text related to any product.
If someone can tell me about a work around I would be grateful. I might resort to Javascript.
Thanks!
-Garvin
Comment #4
garvin commentedComment #5
garvin commentedComment #6
garvin commentedHi All,
For anyone it might help, I've solved my problem.
I had an unencoded colon ":" in my parameter string (idiot). Every browser I tried aside from Internet Explorer(s) worked in spite of the unencoded colon. I tried the modal form with its webform on IE6 and it too threw a HTTP Response error - that was a good clue.
Here's a nice little online encoding tool (thank you Eric A. and Kathryn S. Meyer): http://meyerweb.com/eric/tools/dencoder/