Timeline for Field Collection module Ajax error
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 26, 2014 at 17:58 | vote | accept | Alex Coleman | ||
| Aug 26, 2014 at 17:58 | answer | added | Alex Coleman | timeline score: 1 | |
| Aug 15, 2014 at 10:04 | comment | added | Andy |
I've been caught out before by going beyond max_input_vars. Here's an explanation of why it exists. Dunno if that's what's going on here tho...
|
|
| Aug 14, 2014 at 19:35 | history | tweeted | twitter.com/#!/StackDrupal/status/500002743273398272 | ||
| Aug 14, 2014 at 15:23 | comment | added | Alex Coleman | I just recreated the entire problematic node by hand, and the same Ajax errors started occurring again after adding ~20 associated field collection nodes to it. So it shouldn't have anything to do with missing database entries. | |
| Aug 14, 2014 at 15:05 | history | edited | Alex Coleman | CC BY-SA 3.0 |
added 154 characters in body
|
| Aug 14, 2014 at 14:39 | history | edited | Alex Coleman | CC BY-SA 3.0 |
added 221 characters in body
|
| Aug 14, 2014 at 14:36 | comment | added | FatGuyLaughing | If you have access to the database, get the node id of the book that is having the problem. Next look at the field_data_YOUR_FIELD_COLLECTION_NAME table and find where the reference id equals your book id. I've had a problem in the past with field collections getting deleted but still showing on the node. | |
| Aug 14, 2014 at 14:26 | review | First posts | |||
| Aug 14, 2014 at 14:35 | |||||
| Aug 14, 2014 at 14:25 | history | asked | Alex Coleman | CC BY-SA 3.0 |