[MGNLSYNC-13] Content is synchronized even when is not activated Created: 14/Aug/12  Updated: 29/Mar/22  Resolved: 04/Oct/12

Status: Closed
Project: Magnolia Synchronization Module
Component/s: None
Affects Version/s: 1.1.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-4553 Current state of areas was always act... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Team: Nucleus

 Description   

Synchronization module should send content which is already activated but in some cases now current content is used.
Result of test:

  • headline of demo-project was modified -> on public previous headline was shown
  • text in one article was modified -> modified text was also on public


 Comments   
Comment by Jan Haderka [ 04/Oct/12 ]

This issue is duplicate/side effect of MAGNOLIA-4553.

Generated at Mon Feb 12 07:39:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.