0

I have a custom content with a large number of multivalue date fields (around 200-300 values). I created a node and added a large number of dates. When subsequently editing the post, the following occurs:

  1. The post is saved as unpublished
  2. Changes to the body field and other text fields such as tags are saved
  3. No additional dates can be saved
  4. Clicking on Preview doesn't show a preview, but saves the post as unpublished
  5. Upon attempting to upload an image file, the Drupal message "[content-type] [post-title] has been updated" (with the specific values in place of the [...] placeholders) appears, but it appears BEFORE clicking Save; upon saving the post, no file is saved
  6. "The content on this page has either been modified by another user, or you have already submitted modifications using this form. As a result, your changes cannot be saved." appears when clicking Save after the file upload
  7. The node can be made Published from the content administration screen (but not from editing it individually)
  8. The Revision tab is missing even though the content type has revisions enabled by default
  9. The Authored on date is reset to the first time the node become unpublished

I would like to have some instructions as to how to debug this situation.

PS: The site is hosted on Hostgator.com.

  • There's only one way to debug that really - change the theme to rule that out, then disable contrib/custom modules methodically until you find the culprit. Or step through with a debugger, of course – Clive Aug 12 '13 at 16:48
  • What if the high number of multiple date values have to do with the form data not being saved correctly? I tried to print the $_POST data to screen but I discovered that it is always an empty array on save even in normal cases ($_POST shows data on Preview but not on Save in normal cases). The site is live and I cannot disable modules that easily. – tuccio Aug 12 '13 at 16:55
  • I wouldn't have thought so; either you're exceeding the max POST size or you're not, you wouldn't expect some of those fields to save and others not to if it's just a size problem. Plus the node and fields are saved in a transaction, which should be rolled back if any part fails (or at the very least not committed) – Clive Aug 12 '13 at 16:58
4

I was having a similar problem when editing a node with a field that allowed for unlimited field collection values. Each field collection had 8 input fields, and after adding in over 100 field collection items it stopped adding in more and it would unpublish on Save.

I could publish it from the content administration screen.

I modified max_input_vars in the server php.ini file from max_input_vars=1000 to max_input_vars=2500 and that allowed for the addition of more field collection items and to keep the node published when saved.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.