You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2019. It is now read-only.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -612,11 +612,11 @@ To get detailed information about changes in Magento 2.3.0, see the [Release Not
612
612
613
613
2.2.0
614
614
=============
615
-
To get detailed information about changes in Magento 2.2.0, see the [Release Notes](https://devdocs.magento.com/guides/v2.2/release-notes/bk-release-notes.html)
615
+
To get detailed information about changes in Magento 2.2.0, see the [Release Notes](https://devdocs.magento.com/guides/v2.3/release-notes/bk-release-notes.html)
616
616
617
617
2.1.0
618
618
=============
619
-
To get detailed information about changes in Magento 2.1.0, please visit [Magento Community Edition (CE) Release Notes](https://devdocs.magento.com/guides/v2.1/release-notes/ReleaseNotes2.1.0CE.html "Magento Community Edition (CE) Release Notes")
619
+
To get detailed information about changes in Magento 2.1.0, please visit [Magento Community Edition (CE) Release Notes](https://devdocs.magento.com/guides/v2.3/release-notes/ReleaseNotes2.1.0CE.html "Magento Community Edition (CE) Release Notes")
620
620
621
621
2.0.0
622
622
=============
@@ -1637,7 +1637,7 @@ Tests:
1637
1637
* Improved backend menu keyboard accessibility
1638
1638
* Accessibility improvements: WAI-ARIA in a product item on a category page and related products
1639
1639
* Checkout flow code can work with a separate DB storage
1640
-
* <a href="https://devdocs.magento.com/guides/v1.0/release-notes/changes.html#change-devrc-unit">Unit tests moved to module directories</a>
1640
+
* Unit tests moved to module directories
1641
1641
* Addressed naming inconsistencies in REST routes
1642
1642
* Added Advanced Developer workflow for frontend developers
The members of this team have been recognized for their outstanding commitment to maintaining and improving Magento. Magento has granted them permission to accept, merge, and reject pull requests, as well as review issues, and thanks these Community Maintainers for their valuable contributions.
Copy file name to clipboardExpand all lines: app/code/Magento/Analytics/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Magento_Analytics Module
2
2
3
-
The Magento_Analytics module integrates your Magento instance with the [Magento Business Intelligence (MBI)](https://magento.com/products/business-intelligence) to use [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html) functionality.
3
+
The Magento_Analytics module integrates your Magento instance with the [Magento Business Intelligence (MBI)](https://magento.com/products/business-intelligence) to use [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html) functionality.
4
4
5
5
The module implements the following functionality:
6
6
@@ -16,8 +16,8 @@ The module implements the following functionality:
16
16
17
17
## Structure
18
18
19
-
Beyond the [usual module file structure](https://devdocs.magento.com/guides/v2.2/architecture/archi_perspectives/components/modules/mod_intro.html) the module contains a directory `ReportXml`.
20
-
[Report XML](https://devdocs.magento.com/guides/v2.2/advanced-reporting/report-xml.html) is a markup language used to build reports for Advanced Reporting.
19
+
Beyond the [usual module file structure](https://devdocs.magento.com/guides/v2.3/architecture/archi_perspectives/components/modules/mod_intro.html) the module contains a directory `ReportXml`.
20
+
[Report XML](https://devdocs.magento.com/guides/v2.3/advanced-reporting/report-xml.html) is a markup language used to build reports for Advanced Reporting.
21
21
The language declares SQL queries using XML declaration.
The Magento_CatalogAnalytics module configures data definitions for a data collection related to the Catalog module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_CatalogAnalytics module configures data definitions for a data collection related to the Catalog module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
The Magento_CustomerAnalytics module configures data definitions for a data collection related to the Customer module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_CustomerAnalytics module configures data definitions for a data collection related to the Customer module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
Copy file name to clipboardExpand all lines: app/code/Magento/InstantPurchase/README.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ Prerequisites to display the Instant Purchase button:
10
10
11
11
## Structure
12
12
13
-
In addition to [a typical file structure for a Magento 2 module](https://devdocs.magento.com/guides/v2.2/extension-dev-guide/build/module-file-structure.html)`PaymentMethodsIntegration` directory contains interfaces and basic implementation of integration vault payment method to the instant purchase.
13
+
In addition to [a typical file structure for a Magento 2 module](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/build/module-file-structure.html)`PaymentMethodsIntegration` directory contains interfaces and basic implementation of integration vault payment method to the instant purchase.
14
14
15
15
## Extensibility
16
16
@@ -22,7 +22,7 @@ All payments created for instant purchase also have `'instant-purchase' => true`
22
22
23
23
### Payment method integration
24
24
25
-
Instant purchase support may be implemented for any payment method with [vault support](https://devdocs.magento.com/guides/v2.1/payments-integrations/vault/vault-intro.html).
25
+
Instant purchase support may be implemented for any payment method with [vault support](https://devdocs.magento.com/guides/v2.3/payments-integrations/vault/vault-intro.html).
26
26
Basic implementation provided in `Magento\InstantPurchase\PaymentMethodIntegration` should be enough in most cases. It is not enabled by default to avoid issues on production sites and authors of vault payment method should verify correct work for instant purchase manually.
27
27
To enable basic implementation just add single option to configuration of payemnt method in `config.xml`:
28
28
@@ -52,7 +52,7 @@ Basic implementation is a good start point but it's recommended to provide own i
52
52
53
53
The `Magento_InstantPurchase` module does not introduce backward incompatible changes.
54
54
55
-
You can track [backward incompatible changes in patch releases](https://devdocs.magento.com/guides/v2.2/release-notes/changes/ce_changes.html).
55
+
You can track [backward incompatible changes in patch releases](https://devdocs.magento.com/guides/v2.3/release-notes/backward-incompatible-changes/reference.html).
The Magento_QuoteAnalytics module configures data definitions for a data collection related to the Quote module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_QuoteAnalytics module configures data definitions for a data collection related to the Quote module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
The Magento_ReviewAnalytics module configures data definitions for a data collection related to the Review module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_ReviewAnalytics module configures data definitions for a data collection related to the Review module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
The Magento_SalesAnalytics module configures data definitions for a data collection related to the Sales module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_SalesAnalytics module configures data definitions for a data collection related to the Sales module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
Copy file name to clipboardExpand all lines: app/code/Magento/SampleData/README.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ Installing sample data is optional.
5
5
Technically, sample data is a set of regular Magento modules, which can be deployed and installed together with the Magento instance, or later in the scope of upgrade.
6
6
7
7
## Deploy Sample Data
8
+
8
9
You can deploy sample data from one of the following sources:
9
10
10
11
* From the Magento composer repository, optionally using Magento CLI
@@ -49,9 +50,11 @@ To deploy sample data from the GitHub repository:
49
50
2. Link the sample data and your Magento instance by running: `# php -f <sample-data_clone_dir>/dev/tools/build-sample-data.php -- --ce-source="<path_to_your_magento_instance>"`
50
51
51
52
## Install Sample Data
53
+
52
54
Once the sample data is deployed, it will be installed automatically when you install or upgrade your Magento instance either by using the Magento Setup Wizard or from the command line.
53
55
54
56
## Uninstall Sample Data
57
+
55
58
To remove the sample data modules from the code base, run one of the following commands from the Magento root directory:
56
59
57
60
* If sample data was deployed from the composer repository, run: `# bin/magento sampledata:remove`
@@ -61,6 +64,7 @@ To remove the sample data modules from the code base, run one of the following c
61
64
To delete all the products and other entities provided by the sample data modules, delete the database and reinstall Magento with a clean database.
62
65
63
66
## Reinstall Sample Data
67
+
64
68
If you have deleted certain entities provided by sample data and want to restore them, take the following steps:
65
69
66
70
1. From the Magento root directory, run the following command: `# bin/magento sampledata:reset`
@@ -69,4 +73,5 @@ If you have deleted certain entities provided by sample data and want to restore
69
73
The deleted sample data entities will be restored. Those entities, which were changed, will preserve these changes and will not be restored to the default view.
70
74
71
75
## Documentation
72
-
You can find the more detailed description of sample data manipulation procedures at [https://devdocs.magento.com/guides/v2.0/install-gde/install/cli/install-cli-sample-data.html](https://devdocs.magento.com/guides/v2.0/install-gde/install/cli/install-cli-sample-data.html)
76
+
77
+
You can find the more detailed description of sample data manipulation procedures at <https://devdocs.magento.com/guides/v2.3/install-gde/install/cli/install-cli-sample-data.html>.
Copy file name to clipboardExpand all lines: app/code/Magento/Signifyd/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ The following interfaces (marked with the `@api` annotation) provide methods tha
47
47
48
48
- might be used by `Magento\Signifyd\Api\CaseRepositoryInterface` to retrieve a list of case entities by specific conditions
49
49
50
-
For information about a public API in Magento 2, see [Public interfaces & APIs](https://devdocs.magento.com/guides/v2.1/extension-dev-guide/api-concepts.html).
50
+
For information about a public API in Magento 2, see [Public interfaces & APIs](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/api-concepts.html).
51
51
52
52
## Additional information
53
53
@@ -67,12 +67,12 @@ The Debug Mode may be enabled in the module configuration. This logs the communi
67
67
68
68
The Magento_Signifyd module does not introduce backward incompatible changes.
69
69
70
-
You can track [backward incompatible changes in patch releases](https://devdocs.magento.com/guides/v2.0/release-notes/changes/ee_changes.html).
70
+
You can track [backward incompatible changes in patch releases](https://devdocs.magento.com/guides/v2.3/release-notes/backward-incompatible-changes/reference.html).
71
71
72
72
### Processing supplementary payment information
73
73
74
74
To improve the accuracy of Signifyd's transaction estimation, you may perform these operations (links lead to the Magento Developer Documentation Portal):
-[Retrieve payment method for a placed order](https://devdocs.magento.com/guides/v2.2/payments-integrations/signifyd/signifyd.html#retrieve-payment-method-for-a-placed-order)
78
+
-[Retrieve payment method for a placed order](https://devdocs.magento.com/guides/v2.3/payments-integrations/signifyd/signifyd.html#retrieve-payment-method-for-a-placed-order)
The Magento_WishlistAnalytics module configures data definitions for a data collection related to the Wishlist module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.2/advanced-reporting/modules.html).
3
+
The Magento_WishlistAnalytics module configures data definitions for a data collection related to the Wishlist module entities to be used in [Advanced Reporting](https://devdocs.magento.com/guides/v2.3/advanced-reporting/modules.html).
0 commit comments