* Display channel column in Orders Analytics UI.
* Set $data to false to not use cache.
For development purpose.
* Get channel info from order meta and put into extended_info.
* Set channel in order item level.
* Replace channel with get_origin_label in extended_info.
* Remove unnneeded channel in orders_data.
* Display origin instead of channel in table.
* Fix lint errors.
* Query order meta table based on HPOS.
* Remove code for development purpose.
* Add changelog.
* Fix code comment.
* Guard against null values.
`_wc_order_attribution_utm_source` can be null when the order is created via web admin.
* Set default origin label to "Unknown".
This default is the same as found in `output_origin_column` function in plugins/woocommerce/src/Internal/Orders/OrderAttributionController.php.
* Support server side report download.
This is needed when there are more than 25 records in the Orders Analytics report.
* Fix failed test.
* Fix lint error.
* Simplify code.
We loop through $orders_data instead of $order_attributions data. This is because $order_attributions may not have attributions data for some orders.
By looping through $orders_data, it would automatically cater for "Unknown" data from get_origin_label function call, and we don't need to specify "Unknown" as default value for origin.
* Change "channel" to "attribution" object in controller.
This is because we need more than one piece of information, so we need it to be an object with properties like `origin`, `device` etc.
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
* Change `origin` string to `attribution` array in Orders DataStore.
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
* Change origin string to attribution object.
* Fix indexing after changing from origin string to attribution object.
* Change from origin string to attribution object in table.js.
* Simplify code.
To make code shorter and easier to read, instead of long horizontal code.
* Fix lint errors.
* Fix failed test.
* Fix lint error.
* Fix retrieving origin in CSV export.
* Use $wpdb->postmeta; cosmetic change.
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
* Cosmetic change.
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
* Sanitize order IDs by using absint.
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
---------
Co-authored-by: Kader Ibrahim S <kader.ibrahim.s@a8c.com>
* add a failing test for order totals with HPOS enabled but sync disabled
* fix comment
* ensure the wc/v3/reports/orders/totals endpoint is compatible with HPOS
* add changelog file
* address linter issues
* Add a safety check for the numbers with the same value for the separators
This case breaks the library we are using for number formatting. This is not documented on their end and can't be fixed by passing a different configuration.
We are fixing it on our end by overwriting the thousand separator.
This change will only surface in the checkout blocks, at they are the only blocks doing formatting via React (the products blocks use php).
This will not apply to the order confirmation.
This change is preventing a fatal error thrown by the library and allowing users to see the content of the cart.
It's an edge case, because it happens only why people have the same values for the separators, which is an non-standard way to format.
* Add unit tests and changelog
* Add a safety check for the numbers with the same value for the separators
This case breaks the library we are using for number formatting. This is not documented on their end and can't be fixed by passing a different configuration.
We are fixing it on our end by overwriting the thousand separator.
This change will only surface in the checkout blocks, at they are the only blocks doing formatting via React (the products blocks use php).
This will not apply to the order confirmation.
This change is preventing a fatal error thrown by the library and allowing users to see the content of the cart.
It's an edge case, because it happens only why people have the same values for the separators, which is an non-standard way to format.
* Add unit tests and changelog
* Improve tests
* "Improve tests"
* Add flaky test reporter for flaky e2e test reporter
* Add to stalebot workflow instead
* Update stale action to 9 for node 20
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
* Updated deprecated gh-script action to node 20 variant
* Minor change in e2e test to trigger CI
* Revert e2e test change
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
* Remove empty "Unknown" handling.
This is because `get_origin_label` would return "Unknown" by default, and therefore empty($origin) would not be true.
If someone use a wc_order_attribution_origin_formatted_source filter to return '' as the formatted source, we should respect it anyway and we should not override it with "Unknown".
* Add changelog.
* add a woo.com connect notice in the plugin list for unconnected store
* add an extra notice string for store that runs outdated woo plugins
* add connect page hyoerlink to the plugin notice
* add changelog
* add comment for maybe_show_connect_notice_in_plugin_list()
* fix linter error
* use installed local woo plugin as the counter of extra notices
* only show woo connect notice in the woocommerce settings page
* add woocom connect notice component
* add woocom connect notice component to the content component
* add extra notice in the woocom connect notice component based on the local woo plugins count
* persist dismissal of woo connect notice in the wc admin settings page
* update changelog
* use update-check-public for unconnected stores
* use information from update-check-public API to determine notice show logic
* re-show dismissed connect woocom notice after 1 month
* add re-show notice logic for react admin page of woo connect notice
* fix identation
* differentiate local storage key for notice dismissal
* move woo connect notice script to different file
* rename to connectnotice
* fix linter issue
* fix linter issue
* update woo.com to woocommerce.com
* update woo.com to woocommerce.com in comment
* capitalize the WooCommerce.com
Co-authored-by: Leif Singer <leif@automattic.com>
* capitalize WooCommerce.com
---------
Co-authored-by: Leif Singer <leif@automattic.com>
* Added new OrderSummaryTotals Block
* Refactor order summary and totals block to contain the inner children
* Add migration for Order Summary Block
* Migration to handle older order summary without totals block
* Remove empty lines from order summary migration
* block editor migration for order summary
* Fix isEligible function
* Update Totals title
* Add checkout totals
* Remove echos and dies
* replace individual checkout blocks with totals block
* Change parent of totals inner blocks and add totals block to innerBlockAreas map
* change CART_ORDER_SUMMARY_TOTALS to CHECKOUT_ORDER_SUMMARY_TOTALS
* Fix linting issues
* fix lint warnings
* Add changelog
* Lock movement of the taxes block in attributes.tsx
* Less indentation in the render function of CartOrderSummaryBlock and CheckoutOrderSummaryBlock
* Rename webpack chunkName for order summary totals
* Add coming_soon page as a store page
* Implement coming soon banner dismiss
* Added a new REST for Launch Your Store with a dismiss endpoint
* Updated coming soon banner logic to check for woocommerce_coming_soon_banner_dismissed
* Lint fixes
* Add changefile(s) from automation for the following project(s): woocommerce
* Update plugins/woocommerce/src/Admin/API/LaunchYourStore.php
Co-authored-by: Chi-Hsuan Huang <chihsuan.tw@gmail.com>
* Update plugins/woocommerce/src/Admin/API/LaunchYourStore.php
Co-authored-by: Chi-Hsuan Huang <chihsuan.tw@gmail.com>
* Update plugins/woocommerce/src/Admin/API/LaunchYourStore.php
Co-authored-by: Chi-Hsuan Huang <chihsuan.tw@gmail.com>
* Use user meta to save woocommerce_coming_soon_banner_dismissed
* Lint fixes
* Use the built-in rest api to manage woocommerce_coming_soon_banner_dismissed user meta
* Reset woocommerce_coming_soon_banner_dismissed on login
* Fix lint issues and add back wp_login hook to reset banner dismiss user meta
* Use constant for user meta field
* Update woocommerce_coming_soon_banner_dismissed user meta when X button is clicked
* Restrict user meta to shop manager or admin
* Fix lint issue
* Fix lint issue
---------
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Chi-Hsuan Huang <chihsuan.tw@gmail.com>
* Set access modifier for $error_message to public and added a setter method.
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* Can only be inserted once test excludes the mini-cart template button
* Use function for testing disabled state
* Account for blocks advertise and change selector
* remove skipped tests
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
---------
Co-authored-by: github-actions <github-actions@github.com>
* Render site visibility only when launch-your-store feature flag is on
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* fix: cookie path in private link sharing
The commit includes a fix for the LYS private link woo-share cookie entry. The path for setting the cookie has been corrected to ensure proper functionality. T
* lint
* Update coming soon page link to template editor
* Add changelog
* Hide coming soon link when current theme is classic theme
* Remove line change
* Add type
* Only query order meta for orders that were successfully retrieved from the DB.
* Add changefile(s) from automation for the following project(s): woocommerce
* Address linting issue
---------
Co-authored-by: github-actions <github-actions@github.com>
Co-authored-by: Jorge Torres <jorge.torres@automattic.com>
* CYS - fix use GPT 3.5 model
* Add changefile(s) from automation for the following project(s): woocommerce
* use constant
---------
Co-authored-by: github-actions <github-actions@github.com>