Edit EMA: Left Offsets are not working on React Library

[zJaaal]

Parent Issue

#26644

Problem Statement

We have an issue in the styles of our React SDK the left offsets are not being rendered as expected, we should respect the offsets that the users build in our template builder.

Steps to Reproduce

Here are the screenshots of the issue:

Layout

You can see that there's an offset between the columns

Editor

See in the editor how the offset is not where it should be

NextJS Page

And here we can see that the Next Page has the same issue

Acceptance Criteria

• The offsets should render correctly in the Editor and in the Next Page

dotCMS Version

master - latest

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

[fmontes]

We need to update the libraries and update the nextjs example to test this.

[KevinDavilaDotCMS]

Passed Internal QA

Tested in Master

Screen.Recording.2024-01-25.at.17.30.41.mov

[bryanboza]

we need some work here, seems we are not respecting the layout design

Screen.Recording.2024-02-21.at.2.13.50.PM.mov

[zJaaal]

@bryanboza can you provide the exact docker image you are using? Because I'm in dotcms/dotcms:master_07b2f28 and I'm not able to reproduce this.

Screen.Recording.2024-02-21.at.5.34.43.PM.mov

[zJaaal]

After some research I made. Looks like this issue and other ones are related to Vercel hosting cache. It does not send the new data that we modified in the editor but the cache it generated on first load. It looks like we can do something in our example to make it work, but we need to look for the best approach. This is not an issue or an error in the code but a problem with the hosting service we are using.

cc: @bryanboza @fmontes

[fmontes]

@bryanboza Updated the vercel deploy, working now.

[bryanboza]

Fixed, tested on the last vercel server version and now this is working as expected, tested on qamaster server!