Hello, i resently found that internet explorer cant handle the update of the submit form when the client es changed in the drop down control. When a new client is selected, IE trys to save the file insted of update the form. Tested in Firefox and Chrome it works fine.

The file IE wants to save is named "callbackd64802a3" with variations in the chars and numbers after "callback"
The content of the file is this:

{ "status": true, "data": "\x3cdiv id=\"support-fields-ahah-wrapper\"\x3e\x3c/div\x3e" }

Boost is installed in the site, I try disabling it but the problem continues.

Comments

span’s picture

span commented

Thanks for the report. Which version of IE are you using?

jmrivero’s picture

jmrivero commented

No problem.
IE version is 8.0.7600.16385.

span’s picture

span commented

Please check out this patch and see if it solves your problem #1077832: CCK groups not working properly.

For the record the RC1 in it's current form does not work properly with either browser due to the reasons mentioned in the issue linked to above. If the patch in that issue fixes your problem please report back so I can release a new RC.

Thanks.

span’s picture

span commented
Status: Active » Needs review
jmrivero’s picture

jmrivero commented

Just tested it but the problem is still there :-/

span’s picture

span commented
Status: Needs review » Needs work

Very strange, it fixed the problem in IE7 for me. Will investigate further.

span’s picture

span commented

I've made a new patch here: http://drupal.org/node/1031004#comment-4245564, I haven't tested it against IE yet but will be able to do that tomorrow. If fixes several problems with the RC1 and if you want to try it you are more then welcome. I cannot guarantee it will work though and tomorrow I can test it.

jmrivero’s picture

jmrivero commented

Ok, thnx for your quick support, ill wait, no hurrys ;)

span’s picture

span commented

Ok, cool. New patch in comment #5 in the post I linked to that has been tested. Does it work for you in your setup?

span’s picture

span commented

Should be fixed in rc4.

span’s picture

span commented
Status: Needs work » Fixed
jmrivero’s picture

jmrivero commented
Status: Fixed » Active

Still the same :-/
Got the RC4, removed the old version and uploaded rc4, but its still the same problem.

Now the "Please fill out these values." text is always there but nothing to fill there but the normal support fields, client, priority, user and status.

span’s picture

span commented

I got it working on a whole new install yesterday so perhaps it could have something to do with your configuration? I will have access to IE tomorrow afternoon again and can run another check then.

To make sure it is not something in your setup it would be good if you could make a clean Drupal installation and install only support and support fields module, configure them and test. If that still doesn't work, please report back.

EDIT: Just to make sure, have you configured the fields under the client settings? It seems weird that you do not see any of the custom fields so I'm thinking perhaps you have forgotten to activate them?

jmrivero’s picture

jmrivero commented

Ok, just tested it in a clean install and it works fine.
Added some taxonomy fields to the support content type, same as in the live site and it still works with no problem.
Well, thnx again span.

EDIT: Actually now im not using any CCK field with the tickets, but if i disable the support fields module the client, status, and other fields wont show up in the submit form.
Im using 2 taxonomys asigned to the support content type and use Taxonomy Term Permissions 6.x-1.0 to show/hide some terms depending on the roles.

span’s picture

span commented
Status: Active » Closed (works as designed)

Glad it works for you :D

If you ever run across the reason it didn't work for you, please tell me. Would be good to know!

jmrivero’s picture

jmrivero commented

Erm, it still doesnt work in my production site, but sok, maybe with time and updates it gets fixed.

span’s picture

span commented

Yeah, that's too bad it doesn't :/

If you ever stumble across why please let me know. It's probably in conflict with another module, theme or other configuration but it's impossible for me to locate and test towards anything else then a clean environment. Good luck, hope you get it fixed!