[MAGNOLIA-135] Deactivate: MetaData().setUnActivated() not recursive Created: 26/Oct/04  Updated: 23/Aug/05  Resolved: 23/Aug/05

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 2.0 Final
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Vinzenz Wyser Assignee: Sameer Charles
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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:

 Description   

is it possible to set unActivated recursively in core?

getMetaData(MetaData.ACTIVATION_INFO).setUnActivated()



 Comments   
Comment by Boris Kraft [ 08/Nov/04 ]

Currently, after deactivation the descendents meta date activation status is not changed

Comment by Sameer Charles [ 23/Aug/05 ]

since magnolia core is used for wcm and dms its not a good idea to do anything related to the application in core itself.

Generated at Mon Feb 12 03:14:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.