[uMarketingSuite package] The page is published when users click on "Save and preview" for the personalised version only. ​

[anvont]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

10.3.2

Bug summary

The page is published when users click on "Save and preview" for the personalised version only. ​

Third-party response:
"As described here this is an Umbraco bug as uMarketingSuite simply calls the Umbraco APIs to publish a specific variant and we have verified we do this correctly. However, Umbraco publishes all variants instead.​"

Specifics

No response

Steps to reproduce

Go to a personalized page. ​

Hit the Save & Preview button of that personalized content. ​

View the History on the Info tab. ​
save_and_preview.webm

Expected result / actual result

Expected Result: ​

Umbraco will publish both versions instead of simply saving them. ​

Actual Result: ​

Umbraco will only save all inputted values, and open a new tab for the preview page. ​

Note that the “Save and preview” button at the bottom of the page (which is used for the original content) still just save the works as usual.

[github-actions]

Hi there @anvont!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[Zeegaan]

I can definitely reproduce this.

Here is my test setup for using the source code to debug this:
NotifcationHandler & Composer:

• Enabled segmentation by setting {"showAllowSegmentationForDocumentTypes", true} in BackOfficeServerVariables.cs
• Created a doc type with a tags property editor, with name "Tags"
• Added my notification handler to create the test segment:

using Umbraco.Cms.Core.Composing;
using Umbraco.Cms.Core.Events;
using Umbraco.Cms.Core.Models;
using Umbraco.Cms.Core.Notifications;
using Umbraco.Cms.Core.Services;

namespace Umbraco.Cms.Web.UI;

public class MyComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder) =>
        builder.AddNotificationHandler<MemberSavedNotification, MyNotiHandler>();
}

public class MyNotiHandler : INotificationHandler<MemberSavedNotification>
{
    private readonly IContentService _contentService;

    public MyNotiHandler(IContentService contentService)
    {
        _contentService = contentService;
    }

    public void Handle(MemberSavedNotification notification)
    {
        IContent? content = _contentService.GetById(1068);
        if (content is null)
        {
            return;
        }

        string[] tags = new [] { "Bbbb", "Cccc" };
        content.SetValue("tags", tags, null, "test");
        _contentService.Save(content);
    }
}

[tristanjthompson]

Is there any update on this? We are doing some exploration/prototyping on enabling basic segmentation functionality (using 2 segments - "Default" and "Trade"), and we have seen a similar issue - when we try to publish/unpublish a single variant via the Umbraco interface, the action applies to both variants.

Example.

1. I have enabled segmentation by setting {"showAllowSegmentationForDocumentTypes", true} in BackOfficeServerVariables.cs
2. Created a segmented doctype with some segmented fields
3. Added my notification handler to create a "not created" "Trade" segment
4. Added my trade segment and published - both variants are now created/published.

Action
Unpublish just the Trade segment using the Umbraco UI (note - I have pixelated some sensitive areas of the screenshot).

Expected Result - just the Trade variant is unpublished

Actual Result - the interface initially shows just the Trade variant unpublished in the variant selector at the top, however, refreshing the page updates it and shows that both Default and Trade variants are now unpublished

I know this is slightly different, but it feels like it might be wrapped up in the same thing? Segmented variants not publishing/unpublishing correctly?