-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Admin Error Message: "Call to a member function format() on false" after update to 2.11.9.2 #3449
Comments
Error is gone now an hour later. Maybe this only happens during the first reindex process after the update. |
Error has popped up again several times now. It clears on its own but when it happens, admin notifications are unusable for a while. |
Hello @mfickers, I've added a small fix for this issue. Could you test it on your side by taking inspiration from my commit until it will be not included in our future release? BR, |
Thanks, @vahonc I've patched the file and will report back in a few days. |
It's strange that the Could you share your Indices screen (Admin Panel -> ElasticSuite -> Indices)? BR, |
…ng-false-indexdate-2.10-fix [Indices] Fix #3449, handling a false value of Index updated date
Preconditions
Updated our shop:
PHP 8.2 -> 8.3
Magento 2.4.7-p2 -> 2.4.7-p3
ElasticSuite: 2.11.8.2 -> 2.11.9.2
Now in admin area, a persistent error message is shown where the admin notifications should be:
Magento Version : 2.4.7-p3
ElasticSuite Version : 2.11.9.2
Environment : Production
Third party modules :
Steps to reproduce
Expected result
Actual result
This is the relevant entry from exception.log
For the index with the name
mag2_default_catalog_product_20241125_091325
this method will returnfalse
instead of a valid DateTime:\Smile\ElasticsuiteIndices\Model\IndexStatusProvider::getIndexUpdatedDateFromIndexName
These are the values that produce this result:
Actual error is thrown here: \Smile\ElasticsuiteIndices\Model\IndexStatusProvider::isRebuilding
The method annotation even expects
DateTime|false
for the $indexDate parameter but does not handle afalse
value correctly:Looks like this was introduced in this commit: e208790
The text was updated successfully, but these errors were encountered: