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
Apparently, the SuperTable plugin does not detect whether there was any text change when saving existing items and generates update-search-index processes for all items, which can be hundreds or thousands of unnecessary processes.
For example - we used SuperTable for a simple translation solution for our frontend, which runs in Astro (via GraphQL).
We have hundreds of these items there, and even editing one word will generate hundreds of processes to update the search-index.
Steps to reproduce
Create simple supertable field with 2 fields/columns
Put 100 rows into this table
Even if you later edit only one text item in this table and save it, the plugin will generate an update-search-index process for all, even unchanged, items.
The expected behavior is that when saving, it is detected whether the value has changed (e.g. based on affected rows after the UPDATE query has been executed) and if not, the searchindex update process will not be invoked unnecessarily.
Thanks for improving this behavior.
Craft CMS version
4.4.14
Plugin version
3.0.9
Multi-site?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Hi,
Apparently, the SuperTable plugin does not detect whether there was any text change when saving existing items and generates update-search-index processes for all items, which can be hundreds or thousands of unnecessary processes.
For example - we used SuperTable for a simple translation solution for our frontend, which runs in Astro (via GraphQL).
We have hundreds of these items there, and even editing one word will generate hundreds of processes to update the search-index.
Steps to reproduce
The expected behavior is that when saving, it is detected whether the value has changed (e.g. based on affected rows after the UPDATE query has been executed) and if not, the searchindex update process will not be invoked unnecessarily.
Thanks for improving this behavior.
Craft CMS version
4.4.14
Plugin version
3.0.9
Multi-site?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered: