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
Copy file name to clipboardExpand all lines: api/authentication/oauth-client-credentials.rst
+9
Original file line number
Diff line number
Diff line change
@@ -72,3 +72,12 @@ An example of an API request:
72
72
Authorization: Bearer your access token
73
73
74
74
.. note:: Access tokens for back-office and storefront API are not interchangeable. If you attempt to request data for the storefront API with a token generated for the back-office application, access will be denied.
75
+
76
+
77
+
.. admonition:: Business Tip
78
+
79
+
|What is B2B eCommerce| and how does it differ from B2C? Read our guide to find out.
Copy file name to clipboardExpand all lines: api/enabling-api-feature.rst
+8
Original file line number
Diff line number
Diff line change
@@ -14,5 +14,13 @@ on the :ref:`global <admin-configuration-application>` and :ref:`organization <a
14
14
on the :ref:`global <admin-configuration-application>`, :ref:`organization <admin-configuration-application-org>`, and :ref:`website <admin-configuration-application-website>` levels.
15
15
16
16
17
+
.. admonition:: Business Tip
18
+
19
+
Explore our guide on eCommerce to find out |B2B ecommerce meaning|, benefits, and examples.
Copy file name to clipboardExpand all lines: api/http-methods.rst
+10
Original file line number
Diff line number
Diff line change
@@ -63,6 +63,11 @@ Below is a table summarizing HTTP methods by its idempotency and safety:
63
63
+-------------+------------+------+
64
64
65
65
66
+
.. admonition:: Business Tip
67
+
68
+
Researching |B2B eCommerce platforms|? Explore our platform comparison guide to help you make an informed decision.
69
+
70
+
66
71
.. _web-services-api--http-methods--get:
67
72
68
73
GET
@@ -130,8 +135,13 @@ On successful deletion, the HTTP response status code 204 (No Content) returns w
130
135
If you DELETE a resource, it is removed. Repeatedly calling DELETE on that resource will often return a 404 (NOT FOUND) status code since it was already removed and, therefore, is no longer findable.
You can organize an OroPlatformbased application code within :ref:`Symfony bundles <how-to-create-new-bundle>` or plain directories. Bundle-less directory structure support was added in OroPlatform v5.1 to follow the Symfony best practices and lower the entry level for new developers.
11
+
You can organize an OroPlatform-based application code within :ref:`Symfony bundles <how-to-create-new-bundle>` or plain directories. Bundle-less directory structure support was added to OroPlatform v5.1 to follow the Symfony best practices and lower the entry level for new developers.
12
12
This guide overviews the bundle-less structure and explains how to migrate the application code from the bundles-based to bundle-less structure.
13
13
14
-
.. note:: The use of **bundle-less structure** is optional. However, for individual customization and expansion of Oro functionality or in other cases when creation a new bundle is impractical, a bundle-less structure can be used.
14
+
.. note:: The use of **bundle-less structure** is optional. However, you can use a bundle-less structure for individual customization and expansion of Oro functionality or when creating a new bundle is impractical.
15
15
16
-
The *bundle-less structure* includes the following (configuration and directory structure changes) application structure changes.
16
+
The *bundle-less structure* includes the application structure changes outlined below (configuration and directory).
17
17
18
-
Application-level structure Changes
18
+
Application-level Structure Changes
19
19
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
20
20
21
21
.. code-block:: none
22
22
23
-
24
23
oro-application/
25
24
├── assets/
26
-
| |── your-assets-dir # Here we can store our (scss, js, image, fonts) resources.
25
+
| |── your-assets-dir # Here we can store the (scss, js, image, fonts) resources.
27
26
| └── ...
28
27
├── config/
29
28
│ ├── batch_jobs # Import and Export Configuration.
In order to port an existing bundle to a bundle-less structure, you must update the directory structure to the one shown above. There is no automatic tool for this update, so you must move your code following these guidelines:
133
+
To port an existing bundle to a bundle-less structure, you must update the directory structure to the one shown above. There is no automatic tool for this update, so you must move your code following these guidelines:
.. important:: All application-level workflows can be stored in separate directories, but must be registered in the /config/oro/workflows.yml file (via an import directive).
265
+
.. important:: All application-level workflows can be stored in separate directories but must be registered in the /config/oro/workflows.yml file (via an import directive).
267
266
268
267
269
268
Processes
@@ -376,7 +375,7 @@ System Configurations
376
375
Extension and Configuration Moving
377
376
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
378
377
379
-
1. Create Extension and Configuration classes in ``/src/Configuration``
378
+
1. Create Extension and Configuration classes in ``/src/Configuration``.
380
379
381
380
.. code-block:: php
382
381
@@ -400,7 +399,7 @@ Extension and Configuration Moving
400
399
}
401
400
}
402
401
403
-
2. Register the extension in ``AppKernel::build``
402
+
2. Register the extension in ``AppKernel::build``.
404
403
405
404
.. code-block:: php
406
405
@@ -415,19 +414,23 @@ Extension and Configuration Moving
415
414
Themes & Layouts
416
415
~~~~~~~~~~~~~~~~
417
416
418
-
1. Assets for themes should be moved to ``/src/assets/{your_theme_dir}/``
417
+
1. Assets for themes should be moved to ``/src/assets/{your_theme_dir}/``.
419
418
2. Admin theme configuration:
420
-
- ``/config/oro/assets.yml``
421
-
- ``/config/oro/jsmodules.yml``
422
-
3. Storefront Themes and layouts should be placed in ``/templates/layouts/{your_theme_dir}/``
Oro applications are open source and may be deployed to the on-premise environments. Deployment method could be
68
-
different depending on organization requirements and infrastructure. You can design your custom deployment process,
69
-
noting the following recommendations:
64
+
Oro applications are open source and can be deployed to on-premise environments. Deployment methods can vary depending on organization requirements and infrastructure. You can design your custom deployment process but make sure you follow the recommendations below:
70
65
71
-
#) Take into account recommendations in |Symfony Application Deployment| documentation
72
-
#) Lock all dependencies with |composer.lock| before taking the code to production
73
-
#) Warm up the application cache in production mode
74
-
#) Disable access to `index_dev.php`
75
-
#) Configure crontab and run web socket server
66
+
#) Follow the advice outlined in the |Symfony Application Deployment| documentation.
67
+
#) Lock all dependencies with |composer.lock| before taking the code to production.
68
+
#) Warm up the application cache in production mode.
69
+
#) Disable access to `index_dev.php`.
70
+
#) Configure crontab and run web socket server.
76
71
77
72
Oro applications are scalable.
78
73
79
74
.. note::
80
-
As an alternative to the on-premise deployment, when you created your application following recommendations
81
-
:ref:`above <application-custom-code>`, you can put your application into |OroCloud|. Please contact us to
82
-
get more information.
83
-
75
+
As an alternative to the on-premise deployment, when you create your application following recommendations :ref:`above <application-custom-code>`, you can deploy your application to |OroCloud|. Please get in touch with us for more information.
0 commit comments