You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a super table nested inside a matrix block as below:
When an entry containing this field is saved (any change, not just to the field in question) we see a large number of jobs triggered to Update search indexes and prune extra revisions. None of the fields have 'Use the field's values as search keywords' enabled.
This seems orders of magnitude larger compared to saving without the field, the jobs can sometimes just hang and do place quite a burden on the CPU/Memory of our site despite the change not usual touching this field. If this is expected then is there a way to disable it?
We have tried resaving the super table fields without any luck
Steps to reproduce
Create a matrix block with a nested Super Table Field
Populate the field for a given entry
Save the entry without making any changes to the matrix block
See a large number of jobs triggered
Craft CMS version
4.5.2
Plugin version
3.0.9
Multi-site?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hello @baileydoestech - I've had the same exact issue - did you find a way get those large numbers of jobs to stop bogging down the cms?
There is an async tool that might be helpful to you that partly solves things… Im trying to find a way to not even need that in the first place though.
I believe this got noticeably better for us in a recent Craft release but as super table is now deprecated we aren't going to spend much more time on looking into this. Async queue also helped with us
Describe the bug
We have a super table nested inside a matrix block as below:
When an entry containing this field is saved (any change, not just to the field in question) we see a large number of jobs triggered to Update search indexes and prune extra revisions. None of the fields have 'Use the field's values as search keywords' enabled.
This seems orders of magnitude larger compared to saving without the field, the jobs can sometimes just hang and do place quite a burden on the CPU/Memory of our site despite the change not usual touching this field. If this is expected then is there a way to disable it?
We have tried resaving the super table fields without any luck
Steps to reproduce
Craft CMS version
4.5.2
Plugin version
3.0.9
Multi-site?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered: