[5.x]: Matrix in Matrix reaching max input vars quickly
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
What happened?
I have been testing the "matrix in matrix" solution in Craft 5 for a while now, and I've noticed that I reach the max input vars of 1000 really quickly.
For my test I have a few different entry types and matrix fields:
- Section
-
- Column
-
-
- Image, Text
-
Creating one section, with 3 columns inside, with one image and text block in each column, so a total of 9 blocks, already hits max input vars.
I might be mistaken, but wasn't the entrification of matrix fields partly to avoid saving huge payloads (neo, supertable), and to offset the saving to each individual entry instead of saving the whole "field"?
Writing something in one text field now turns the whole page blue with "changes" and I get told I have hit max input vars.
I know one can up this limit, and we have it higher in production, but at the rate this is growing atm, we would have to have 50 - 100 000 vars limit for a large page with a lot of content..
Craft CMS version
5 Alpha 11
PHP version
8.2
Operating system and version
MacOS
Database type and version
MariaDB
Image driver and version
No response
Installed plugins and versions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the nested Matrix structure described in the issue using Craft 5 Alpha 11, PHP 8.2, and MariaDB, then inspect the save request when the 1,000-input limit is reached. Compare the number of submitted variables with the nested blocks and verify that a large page can be saved without requiring an extreme server limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mariadb, php
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100