You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I am encountering an issue with Newspack Campaigns where prompts configured to display based on specific tags do not behave as expected. When multiple prompts are set up with different tags, the last created prompt appears on all archive pages and the home page, regardless of the tag settings.
To Reproduce
Go to the Newspack Campaigns section.
Create a prompt and configure it to display on posts with a specific tag (e.g., 'Tag1').
Verify that this prompt displays correctly on posts with 'Tag1'.
Create another prompt and configure it to display on posts with a different tag (e.g., 'Tag2').
Notice that the second prompt not only appears on posts with 'Tag2' but also on all archive pages and the home page, despite the tag configuration.
Screenshots
Expected behavior
Each prompt should only appear on posts with their configured tags and not affect the display on archive pages or the home page unless specifically set to do so. The expected behavior is for the prompts to adhere strictly to their tag-based visibility settings without overlapping or misfiring on unrelated pages.
The text was updated successfully, but these errors were encountered:
Describe the bug
I am encountering an issue with Newspack Campaigns where prompts configured to display based on specific tags do not behave as expected. When multiple prompts are set up with different tags, the last created prompt appears on all archive pages and the home page, regardless of the tag settings.
To Reproduce
Screenshots
Expected behavior
Each prompt should only appear on posts with their configured tags and not affect the display on archive pages or the home page unless specifically set to do so. The expected behavior is for the prompts to adhere strictly to their tag-based visibility settings without overlapping or misfiring on unrelated pages.
The text was updated successfully, but these errors were encountered: