[MAGNOLIA-138] Alert user that public instance can't be found Created: 26/Oct/04  Updated: 23/Jan/13  Resolved: 17/May/06

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.0 Final
Fix Version/s: 3.0 RC1

Type: Improvement Priority: Minor
Reporter: Kyle Gabhart Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Any


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)
Date of First Response:

 Description   

When administrators attempt to activate/deactivate repository elements (content, users, roles) when no public instance is running, the action fails. This dependency is acceptable, by the fact that this action fails silently is not acceptable. An alert or error message should be displayed indicating "No Public Instance Found", or "Public site must be active to complete this action", or something to that affect.



 Comments   
Comment by Boris Kraft [ 26/Oct/04 ]

This will get more complicated when we have "surround publishing" fully implemented. In general, we will be able to publish to many places. Once workflow integration is done, the publishing will become the launch of a workflow; where customizations will be able to do stuff like publish information based on arbitrary information. There the notion of a "public instance" will be more or less gone; what remains is a workflow that might go through or not; at the same time the workflow is asynchronous and can take an arbitrary amount of time, for instance if a reviewr has to look at the content that you want to publish.

So what to do about it? Maybe if there is no place to activate to (or no workflow defined), activation could be disabled. Definitely, if the content can not be activated, the status indicater should remain unchanged (or even change to denote that activation has failed). For the future, we will need something like a log or history for activated items, for the facts outlined above (Excercise for the reader: activation to site a is successfull, to site b fails. What is the sematics?)

Comment by Philipp Bracher [ 17/May/06 ]

acitvation problems are alerted

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