Closed paales closed 10 years ago
This one should not happen anymore with the latest commit (e1a1aa44dcf180be99e55aa5f15a6238f7f713e9). Anyway, as this is not the first time that you get this error on the same grid, can you tell if there is a specific "setup" for it to happen ? And did it already happen on other grid(s) ?
On a side note, a messages system dedicated to the extension is intended for the next commit, so ultimately it should be a reachable goal to detect and prevent all the errors of this kind, and to display related messages with possible causes and / or solutions.
This one should not happen anymore with the latest commit (e1a1aa4). Anyway, as this is not the first time that you get this error on the same grid, can you tell if there is a specific "setup" for it to happen ? And did it already happen on other grid(s) ?
Hmm, I remember when the error popped up the last time more grids started to show the same behavior but can't tell for sure. Flushed the cache almost immediately:)
On a side note, a messages system dedicated to the extension is intended for the next commit, so ultimately it should be a reachable goal to detect and prevent all the errors of this kind, and to display related messages with possible causes and / or solutions.
Nice :)
The thing that might be unique is that multiple columns are added through an observer.
The new option "Force Grid Rewrites" in the system config should help to prevent most of the problems of this kind (but is still experimental)
The problem is solved after flushing the cache.