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 Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+10-6Lines changed: 10 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -127,18 +127,18 @@ We use symbolic links for topics that are the same across versions of Magento. A
127
127
128
128
When you create a new topic (create a new `.md` file) and its content is the same for 2.2 and 2.3 versions, create a symbolic link.
129
129
130
-
For example, if you created a new file for v.2.2---`guides/v2.2/install-gde/new-doc-topic.md`---and its content is the same for v.2.3, use the command below to create the symbolic link.
130
+
For example, if you created a new file for v.2.2: `guides/v2.2/install-gde/new-doc-topic.md`and its content is the same for v.2.3, use the command below to create the symbolic link.
If you have an image that is identical between versions, it should placed in `/common/images`. Please optimize images before committing them to the repository.
141
-
If done correctly, the symbolic link path will start with 3 or 4 instances of `../`, as the above example shows.
141
+
If done correctly, the symbolic link path will start with 2-4 instances of `../`, as the above example shows. If possible, check a symlinked file within the same folder to ensure the proper pathing.
142
142
143
143
### Remove a symbolic link
144
144
@@ -149,11 +149,15 @@ The removal should use the `git rm` command specifically. Deleting the file thro
- description: Added the following information to the [Set up Elasticsearch](https://devdocs.magento.com/guides/v2.3/cloud/project/project-conf-files_services-elastic.html)<br/>topic
35
+
in the _Cloud Guide_–<br/>- Recommendation to always set up<br/>Elasticsearch
36
+
as a fallback option if using a third-party search tool<br/>- Instructions for
- description: Added the documentation for the [DynamicRowsRecord](https://devdocs.magento.com/guides/v2.2/ui_comp_guide/components/ui-dynamicrows-record.html)
- description: Moved the `CategoryInterface` attributes to a separate [topic](https://devdocs.magento.com/guides/v2.3/graphql/product/category-interface.html)
- description: Added an "Errors" section to the [changeCustomerPassword mutation](https://devdocs.magento.com/guides/v2.3/graphql/mutations/change-customer-password.html)
- description: Added a warning to ensure that the [CRYPT_KEY](https://devdocs.magento.com/guides/v2.3/cloud/env/variables-deploy.html#crypt_key) deploy
127
+
variable for Magento Commerce Cloud environments is set in the Project Web UI
- description: Added documentation for the [Folder tree widget](https://devdocs.magento.com/guides/v2.3/javascript-dev-guide/widgets/widget-folder-tree.html)
- description: Added the following new topics to the _Magento Functional Testing Framework Guide_<br/>- [Selectors](https://devdocs.magento.com/mftf/docs/guides/selectors.html)<br/>-
Copy file name to clipboardExpand all lines: _includes/config/setup-cron_2.2_about.md
+1Lines changed: 1 addition & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -9,5 +9,6 @@ Magento uses cron for two sets of tasks, and for each, cron can run with a diffe
9
9
* Web server PHP plug-in configuration: Two other cron jobs are used by the [Component Manager and System Upgrade utilities]({{ page.baseurl }}/comp-mgr/bk-compman-upgrade-guide.html).
10
10
11
11
{: .bs-callout-warning }
12
+
12
13
* To avoid issues during installation and upgrade, we strongly recommend you apply the same PHP settings to both the PHP command-line configuration and to the PHP web server plug-in's configuration. For more information, see [Required PHP settings]({{ page.baseurl }}/install-gde/prereq/php-settings.html).
13
14
* In a multi-node system, crontab can run on only one node. This applies to you only if you set up more than one webnode for reasons related to performance or scalability.
0 commit comments