BB-24920: Customer Dashboard (#40278)

* BB-24942: Added new enpoint for customer dashboard page (#40151)
- added customer dashboard controller

* BB-24993: [Frontend] Create layout for Dashboard Page (#40208)
- added base scructure
- show title just Name
- added base styles

* BB-25132: Add titles for Dashboard and Conversations pages
- updated navigation.yml files in CustomerBundle and ConversationBundle

* BB-25132: Add titles for Dashboard and Conversations pages
- added ACL for oro_customer_frontend_customer_user_dashboard_index route

* BB-24998: [Frontend] Implement Charts (#40179)

* BB-24997: [Frontend] Implement compact view for slider with products (#40336)

* BB-25142: Add Purchase Volume Chart
- added a new purchase_volume_chart
- added PurchaseVolumeChartDataProvider layout data provider
- updated layout and twig templates for customer dashboard page
- added unit and functional tests

* BB-24994: [Frontend] Implement new template for quick access menu (#40266)
- added a new oro_customer_dashboard_quick_access_menu storefront menu
- updated twig and layout templates

* BB-24995: [Frontend] Implement datagrid widget (#40337)

* BB-24996: [Frontend] Implement template for News section (#40305)
- template and styles

* BB-25179: Add recommended products section
- added 2 customer dashboard recommended products content blocks for demo data
- added 2 customer dashboard promotional content content blocks for demo data
- updated ContentBlockDataProvider layout data provider
- updated layout and twig templates
- updated unit and functional tests

* BB-25205: Update customer dashboard quick access menu
- updated navigation.yml files for oro_customer_dashboard_quick_access_menu menu

* BB-25193: Add possibility to add to content of content block data attr
- updated configuration for html_purifier

* BB-25208: Forbid delete content block if it's used in theme configuration
- added getThemeConfigurationOptionsNamesByType method into ThemeConfigurationProvider that returns all options names by option type
- updated ContentBlockVoter
- updated unit tests

* BB-25187: Update orders demo data
- updated orders demo fixture

* BB-25127: [Frontend] Charts RTL (#40404)

* BB-24920: Customer Dashboard

* BB-25179: Add recommended products section

* BB-24920: Customer Dashboard
- added colors for chart

* BB-25148: Add Grid 'My Latest Orders' (#40414)
- added Grid 'My Latest Orders'

* BB-25142: Add Purchase Volume Chart

* BB-25189: Add 'Open Quotes' widget (#40495)
- added datagrid

* BB-25191: Add 'My Checkouts' widget (#40491)
- added datagrid

* BB-25192: Add 'Requests For Quote' widget (#40509)
- added datagrid

* BB-25190: Add 'My Shopping Lists' widget (#40527)
- added datagrid

* BB-25233: Allow the use of widgets on storefront (#40518)
- added logic that allow the use of widgets on storefront
- added a new customer_dashboard_datagrid content_widget
- updated fixtures
- added new content_widget layout block type
- updated acl voter
- updated unit tests
- updated layout and twig templates

* BB-25233: Allow the use of widgets on storefront
- added fixtures for already installed applications

* BB-25232: Replace the form with the 'Contact Us' widget on the 'Contact Us' page
- replaced the using the Contact Us form on the contact_us widget on the Contact Us page

* BB-25190: Add 'My Shopping Lists' widget

* BB-25233: Allow the use of widgets on storefront

* BB-25190: Add 'My Shopping Lists' widget (#40555)

* BB-25190: Add 'My Shopping Lists' widget

* BB-25263: Final code review (#40567)
- moved styles to FrontendBundle

* BB-25296: Add support for defining predefined values for content_block_selector and content_widget_selector theme options (#40604)
- added contact_us_form theme options
- updated layout template from ContactUs bridge bundle
- added support for defining predefined values for content_block_selector and content_widget_selector
- updated theme.yml file
- updated layout and twig templates for customer dashboard page
- updated unit tests

* BB-25186: Changelog & documentation (#40612)

* BB-25000: Add Behat tests for Customer Dashboard (#40676)

* BB-25356: XSS tests (#40714)

* BB-25395: Mini Grids are displayed without permissions (#40758)
- changed translations for customer dashboard page
- updated logic for ThemeConfigurationProvider, now it takes into account the default value for options
- added check on permission into CustomerDashboardDatagridContentWidgetType
- updated unit and functional tests

* BB-24920: Customer Dashboard
- removed icon for a chart

* BB-25407: Impossible to edit text in customer-dashboard-promotional-content content block (#40768)

---------

Co-authored-by: kotliarrr <[email protected]>
Co-authored-by: Yuliya Nedayvoda <[email protected]>
Co-authored-by: Dmytro Sherstiuk <[email protected]>
Co-authored-by: mkotliar <[email protected]>
Co-authored-by: Dima Sherstuyk <[email protected]>
Co-authored-by: Viacheslav Chekanovskiy <[email protected]>
Co-authored-by: Daria Hanzenko <[email protected]>

Author: 7 people

backend/configuration/yaml/datagrids.rst

@@ -682,6 +682,24 @@ There is the option that allows to turn off Datagrid Settings over datagrids.yml
 
 See for more information :ref:`Frontend Datagrid <customizing-data-grid-in-orocommerce-frontend>`.
 
+itemsCounter
+~~~~~~~~~~~~
+
+transTemplate
+"""""""""""""
+
+type: ``string``
+
+There is an option that allows setting of a translation template for the datagrid items counter.
+
+.. code-block:: yaml
+
+    grid-name:
+        options:
+            toolbarOptions:
+                itemsCounter:
+                    transTemplate: 'oro_frontend.datagrid.pagination.totalRecords.ordersPlural'
+
 jsmodules
 ^^^^^^^^^
 

backend/entities/customize-datagrids/backend/advanced-grid-configuration.rst

@@ -500,6 +500,22 @@ The "There are no users" message is shown for an empty grid and "No users were f
             my_custom_empty_grid_message: 'There are no users'
             my_custom_empty_filtered_grid_message: 'No users were found to match your search. Try modifying your search criteria...'
 
+Problem 12
+~~~~~~~~~~
+
+*I want to hide the workflow step column that is rendered in the grid.*
+
+**Solution**:
+
+    .. code-block:: yaml
+
+        services:
+            oro_rfp.datagrid.listener.column:
+                class: 'Oro\Bundle\WorkflowBundle\Datagrid\HideWorkflowStepColumnListener'
+                tags:
+                    - { name: kernel.event_listener, event: oro_datagrid.datagrid.build.before.rfp-requests-grid, method: onBuildBefore }
+
+
 **Related Articles**
 
 * :ref:`Datagrids <data-grids>`

bundles/commerce/CMSBundle/content-widgets/index.rst

@@ -309,6 +309,11 @@ For example:
 
     {{ entity.content | oro_html_sanitize | render_content }}
 
+Also, it is possible to use the widget twig function.
+
+.. code-block:: twig
+
+    {{ widget('widget_name') }}
 
 
 Display Label for Content Widget in Layout
@@ -330,3 +335,24 @@ You can display these variables in the following ways:
                     '=data["locale"].getLocalizedValue(data["labels"])'
 
     ...
+
+Render a Content Widget in the Layout
+-------------------------------------
+
+Content widgets can be rendered by unique `name` using the `content_widget` block type:
+
+.. code-block:: yaml
+
+
+    layout:
+        actions:
+            - '@add':
+                id: marketing_widget # unique layout block id
+                parentId: page_content
+                blockType: content_widget
+                options:
+                    name: marketing-widget # unique content widget name
+
+**Note**
+
+An administrator can rename or delete a defined content widget. So if there is no content widget with a defined name, this may be caused by a typo in a widget name or the non-existence of the widget itself; nothing is rendered, and no errors are displayed. A `notice` message is written to the log.

code_examples/commerce/content_widget/copyright/Tests/Behat/Features/content_widget_crud.feature

@@ -45,7 +45,7 @@ Feature: Content Widget CRUD
 
   Scenario: Check content widgets datagrid
     When go to Marketing/ Content Widgets
-    Then there is 4 records in grid
+    Then there is 9 records in grid
     And I should see following grid:
       | Name       | Description             | Type      | Layout |
       | copyright1 | copyright1_description2 | Copyright |        |

frontend/storefront/theme-configuration.rst

@@ -46,6 +46,11 @@ The theme configuration has the following option types:
 |                              | Previews keys depend on content block |
 |                              | alias.                                |
 +------------------------------+---------------------------------------+
+| `content_widget_selector`    | A single field is used to choose one  |
+|                              | content widget from a list. The names |
+|                              | are provided dynamically. Previews    |
+|                              | keys depend on content widget names.  |
++------------------------------+---------------------------------------+
 | `product_page_template`      | A single field is used to choose one  |
 |                              | page template from a list (static     |
 |                              | values: default, tabs, wide).         |
@@ -201,3 +206,27 @@ To validate theme configuration options, use the following command:
 .. code-block:: none
 
    bin/console oro:theme:configuration:validate
+
+How-To Guides
+-------------
+
+Problem 1
+~~~~~~~~~
+
+*I want to forbid deleting entities that are stored in the theme configuration as a value of option.*
+
+**Solution**:
+
+    .. code-block:: yaml
+
+        services:
+            oro_cms.acl.voter.content_widget:
+                class: Oro\Bundle\ThemeBundle\Acl\Voter\ThemeConfigurationDependencyDeleteVoter
+                arguments:
+                    - '@oro_entity.doctrine_helper'
+                    - '@oro_theme.provider.theme_configuration'
+                    - 'content_widget_selector'
+                calls:
+                    - [setClassName, ['Oro\Bundle\CMSBundle\Entity\ContentWidget']]
+                tags:
+                    - { name: security.voter }