Describe your bug or feature request.
When I run the update I am getting the following error for many of the different commerce views and core.views pages.
views.view.commerce_giftcard_admin
views.view.commerce_giftcard_transactions_admin
views.view.commerce_orders
views.view.commerce_order_payments
here is the entire error:
// Requirements check reports errors. Do you wish to continue?: yes.
-------- --------------------- ------------- ----------------------------
Module Update ID Type Description
-------- --------------------- ------------- ----------------------------
views timestamp_formatter post-update Update timestamp formatter
settings for views.
-------- --------------------- ------------- ----------------------------
// Do you wish to run the specified pending updates?: yes.
> [notice] Update started: views_post_update_timestamp_formatter
> [error] Saving the configuration entity with ID views.view.commerce_product_bundles generated an exception: 'Entity queries must explicitly set whether the query should be access checked or not. See Drupal\Core\Entity\Query\QueryInterface::accessCheck().'
> [error] Update failed: views_post_update_timestamp_formatter
[error] Update aborted by: views_post_update_timestamp_formatter
[error] Finished performing updates.
the same is happening for:
core.entity_view_display.commerce_order.default.default
core.entity_view_display.commerce_order_item.default.commerce_pos_order_item
core.entity_view_display.commerce_order_item.default.default
core.entity_view_display.commerce_subscription.license.default
core.entity_view_display.commerce_subscription.product_variation.default
core.entity_view_display.commerce_subscription.standalone.default
Comments
Comment #2
socialnicheguru commentedComment #3
socialnicheguru commentedComment #4
jsacksick commentedHow is this a Commerce bug report? The update failing is from the Views module?
Comment #5
jsacksick commentedYou'd need to check what's causing this exception using a debugger or something, if that is possible for you.
Comment #6
socialnicheguru commentedThis error is hard to reproduce. It could be due to local environment or some other issue with the upgrade.