Answers.Body: <p>Craft 2.5 changed from Redactor I to Redactor II, so chances are you just need to update your Redactor configs to the new format: <a href="https://craftcms.com/support/redactor-ii-configs" rel="nofollow">https://craftcms.com/support/redactor-ii-configs</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-23T02:03:19.857Z
Answers.Text: It was related to Redactor config, but not just the bits mentioned in that support post. They also changed how they handle the 'formattingAdd' property. Might be worth adding a note to that support post that mentions it's not comprehensive and folks may need to look to the Imperavi docs for additional changes to config code? In any case thanks for point me in the right direction!
Answers.UserDisplayName: philzelnar
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-04-22T00:06:13.740Z
Answers.LastActivityDate: 2016-04-22T00:06:13.740Z
Answers.UserDisplayName: Brad Bell
Body: <p>Running into some issues with matrix fields after upgrading from 2.4 to 2.6.</p>
  
  <p>The matrix in the site includes a whole bunch of block types that are used to build row-based pages (e.g., Intro, Profile, News, Text, etc.).</p>
  
  <p>When creating a new page everything works just fine at first. However, when you insert certain block types into the matrix, suddenly you can no longer reorder/collapse/add blocks in that matrix.</p>
  
  <p>I notice that when it breaks, the following error pops up in the console:</p>
  
  <pre><code>Uncaught: TypeError: Cannot read property '0' of undefined - velocity.min.js
  </code></pre>
  
  <p>Anyone run into this or have ideas to what this might be? I can't seem to find a commonality between the blocks that cause the error and am not sure where to go with this. </p>
  
  <p>Note: this particular matrix config has a <em>ton</em> of fields (we've had to extend the php memory limit etc. when saving changes to the config).</p>
  
  <p>Tks in advance!</p>
  
  <p><a href="https://i.sstatic.net/HTJRx.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/HTJRx.png" alt="enter image description here"></a></p>
  
  <p><a href="https://i.sstatic.net/EAYNu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/EAYNu.png" alt="enter image description here"></a></p>
  
Tags: <matrix><updating>
Title: Matrix Issues After Upgrading from 2.4 to 2.6
ThreadText: # Matrix Issues After Upgrading from 2.4 to 2.6
  
  (Asked by: username_0 on 2016-04-21)
  
  Running into some issues with matrix fields after upgrading from 2.4 to 2.6.
  
  The matrix in the site includes a whole bunch of block types that are used to build row-based pages (e.g., Intro, Profile, News, Text, etc.).
  
  When creating a new page everything works just fine at first. However, when you insert certain block types into the matrix, suddenly you can no longer reorder/collapse/add blocks in that matrix.
  
  I notice that when it breaks, the following error pops up in the console:
  
  ```
  Uncaught: TypeError: Cannot read property '0' of undefined - velocity.min.js
  
  ```
  
  Anyone run into this or have ideas to what this might be? I can't seem to find a commonality between the blocks that cause the error and am not sure where to go with this.
  
  Note: this particular matrix config has a *ton* of fields (we've had to extend the php memory limit etc. when saving changes to the config).
  
  Tks in advance!
  
  [![enter image description here](https://i.sstatic.net/HTJRx.png)](https://i.sstatic.net/HTJRx.png)
  
  [![enter image description here](https://i.sstatic.net/EAYNu.png)](https://i.sstatic.net/EAYNu.png)
  
  **Tags:** matrix, updating
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-04-22. Score: 1 | Accepted answer
  
  Craft 2.5 changed from Redactor I to Redactor II, so chances are you just need to update your Redactor configs to the new format: <https://craftcms.com/support/redactor-ii-configs>
  
  > **Comments:**
  > **username_0**: It was related to Redactor config, but not just the bits mentioned in that support post. They also changed how they handle the 'formattingAdd' property. Might be worth adding a note to that support post that mentions it's not comprehensive and folks may need to look to the Imperavi docs for additional changes to config code? In any case thanks for point me in the right direction!  
  
  ---
  
  