4 results found

1. Restore access to SendGrid

   Before CMS 12 (and/or Commerce 14, DXP customers had access to SendGrid to log in directly at Sendgrid to see statistics on emails sent, bounce rates, open rates etc. This access was revoked as clients upgraded and the DXP environments were switched out.
   Emails are fundamental for any commerce solution and I don't see any justifiable reason that DXP customers shouldn't at least have read-only access to SendGrid directly to self serve information on their email deliverability health.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  0 comments  ·  Other  ·  Delete…  ·  Admin →

2. Using HTTP/2 calls from the Server

   HTTP/2 is more performant than the current HTTP 1.1 and it is already available on the Cloudflare side, it would nice if it could be used when integrating with other systems. Faster calls on the server should add to the overall speed of the application.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  0 comments  ·  Delete…  ·  Admin →

3. Nested Content Issues

   Nested Content Issues

   I’ve been trying to create blocks with content areas, where some blocks are nested inside others due to the structure. I’ve identified two scenarios:

   Manual tree creation from scratch:
   When building the “tree” manually, the CMS seems to save the changes, but those changes are not published in the corresponding child block. Instead, they appear to be stored at the top-level parent component. As a result, the system detects that nested components exist, but their configuration/content is missing — leading to empty components being sent to the frontend.

   Using pre-existing components:
   When assembling the “tree” using already created blocks, the system correctly detects and publishes them. This suggests that the issue specifically affects newly created components within the same tree.

   This behavior can significantly impact the content editing experience, especially for users familiar with the CMS PaaS, where nested content creation and publishing works seamlessly.

   Nested Content Issues

   I’ve been trying to create blocks with content areas, where some blocks are nested inside others due to the structure. I’ve identified two scenarios:

   Manual tree creation from scratch:
   When building the “tree” manually, the CMS seems to save the changes, but those changes are not published in the corresponding child block. Instead, they appear to be stored at the top-level parent component. As a result, the system detects that nested components exist, but their configuration/content is missing — leading to empty components being sent to the frontend.

   Using pre-existing components:
   When assembling the “tree” using already… more

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  1 comment  ·  Editing Content and Visual Builder  ·  Delete…  ·  Admin →

4. text editor missing formatting

   This appears to be a current bug. As our users were previously able to edit content using the WYSIWYG editor w/ formatting options, vs. having to edit in html.

   please restore this functionality.

   •  

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Closed  ·  1 comment  ·  Editing Content and Visual Builder  ·  Delete…  ·  Admin →