Hi @chriscarvache
Thanks for the attachment.
Yes, the issue is definitely related to the size of the flexible content field.
The current ACF data architecture does not allow for such massive field sizes, so I am unable to help fix this issue in ACF4.
In ACF5, this will no longer be an issue, as each sub field is saved as a unique entry to the DB. This will prevent the flexible content field from becoming so big that it can’t save.
Sorry to not provide a solution as yet, but please wait for v5 to use a flexible content field at this size.
perhaps a temporary solution is to increase your server’s max_vars setting + PHP memory – http://www.advancedcustomfields.com/faq/limit-number-fields/
Thanks
E
