[FREEZE-11] Availability rules do not work properly for custom apps Created: 05/Jul/23  Updated: 05/Jul/23

Status: Open
Project: Freeze
Component/s: None
Affects Version/s: 1.8
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Martin Klaude Assignee: Andrew Warinner
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia version: 6.2.36


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

 Description   

Steps to reproduce

  1. Create a custom app as described by Magnolia
    1. Configure the content type
    2. Create the app configuration based on the content type
  1. Freeze content publication through the REST API
  2. Check the publication actions of the custom app

Expected results

  • There is a need to add IsNoGlobalFreeze to the configuration of a custom app.
  • Publication actions are not possible and the actions cannot be clicked.

Actual results

As defined in https://docs.magnolia-cms.com/freeze/index.html#_action_configuration, I expected that I need to add IsNoGlobalFreeze to the availability rules. However, the publication will be blocked whether this rule is configured or not.

Additionally, the actions for publication (like "Publish" and "Unpublish") are shown as active and can be clicked.

Workaround

-

Development notes



 Comments   
Comment by Martin Klaude [ 05/Jul/23 ]

Hint: The actual used version is 2.0 according to https://docs.magnolia-cms.com/freeze/index.html.

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