Closed nouphalpgs closed 2 years ago
Hi @nouphalpgs ,
I'm not able to replicate this so far. Can you provide a little bit more context:
We are using Laravel 8, we are not sure whether its package issue. This error comes when we try to retrieve the model from Laravel cache. When we removed the query from laravel cache, then there is no issue.
Cache was the detail that I needed to figure it out. It seems like serializing/unserializing would cause the internal index of meta to get messed up. I've adjusted the code to regenerate it properly.
Fixed in 5.1.1
Happy Holidays!
Thanks.
On Sun, Dec 26, 2021 at 10:11 PM Sean Fraser @.***> wrote:
Cache was the detail that I needed to figure it out. It seems like serializing/unserializing would cause the internal index of meta to get messed up. I've adjusted the code to regenerate it properly.
Fixed in 5.1.1
Happy Holidays!
— Reply to this email directly, view it on GitHub https://github.com/plank/laravel-metable/issues/70#issuecomment-1001223549, or unsubscribe https://github.com/notifications/unsubscribe-auth/AWUP5T4VJ654D3DHGA6N27LUS5LG5ANCNFSM5KPSQYOA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
The error comes here vendor/plank/laravel-metable/src/Metable.php:218