Closed (fixed)
Project:
Experience Builder
Version:
0.x-dev
Component:
Auto-save
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Apr 2025 at 14:53 UTC
Updated:
15 May 2025 at 14:59 UTC
Jump to comment: Most recent
Comments
Comment #3
meghasharma commentedWorking on it
Comment #5
meghasharma commentedI've updated the messages in \Drupal\experience_builder\Controller\ErrorCodesEnum::getMessage() to make them more helpful and actionable.
Comment #6
wim leersComment #7
wim leers@tedbow: can you propose improved UI strings? 🙏
Comment #8
tedbow@lauriii since you made this issue did you run into these messages while using XB or just reviewing?
If you ran into it using XB what circumstances where they under? Locally where there was only one person using XB or where there might have been more?
Comment #9
lauriiiI ran into this by making a change and then quickly trying to publish it after making that change. I think the error I got was "This item is unexpected." and it was really confusing because I had no idea what is "this" in the context of the message and why it was unexpected.
Comment #10
tedbow@lauriii thanks. Yeah that is the case that I could reproduce manually but not all the time.
Comment #11
tedbowCreated #3520592: [PP-1] Do not allow a user Publish request while there are pending changes to the current layout as idea how we might make this situation in #9 less likely
Comment #12
wim leersClarifying issue title; issue summary could still use an update. Per @tedbow, #3520592: [PP-1] Do not allow a user Publish request while there are pending changes to the current layout probably is the right thing to do here, because that reduces the probability of ever seeing these messages.
Comment #13
meghasharma commentedUpdated the error messages in ErrorCodesEnum::getMessage() as per feedback from @tedbow.
Comment #14
wim leersPer #13.
Comment #15
tedbowthink is good. Thanks @meghasharma. Hopefully e2e test will pass otherwise because it is
component-operations.cy.jsis probably random failComment #16
tedbowThis is still marked as "Needs design" but I think it would be ok to merge the existing MR and then improve. The updated message would at least give the user something they can do that I think should resolve the problem. We can then improve
Comment #17
lauriiiThis definitely seems like an improvement over what was there before 👍
Comment #18
tedbowOk. Let's get this and then figure how we can make it better
Comment #20
tedbowGoing to mark as fixed as #3520592: [PP-1] Do not allow a user Publish request while there are pending changes to the current layout should make it better.
If we still want to improve the messaging further, lets just reopen this issue