[MGNLSTK-433] Singleton paragraphs don't show 'delete' button when used on non-singleton pages Created: 17/Aug/09  Updated: 14/Mar/12  Resolved: 14/Mar/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: paragraphs
Affects Version/s: 1.1.1
Fix Version/s: 2.0

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Christian Ringele
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLSTK-436 Make inplace templating more usable Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Paragraphs used on singleton paragraph templates do not show the delete button in the edit bar.
This is implemented this was because the paragraph gets generated automatically by the template and singly this paragraph is rendered.
So out of this no delete button is needed.

But on the other hand these paragraphs were implemented with the idea, that they can be used on any other page.
If so, they cannot be removed, because they don't show up with a delete button.

Now either they must generally show a delete button -> when they are deleted on a singleton paragraph template they will be auto generated automatically again.

Or a mechanism is implemented, which hides the delete button only if the paragraph is used on a singleton paragraph template.



 Comments   
Comment by Boris Kraft [ 17/Aug/09 ]

"when they are deleted on a singleton paragraph template they will be auto generated automatically again."

The usability aspect of a delete button that doesn't in fact delete shudders me, so that is not an option. Maybe use a reference to add paragraphs that are not singletons, or extract the singleton behavior from the paragraph definition (in other words, it is not the paragraph that should decide if it is used as a singleton).

Comment by Christian Ringele [ 30/Dec/11 ]

This will be solved in STK 2.0 different.

Comment by Daniel Lipp [ 14/Mar/12 ]

According to comment from november 2011 this will be solved differently.

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