Closed (fixed)
Project:
Experience Builder
Version:
0.x-dev
Component:
Page
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
11 Jul 2025 at 11:51 UTC
Updated:
28 Jul 2025 at 11:29 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #2
penyaskitoComment #4
penyaskitoComment #5
tedbowsee MR comment
Comment #6
tedbowI am still getting the anonymous if I don't change the title. Also I do think we want
$use_existing_revision_id = AutoSaveManager::contentEntityIsConsideredNew($original_entity);Because otherwise if you first create a page that hasn't been published and change the title it will never be considered new which I don't think is the intention
and that would leave the first revision showing as anonymous, which I don't think is the intention.
Comment #7
tedbowI think I found a bug that is 0.x and this branch.
Even if
$use_existing_revision_id === truea new revision is always created.I think the intention of this code, from reading the comment, is that if you
The last item does not work. there are always 2 items. Presumably for every XB page there will always be the same first revision with the same data, excepted for created and changed timestamps, because no changes have been made for this revision.
I am not sure why this happens
This relates to this issue because that first revision will always show as "anonymous"
But that might be a bigger problem that we could fix in a follow-up. If someone one knows why this is happening it and it is a small fix it might make sense to fix it here
Comment #8
lauriiiI think that's a separate issue, good catch! Let's file another issue for that 👍
Comment #9
tedbowComment #10
tedbowre #8 I created #3535515: New XB pages also create a new revision on publish even though they are intended not to. I didn't add a todo in this issue's MR because I don't think we would change what we are doing here
Comment #11
isholgueras commentedI've tested it in this branch and in

0.x. In0.xcan reproduce the issue but in this branch the user is there. Even I created a new Content Editor user (nacho) with the right permissions and works well.The code looks good to me too, so I think it's RTBC.
Comment #13
lauriiiComment #14
mayur-sose commentedTested following scenarios and changes are working as expected :