Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[uMarketingSuite package] Segmentation is not applicable for the Tags control type #13959

Open
anvont opened this issue Mar 14, 2023 · 3 comments
Labels
state/needs-more-info We don't have enough information to give a good reply type/bug

Comments

@anvont
Copy link

anvont commented Mar 14, 2023

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

10.3.2

Bug summary

Segmentation feature of the uMarketingSuite package is not applicable for the Tags control type (cannot save the values on the personalised version)​.

Thir-party response:
"We use a built-in Umbraco feature “segment variation” to create personalized variants of a page. We have no control over the way specific property editors interact with these variants.​
The issue mentioned seems to be a bug specific to Tags which apparently does not support page variants which is something uMarketingSuite cannot resolve but Umbraco should fix. "

Specifics

No response

Steps to reproduce

  1. Allow Segmentation for the Tags field. ​
  2. Input values to the personalised version. ​
  3. Hit save.
TagsControlType.webm

Expected result / actual result

Expected Result: ​

The values are saved separately for each version. ​

Actual Result: ​

All inputted values are lost.

@github-actions
Copy link

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
Copy link
Member

Zeegaan commented Mar 21, 2023

Hmmm, I cannot reproduce this, can you see if I'm doing anything wrong here 🤔

  • Created a document type with segments allowed
  • Added tags property editor with vary by segment.
  • Created a content node with a default & "test" segment
  • Add "Aaa" tag to default
  • Save and publish default
  • Add "Bbbb" tag to "test" segment
  • Save and publish both

TagsWithSegments

@Zeegaan Zeegaan added the state/needs-more-info We don't have enough information to give a good reply label Mar 21, 2023
@anvont
Copy link
Author

anvont commented Mar 28, 2023

Hi @Zeegaan ,

Can you please try again with a Multilingual Site?

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state/needs-more-info We don't have enough information to give a good reply type/bug
Projects
None yet
Development

No branches or pull requests

2 participants