I'm going through a long list of nodes with incorrect addresses and correcting them. I'm getting irregular Ajax errors:
- sometimes when I select "United States" as a country, the states pull-down doesn't appear
- sometimes when I try and save the node, it refreshes to the edit form and there's an Ajax warning in the log: Invalid form POST data.

Any suggestions please?

Comments

rtdean93’s picture

I am having similar trouble. I believe there is a conflict with the copy billing address formatter. If I disable the formatter, then the ajax form works when changing the country of the shipping address.

kristen pol’s picture

I'm getting AJAX errors when trying to change the country as well. It gives is:

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /system/ajax
StatusText: Internal Server Error
ResponseText: 

Notice there is no response text so it isn't very helpful :/ I'm going to have to switch to using a different module for address fields for now... maybe location or addresses.

[UPDATE] I just tried Location and get an AJAX error when changing the country as well, so there is something else going on...

An AJAX HTTP error occurred.
HTTP Result Code: 500
Debugging information follows.
Path: /system/ajax/field_location/und/0
StatusText: Internal Server Error
ResponseText: 

[UPDATE2] It turns out that it was due to the fact that I'm using the field in an Entityform:

#1606878: Panels integration fails (AJAX error) due to functions living in .admin.inc file instead of .module file

The upshot is:

CHECK YOUR APACHE LOGS ;)

rszrama’s picture

Category: bug » support
Status: Active » Closed (cannot reproduce)

There isn't much we can do to address irregular errors, but it looks like there may be module incompatibilities at play. It could also be you're just moving too quickly for the Drupal forms system. If an AJAX refresh is in progress and you try to generate another one, it could result in an error I believe. If you get solid steps to reproduce this on a clean install, I'm happy to try and rig it up locally to see if there's truly an issue. Otherwise it just sounds like expected (if unfortunate) behavior.