Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.When we added the dashboard, we provided settings for disabling fetching messages and the toolbar link should they interfere with a site. However, in certain high-volume stores, the summary reports (e.g., most sold products) or prior period comparison queries may time out or otherwise run out of resources. Not sure how detailed we need to go here - could theoretically add a setting for everything, but we should at least add them for the top 4 items:
commerce_dashboard_show_prior_period_comparisoncommerce_dashboard_show_sales_this_yearcommerce_dashboard_show_product_reportcommerce_dashboard_show_promotion_reportcommerce_dashboard_show_sales_this_monthcommerce_dashboard_show_sales_this_weekcommerce_dashboard_show_sales_todaycommerce_dashboard_show_store_selector
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 3412349-4.patch | 7.46 KB | jsacksick |
Comments
Comment #2
rszrama CreditAttribution: rszrama at Centarro commentedComment #3
jsacksick CreditAttribution: jsacksick at Centarro commentedOnly setting name that I changed is:
"commerce_dashboard_show_sales_today" to "commerce_dashboard_show_sales_this_day", as the setting varialble name is built dynamically for all periods.
We could also rename the period to "today" instead of "day", but that would still mean having special handling for this period when building the setting key.
Comment #4
jsacksick CreditAttribution: jsacksick at Centarro commentedComment #7
jsacksick CreditAttribution: jsacksick at Centarro commentedCommitted!
Comment #8
jsacksick CreditAttribution: jsacksick at Centarro commented