While looking to make some minor changes to a drupal commerce site, I needed to change the formatter on one of the views fields. When I pressed 'Apply (this display)' nothing happened, I tried a few more times but still nothing happened. I checked the watchdog log and it displayed "Invalid form POST data.". I also checked the apache error logs, and there was nothing in there.

Upon further testing I found that it isn't just the one field, or even the one view for which this issue occurs, it also occurred on various different fields across various different views. There didn't seem to be any link between the fields which couldn't be updated, other than possibly being inside the same view as a commerce_product field.

What I have tried so far:
Clearing the caches,
Disabling caching,
Different web browser,
Adding a new field (same issue occurs when clicking apply).

None of the above made any difference to the issue, other than trying to add a new field, which revealed that fields could not be added/removed either because of this issue.

Comments

DerryC created an issue. See original summary.

DerryC’s picture

DerryC CreditAttribution: DerryC commented
Component: Views Data » Miscellaneous
pauldolphin’s picture

pauldolphin CreditAttribution: pauldolphin as a volunteer commented

I'm encountering a similar issue. What's even stranger is that this is not affecting all views. Some allow me to save... others will not. How did you resolve this?

zalak.addweb’s picture

zalak.addweb CreditAttribution: zalak.addweb commented
Issue tags: +views
nimbletoad’s picture

nimbletoad CreditAttribution: nimbletoad commented

Has anybody found a solution to this? I am now getting this error sporadically in my views and cannot find a common reason. If open the views a views link such as add field or edit a field, I am able to apply changes. However, if I try to reopen that link in the same window it will not let me apply changes with a resulting Invalid form POST data log message.

jgalletta’s picture

jgalletta CreditAttribution: jgalletta commented

Just had this issue on a project.

I added at some point an ajax form on a node full page, and views interface started to throw this error.
I then found this issue: https://www.drupal.org/node/1922342, which is for Search API, but the suggested workaround worked for me. It's strange because my ajax form is on full rendered entities only and the view I had the problem on doesn't render full entities.

So basically, check if you have somewhere in the entities displayed by your view an ajax form, and if it's the case set a custom id on the ajax form element.

johnzzon’s picture

johnzzon
Primary language Swedish
Location Gothenburg 🇸🇪
CreditAttribution: johnzzon at Kodamera AB commented

Thanks jgalletta, that was the issue for me as well. Another module was rendering an AJAX-form on all pages that was conflicting.