* Update PageController.php to prevent PHP warning when menu items have no position set
Update PageController.php to prevent PHP warning when menu items have no position set. This can occur when a user has permission to view WordPress admin pages but does not have permission to administer WooCommerce.
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* Make sure alert.id and action.id are defined
* Copy id from db to action
* Add changelog
* Add error message when something goes wrong while triggering note action
* Rename changelog
* Add @wordpress dependencies for customize store task
* Update webpack config to bundle wp edit-site package instead of using external
* Add customize-store task list item fill
* Update CustomizeStore task to load editor scripts and settings
* Update customize store routing path
Use /* since we want to match any path that starts with customize-store
* Add assembler-hub
* Ignore some wp packages from syncpack for customize store assembler hub
We need to use specific versions of these packages for the customize store
"@wordpress/interface", "@wordpress/router", "@wordpress/edit-site"
* Add changefile(s) from automation for the following project(s): woocommerce
* Tweak style
* Use CustomizeStoreContext and send xstate event
* Update assembler-hub style
* Fix nav width
---------
Co-authored-by: github-actions <github-actions@github.com>
- `ProductListContextProvider` provides `setIsLoading` function as well as `isLoading`.
- `Discover` uses these values from context, instead of keeping a loading state in itself.
- `FeedbackModal` calls `maybSetTimeout` when `isLoading` changes. If `isLoading` isn't truthy, and snackbar hasn't already rendered, it sets a timeout of 5 seconds to show it.
- Removed wrapping <WooFooterItem> from around Footer component, so it's no longer a child of the WooCommerce Admin `.woocommerce-layout__footer` footer.
- Removed the `position: relative` from `.woocommerce-layout__footer`. It needs to be `position: fixed`.
- Added FooterContent component to Footer, to allow the layout we want.
- Changed use of context. This now only has states for the selected tab and loading state.
- We use this context in `Tabs` and `Content` to keep track of which tab is selected, and set the selected tab.
- We also use it in `Discover` and `Extensions`, which both report loading state to the context. This allows us to use it to only render the snackbar when loading is complete.
- Extensions: moved `productList` and `setProductList` and logic for getting product list from the context provider to a state in this component. We don't need to share the list of products in the context.
- Renamed `ProductListContext`, `ProductListContextProvider` and `productListContextValue` to more generic `MarketplaceContext`, `MarketplaceContextProvider` and `marketplaceContextValue`.
- Renamed a constant and created constants for API paths.
- Only shows snackbar after content has loaded, and after a timeout. We set a date `marketplace_redesign_2023_last_shown_date` in local storage to ensure we only show one snackbar.
### Changes:
- [ ] Remove the "Venezuelan bolívar" currency (VEF)
- [ ] Remove the "Bs F" symbol (VEF)
- [ ] Update the "Bolívar soberano" currency to "Venezuelan bolívar" (VES)
- [ ] Update the "Bs.S" symbol to "Bs." (VES)
### Justification:
The official name of Venezuela's currency is Bolivar (Bs.). However, as we have had a couple of reconversions in recent years, temporary epithets have been used to distinguish the different monetary cones with a practical sense in the transition period. This is the reason why Bolivar Fuerte (Bs.F) and Bolivar Soberano (Bs.S) was used.
However, the Bolívar Fuerte (monetary cone) went out of circulation on December 3, 2018 and the Bolívar Soberano (monetary cone) started to be called only Bolívar (Bs.) since February 2019, after a reasonable period of time had passed for the population to get used to the change of monetary cone.
This came into effect with Resolution No. 19-02-01 published on February 14, 2019 by the Central Bank of Venezuela (BCV, Banco Central de Venezuela), where it can be read:
[...] _as of the effective date of this Resolution, the price of goods and services and other monetary amounts shall be expressed only in the monetary scale in effect as of August 20, 2018, making mention of "bolívares" or the symbol "Bs."_
### References:
Resolución N° 19-02-01 del Banco Central de Venezuela (February 14, 2019)
http://www.bcv.org.ve/system/files/documentos_juridicos/resolucion_cese_doble_expresion_precios_bienes_y_servicios_definitiva.pdf
* Initial set up and migration for the BlockTemplate
* Migrate remaining fields to the new SimpleProductTemplate
* Remove re-usable functions and clean up
* Add interfaces
* Add changelogs
* Remove unused id from block attributes
* Update changelog
* Address refactor suggestions
* Fix lint errors
* Add tests
* Address PR feedback
* Extend from BlockContainerInterface instead of BlockInterface
* Temporary solution to avoid extra queries
after dismissing an incentive. We will prevent doing anything else, including order queries, if there is a dismissed incentive.
---------
Co-authored-by: github-actions <github-actions@github.com>
* Save changes
* Remove restriction from the variations dropdown to let users create multiple attributes with the same name
* Add support for autogenerate slug in the create attribute endpoint
* Add a tooltip to specify the slug of the attribute when there are more than one listed in the dropdown list
* Add changelog files
* Revert filtering to the prev implementation
* Add review suggestions
* Add return description to the generate_unique_slug function description
- In the status report (server PHP version display)
- In the abstract CSV exporter (fputcsv function)
- In the legacy REST API controllers (get_raw_data function)
- In the wc_setcookie function
- In the wc_round_tax_total function
Also remove the infrastructure for WP and PHP minimum requirement notices
* Update Yoast PHPUnit Polyfill to 2.0
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
-Change "Requires PHP":
- In woocommerce.php
- In readme.txt
- In plugins/woocommerce-docs/woocommerce-docs.php
- In packages/js/create-product-editor-block/plugin-templates/$slug.php.mustache
- Change "testVersion" in phpcs.xml:
- In the root of the repository
- In plugins/woocommerce
- In plugins/woocommerce-beta-tester
- Change "require-php" and "config-platform-php" in composer.json
- Update composer.lock with more modern versions of some of the dependencies
- Remove the admin notice about the upcoming bump for PHP 7.3 users in class-wc-admin-notices.php
* Update Jetpack label and description
* Replace Jetpack with Jetpack Boost for treatment group
* Add changelog
* Append plugin_name param to Jetpack Connection page URL
* Use the correct experiment name
* Add id, description, title, and area to block template methods
* Add block template registry and controller
* Remove errant die
* Add new template properties to existing test templates
* Add new template method tests to custom block template tests
* Add template registry tests
* Add template controller tests
* Add tests around template transformer
* Use template instance for registration
* Add changelog entry
* Fix tests for block controller not be initialized by container
* Remove is_connected condition from can_view
To display WooPayments task as completed if applicable rather than an uncompleted payments task.
* Add changelog entry
* Fix failing disable test
* Add changefile(s) from automation for the following project(s): woocommerce
* Fix daily failing
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
Co-authored-by: github-actions <github-actions@github.com>
We were hitting the WCCOM API directly from the front end. However,
that limits of in terms of caching and reducing the load on WCCOM.
To prevent that, we added a REST API endpoint. This endpoint
fetches discover page content from WCCOM and puts in a transient.
This is actually how the page works in the previous version. So
we were able to reuse a lot of the code.
- Removed duplicate `Search` styles from `header.scss`.
- Removed 10px top padding from `Header`. Applied it to title, meta and search containers instead.
- Deleted duplicate search button style from `header.scss`.
- Swapped round order of search component and header meta div so tab navigation order is correct.
- Added focus style to search component.
- Reduced footer side padding on mobile.
- Changed `.woocommerce-marketplace__header-title` page title to an h1 for accessibility.
- Removed top margin from product cards – the css grid handles the gap.
- Removed margin from `.woocommerce-marketplace__product-card__description`.
- Reduced font weight of price in product cards.
- Set margin below product list header.
- Removed right margin from tab buttons – css grid handles the gap.
- Increased top padding of `.woocommerce-marketplace__content`.
Addressing linter error.
To ensure they have an implementation of the get_order_key function.
Visits to the order_received page with the id of a refund result in a fatal error.
As an alternative to #39406, this tries to solve the same issue in a
simpler way: break the "thank you" message out into its own small
template file and just include it in more places, so that no matter
the context, the order confirmation screen will always say thank you,
acknowledging that the order data has been received.
* Update beta tester build step
* Add changefile(s) from automation for the following project(s): woocommerce-beta-tester
---------
Co-authored-by: github-actions <github-actions@github.com>
* Store transactional meta in HPOS tables.
* Add transaction to the list of legacy meta, since we have getters for it, but its not stored in custom table.
* Add unit test.
* Unit test fixups + mark payment tokens as non internal for datastore.
* Use correct filename for HPOS.
* Mark payment_tokens as internal and update getter/setters accordingly.
* Fix indentation.
* Address PR review feedback.
* Revert behaviour of code that was using nullish coalescing operator.
* Add changefile(s) from automation for the following project(s): woocommerce
---------
Co-authored-by: github-actions <github-actions@github.com>
* Auto create variations and move product to variable when adding variation options
* Delete unused components
* Add tour to variation options
* Remove unneeded options
* Add changelog
* Fix types
* Fix lint errors
* Fix broken tests
* FIlter out option tags when not included in attributes
* Don't invalidate variations data when no new variations are created
nigeljamesstevenson
Jorge A. Torres
defive
RJ
Chris Runnells
Moon
Barry Hughes
Nathan Silveira
Matt Sherman
Vedanshu Jain
Ilyas Foo
Leif Singer
Chi-Hsuan Huang
github-actions
And Finally
Jon Lane
Hsing-yu Flowers
Matt Sherman
boblinthorst
github-actions[bot]
Yordan Soares
Peter Fabian
Yordan Soares
Alexandre Lara
Fernando Marichal
louwie17
Ismael Martín Alabarce
Christopher Allford
Maikel David Pérez Gómez
Ron Rennick
Néstor Soriano
jonathansadowski
Kyle Nel
Jonathan Lane
Niels Lange
Joshua T Flowers
Kader Ibrahim S
raicem
AnnaMag
Ahmed
Tam Mullen
Thomas Shellberg
Corey McKrill
Dan Q
Sam Seay
Gan Eng Chin
Cem Ünalan