Answers.Body: <p>Most likely you're bumping into <code>php.ini</code> limitations.  I'd bump the values of <a href="https://secure.php.net/manual/en/ini.core.php#ini.memory-limit" rel="nofollow noreferrer">memory_limit</a>, <a href="https://secure.php.net/manual/en/ini.core.php#ini.post-max-size" rel="nofollow noreferrer">post_max_size</a> and <a href="https://secure.php.net/manual/en/info.configuration.php#ini.max-input-vars" rel="nofollow noreferrer">max_input_vars</a> and see if that helps.</p>
  
  <p>They are common culprits when POSTing large amounts of data (which is what 450 Matrix Blocks would be considered).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-15T00:46:05.687Z
Answers.Text: Excellent, thanks. The memory allocation was pretty hefty, but I hadn't thought to look at `post_max_size` or `max_input_vars`. Upped both and it's usable again.
Answers.UserDisplayName: Nim Wunnan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-15T21:53:46.183Z
Answers.Text: One note -- `post_max_size` allows `0M` as a setting for unlimited size, but Craft will apply this literally to asset uploads as a size limit of 0, so should be specified as a large number if you want to increase it.
Answers.UserDisplayName: Nim Wunnan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-09-11T23:32:09.347Z
Answers.LastActivityDate: 2017-09-11T23:32:09.347Z
Answers.UserDisplayName: Brad Bell
Body: <p>A client has a Singles entry with a Matrix block defined that contains a few text fields, and one image field. They've created approximately 450 instances of this Matrix block, and can no longer update the page. Craft throws a 500 error. Craft logs just show a basic </p>
  
  <p><code>exception 'Craft\HttpException' in /srv/[clientName]/releases/20170418025256/craft/app/controllers/TemplatesController.php:59</code></p>
  
  <p>and nothing of use in the Apache error logs. Anyone have experience with this sort of error, or confidence that this would be a Craft bug?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-12T08:40:34.070Z
Comments.Text: Is the HTTP 500 error Craft-styled or is it a general webserver HTTP 500 error?
Comments.UserDisplayName: Andris Sevcenko
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-09-13T00:04:06.873Z
Comments.Text: Craft-styled, sorry should have specified.
Comments.UserDisplayName: Nim Wunnan
Tags: <matrix><singles>
Title: Single entry with 450 Matrix blocks throwing error on save
ThreadText: # Single entry with 450 Matrix blocks throwing error on save
  
  (Asked by: username_0 on 2017-09-11)
  
  A client has a Singles entry with a Matrix block defined that contains a few text fields, and one image field. They've created approximately 450 instances of this Matrix block, and can no longer update the page. Craft throws a 500 error. Craft logs just show a basic
  
  `exception 'Craft\HttpException' in /srv/[clientName]/releases/20170418025256/craft/app/controllers/TemplatesController.php:59`
  
  and nothing of use in the Apache error logs. Anyone have experience with this sort of error, or confidence that this would be a Craft bug?
  
  **Tags:** matrix, singles
  
  > **Comments:**
  > **username_1**: Is the HTTP 500 error Craft-styled or is it a general webserver HTTP 500 error?  
  > **username_0**: Craft-styled, sorry should have specified.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-09-11. Score: 3 | Accepted answer
  
  Most likely you're bumping into `php.ini` limitations. I'd bump the values of [memory\_limit](https://secure.php.net/manual/en/ini.core.php#ini.memory-limit), [post\_max\_size](https://secure.php.net/manual/en/ini.core.php#ini.post-max-size) and [max\_input\_vars](https://secure.php.net/manual/en/info.configuration.php#ini.max-input-vars) and see if that helps.
  
  They are common culprits when POSTing large amounts of data (which is what 450 Matrix Blocks would be considered).
  
  > **Comments:**
  > **username_0**: Excellent, thanks. The memory allocation was pretty hefty, but I hadn't thought to look at `post_max_size` or `max_input_vars`. Upped both and it's usable again.  
  > **username_0**: One note -- `post_max_size` allows `0M` as a setting for unlimited size, but Craft will apply this literally to asset uploads as a size limit of 0, so should be specified as a large number if you want to increase it.  
  
  ---
  
  