I'd like your opinions on a deletion dilemma

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

I'd like your opinions on a deletion dilemma

Dan Wilga-2
There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference
, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set "
Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]


mm_recycle_test4.txt (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

Adam Franco
Administrator
Hi Dan,

I actually never realized that this was how deletes worked.

The option most intuitive to me is #2: For nodes on multiple pages, deleting one page drops that reference to the node, leaving it intact (and visible) on other pages. Nodes would only get deleted when they are attached to a single page that is in the process of being deleted.

#2 makes more sense to me (and should have fewer weird edge cases) than multiple bins, or just deleting nodes right away. For example, if a profile node is attached to two department pages and one of those department pages gets deleted it doesn't make sense that the node would get removed from the other page that was not edited directly.


Adam

--

Adam Franco
Senior Software Engineer - Web Applications
Library and Information Services
Middlebury College
Middlebury, VT 05753
[hidden email]
802.443.2244

On Thu, Sep 18, 2014 at 10:26 AM, Dan Wilga <[hidden email]> wrote:
There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set " Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=685438.780c6126d238396bdd2f98c1d84c15c7&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706172

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

Jay Dansand
In reply to this post by Dan Wilga-2
I'd vote for option #2.

If deleting a page has a side-effect of deleting nodes from other pages, it makes the whole business of sharing nodes on pages onerous. It'll be hard to explain well (it really feels counterintuitive to me: "I am deleting page X, why should this affect page Y?") and adds administrative overhead to the users.

When a user attempts to delete a page, consider the three ways this can work out: 1) they actually want the nodes to be deleted (I don't think this has ever come up in our use cases), 2) they heed the warning text and then have to manually go through and remove the shared nodes first (cumbersome), or 3) they don't read or understand the warning (more likely) and suddenly the node vanishes from multiple pages and nobody notices it.

Changing bin behavior as in option #2 avoids the pitfalls and I think represents (at least for us) the more common use case.



On Sep 18, 2014, at 9:27 AM, Dan Wilga <[hidden email]> wrote:

There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference
, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set "
Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=849053.214f550f57fa54a976b5f2d087b6d379&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

<mm_recycle_test4.txt>

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706173

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

McBride, Ian S.
In reply to this post by Dan Wilga-2
Either way, it would be nice to include a message on the delete confirmation page saying "this content will continue to be shown on: [list of pages]" or "this content will also be deleted from: [list of pages]".


Ian McBride
[hidden email]<mailto:[hidden email]>
skype: [hidden email]<mailto:[hidden email]>
Web Technologies & Services
Information Technology Services
Middlebury College

From: Jay Dansand <[hidden email]<mailto:[hidden email]>>
Reply-To: Monster Menus Development <[hidden email]<mailto:[hidden email]>>
Date: Thursday, September 18, 2014 at 10:43 AM
To: Monster Menus Development <[hidden email]<mailto:[hidden email]>>
Subject: Re: I'd like your opinions on a deletion dilemma

I'd vote for option #2.

If deleting a page has a side-effect of deleting nodes from other pages, it makes the whole business of sharing nodes on pages onerous. It'll be hard to explain well (it really feels counterintuitive to me: "I am deleting page X, why should this affect page Y?") and adds administrative overhead to the users.

When a user attempts to delete a page, consider the three ways this can work out: 1) they actually want the nodes to be deleted (I don't think this has ever come up in our use cases), 2) they heed the warning text and then have to manually go through and remove the shared nodes first (cumbersome), or 3) they don't read or understand the warning (more likely) and suddenly the node vanishes from multiple pages and nobody notices it.

Changing bin behavior as in option #2 avoids the pitfalls and I think represents (at least for us) the more common use case.



On Sep 18, 2014, at 9:27 AM, Dan Wilga <[hidden email]<mailto:[hidden email]>> wrote:

There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set" Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=849053.214f550f57fa54a976b5f2d087b6d379&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

<mm_recycle_test4.txt>

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=685439.7e7cbccf9bb225cf8471bffe1cb67503&n=T&l=monster_menus&o=706173

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

---
You are currently subscribed to monster_menus as: [hidden email].
To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706174
or send a blank email to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: I'd like your opinions on a deletion dilemma

Hilary Caws-Elwitt
In reply to this post by Dan Wilga-2

Another vote for option #2! And I like Ian’s suggestion of a message, too (not crucial though).

 

--

Hilary Caws-Elwitt

IT Analyst - Five Colleges, Inc. - http://www.fivecolleges.edu

97 Spring St, Amherst MA 01002

[hidden email] - 413-542-4022

 

From: Dan Wilga [mailto:[hidden email]]
Sent: Thursday, September 18, 2014 10:27 AM
To: Monster Menus Development
Subject: I'd like your opinions on a deletion dilemma

 

There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set " Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=1034715.d8dc340b0014c740c37e95754e54e1f3&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706199

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

Dan Wilga-2
In reply to this post by Dan Wilga-2
There's a corollary to the original question:

When Page A and Page B contain the same node and THE NODE is permanently deleted (without using a bin), it disappears from both pages.

If bins are used, then deleting THE NODE causes two bins to be created, both of which contain the node. If either bin is emptied, the node remains in the other bin, and can potentially be restored.

1. Should only one bin be created, and the node left visible on the other page?

2. Or should emptying either bin delete the node in both places, for consistency with the no-bin case?
I think this would also be more consistent with #2, below.

On 9/18/14 10:26 AM, Dan Wilga wrote:
There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference
, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set "
Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685500.19fa7de7038497527f6a88cf1629251d&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]


---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706352

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: I'd like your opinions on a deletion dilemma

Jay Dansand
In reply to this post by Dan Wilga-2

So, if I understand it correctly, with the current behavior:

 

1)    Node “Foo” appears on pages “Bar” and “Baz”.

2)    (with bins enabled) If you delete the node from Bar, then it is also removed from Baz, and placed into recycling bins under both Bar and Baz.

3)    If you empty Bar’s recycling bin, then the node still exists in Baz’s recycling bin.

 

I think the intent of our votes for #2 in the previous question was that taking an action on page Bar shouldn’t have an implicit side-effect on page Baz.  At least, that was my argument.  In this case, the current behavior is almost perfect, but I’d vote in favor of option #1: deleting the node on Bar does not remove it from Baz. Perhaps there should be a checkbox on mm_ui_node_delete_confirm that asks “Should this node be removed from all other pages as well?” in which case the current behavior (separate, disconnected recycling bins) takes over.

 

As far as the current no-bin behavior goes, that’s actually a problem for us and we’re planning to write another mm_tweak to prompt for permanently deleting the node from all pages or just remove the reference from the current page.  Or, if you all would be onboard with changing that behavior upstream, it’d make it more consistent with the current (or proposed change #1) behavior when using bins… J


-- 
Jay Dansand '08
Senior Web Application Developer
Technology Services, Seeley G. Mudd Library
Lawrence University
Appleton, WI
920-832-6585
[hidden email]

From: Dan Wilga [mailto:[hidden email]]
Sent: Wednesday, September 24, 2014 2:12 PM
To: Monster Menus Development
Subject: Re: I'd like your opinions on a deletion dilemma

 

There's a corollary to the original question:

When Page A and Page B contain the same node and THE NODE is permanently deleted (without using a bin), it disappears from both pages.

If bins are used, then deleting THE NODE causes two bins to be created, both of which contain the node. If either bin is emptied, the node remains in the other bin, and can potentially be restored.

1. Should only one bin be created, and the node left visible on the other page?

2. Or should emptying either bin delete the node in both places, for consistency with the no-bin case? I think this would also be more consistent with #2, below.

On 9/18/14 10:26 AM, Dan Wilga wrote:

There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set " Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685500.19fa7de7038497527f6a88cf1629251d&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

 

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=849053.214f550f57fa54a976b5f2d087b6d379&n=T&l=monster_menus&o=706352

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706354

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: I'd like your opinions on a deletion dilemma

Hilary Caws-Elwitt
In reply to this post by Dan Wilga-2

I second option #1; the checkbox would be a great addition to that.

 

·         #1 because from the user point of view, each node appearance is independent. Only when the last one is removed should the node actually disappear from view.

·         Checkbox because from the content creator point of view, maybe I’m deleting something outdated and I’ve forgotten it’s also showing on other pages.

 

--

Hilary Caws-Elwitt

IT Analyst - Five Colleges, Inc. - http://www.fivecolleges.edu

97 Spring St, Amherst MA 01002

[hidden email] - 413-542-4022

 

From: Jay Dansand [mailto:[hidden email]]
Sent: Wednesday, September 24, 2014 3:57 PM
To: Monster Menus Development
Subject: RE: I'd like your opinions on a deletion dilemma

 

So, if I understand it correctly, with the current behavior:

 

1)    Node “Foo” appears on pages “Bar” and “Baz”.

2)    (with bins enabled) If you delete the node from Bar, then it is also removed from Baz, and placed into recycling bins under both Bar and Baz.

3)    If you empty Bar’s recycling bin, then the node still exists in Baz’s recycling bin.

 

I think the intent of our votes for #2 in the previous question was that taking an action on page Bar shouldn’t have an implicit side-effect on page Baz.  At least, that was my argument.  In this case, the current behavior is almost perfect, but I’d vote in favor of option #1: deleting the node on Bar does not remove it from Baz. Perhaps there should be a checkbox on mm_ui_node_delete_confirm that asks “Should this node be removed from all other pages as well?” in which case the current behavior (separate, disconnected recycling bins) takes over.

 

As far as the current no-bin behavior goes, that’s actually a problem for us and we’re planning to write another mm_tweak to prompt for permanently deleting the node from all pages or just remove the reference from the current page.  Or, if you all would be onboard with changing that behavior upstream, it’d make it more consistent with the current (or proposed change #1) behavior when using bins… J


-- 
Jay Dansand '08
Senior Web Application Developer
Technology Services, Seeley G. Mudd Library
Lawrence University
Appleton, WI
920-832-6585
[hidden email]

From: Dan Wilga [[hidden email]]
Sent: Wednesday, September 24, 2014 2:12 PM
To: Monster Menus Development
Subject: Re: I'd like your opinions on a deletion dilemma

 

There's a corollary to the original question:

When Page A and Page B contain the same node and THE NODE is permanently deleted (without using a bin), it disappears from both pages.

If bins are used, then deleting THE NODE causes two bins to be created, both of which contain the node. If either bin is emptied, the node remains in the other bin, and can potentially be restored.

1. Should only one bin be created, and the node left visible on the other page?

2. Or should emptying either bin delete the node in both places, for consistency with the no-bin case? I think this would also be more consistent with #2, below.

On 9/18/14 10:26 AM, Dan Wilga wrote:

There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set " Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685500.19fa7de7038497527f6a88cf1629251d&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

 

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=849053.214f550f57fa54a976b5f2d087b6d379&n=T&l=monster_menus&o=706352

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=1034715.d8dc340b0014c740c37e95754e54e1f3&n=T&l=monster_menus&o=706354

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706357

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

Adam Franco
Administrator
In reply to this post by Dan Wilga-2
Jay hit it on the head:
"taking an action on page Bar shouldn’t have an implicit side-effect on page Baz."

Adding a checkbox to allow deleting a node (or all nodes on a page) from all other pages would be a reasonable way to allow side-effects on other pages, but that shouldn't be the default behavior.


Adam

--

Adam Franco
Senior Software Engineer - Web Applications
Library and Information Services
Middlebury College
Middlebury, VT 05753
[hidden email]
802.443.2244

On Wed, Sep 24, 2014 at 4:16 PM, Hilary Caws-Elwitt <[hidden email]> wrote:
I second option #1; the checkbox would be a great addition to that.


·         #1 because from the user point of view, each node appearance is independent. Only when the last one is removed should the node actually disappear from view.

·         Checkbox because from the content creator point of view, maybe I’m deleting something outdated and I’ve forgotten it’s also showing on other pages.

--
Hilary Caws-Elwitt
IT Analyst - Five Colleges, Inc. - http://www.fivecolleges.edu<http://www.fivecolleges.edu/>
97 Spring St, Amherst MA 01002
[hidden email]<mailto:[hidden email]> - <a href="tel:413-542-4022" value="+14135424022">413-542-4022

From: Jay Dansand [mailto:[hidden email]]
Sent: Wednesday, September 24, 2014 3:57 PM
To: Monster Menus Development
Subject: RE: I'd like your opinions on a deletion dilemma

So, if I understand it correctly, with the current behavior:


1)    Node “Foo” appears on pages “Bar” and “Baz”.

2)    (with bins enabled) If you delete the node from Bar, then it is also removed from Baz, and placed into recycling bins under both Bar and Baz.

3)    If you empty Bar’s recycling bin, then the node still exists in Baz’s recycling bin.

I think the intent of our votes for #2 in the previous question was that taking an action on page Bar shouldn’t have an implicit side-effect on page Baz.  At least, that was my argument.  In this case, the current behavior is almost perfect, but I’d vote in favor of option #1: deleting the node on Bar does not remove it from Baz. Perhaps there should be a checkbox on mm_ui_node_delete_confirm that asks “Should this node be removed from all other pages as well?” in which case the current behavior (separate, disconnected recycling bins) takes over.

As far as the current no-bin behavior goes, that’s actually a problem for us and we’re planning to write another mm_tweak to prompt for permanently deleting the node from all pages or just remove the reference from the current page.  Or, if you all would be onboard with changing that behavior upstream, it’d make it more consistent with the current (or proposed change #1) behavior when using bins… ☺

--
Jay Dansand '08
Senior Web Application Developer
Technology Services, Seeley G. Mudd Library
Lawrence University
Appleton, WI
<a href="tel:920-832-6585" value="+19208326585">920-832-6585
[hidden email]<mailto:[hidden email]>
From: Dan Wilga [mailto:[hidden email]]
Sent: Wednesday, September 24, 2014 2:12 PM
To: Monster Menus Development
Subject: Re: I'd like your opinions on a deletion dilemma

There's a corollary to the original question:

When Page A and Page B contain the same node and THE NODE is permanently deleted (without using a bin), it disappears from both pages.

If bins are used, then deleting THE NODE causes two bins to be created, both of which contain the node. If either bin is emptied, the node remains in the other bin, and can potentially be restored.

1. Should only one bin be created, and the node left visible on the other page?

2. Or should emptying either bin delete the node in both places, for consistency with the no-bin case? I think this would also be more consistent with #2, below.

On 9/18/14 10:26 AM, Dan Wilga wrote:
There's an issue that was raised quite some time ago:

  https://www.drupal.org/node/1890488

It details a difference, which may not seem entirely intuitive, in the way deletion occurs when recycle bins are being used vs. not used.

When Page A and Page B contain the same node and Page A is permanently deleted (without using a bin), the node remains on Page B.

If bins are used, then two bins are created: one contains Page A and the node, the other just the node. The node is no longer visible on Page B, even though that page is not in the bin. Both bins must be emptied for the node to be completely deleted.

To try this out for yourself, paste the attached PHP code into devel/php. Then, go to x/a/b and either delete it permanently or move it to the recycle bin. (See admin/mm/settings, in the General section. Set " Automatic recycle bin deletion interval" to either a value or "don't use recycle bins".)

The question is: Should this be made more consistent and, if so, in which direction? Choose one:

1. Change the no-bin case to immediately delete the node from Page B. This is probably not ideal, since it's more destructive than the current behavior. A warning message could include references to the other affected pages.

2. Change the way adding a page to the bin works, such that the node remains visible on Page B, and only the Page A reference is in the bin. Emptying the bin just removes the Page A reference, and leaves the node on Page B intact. A warning message, though likely confusing, could accompany this situation, either at the point where the page is placed into the bin or when emptying.

3. Leave things as they are now, and perhaps add more specific warnings.

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=685500.19fa7de7038497527f6a88cf1629251d&n=T&l=monster_menus&o=706171

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>


---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=849053.214f550f57fa54a976b5f2d087b6d379&n=T&l=monster_menus&o=706352

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=1034715.d8dc340b0014c740c37e95754e54e1f3&n=T&l=monster_menus&o=706354

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

---

You are currently subscribed to monster_menus as: [hidden email]<mailto:[hidden email]>.

To unsubscribe click here: http://lists.middlebury.edu/u?id=685438.780c6126d238396bdd2f98c1d84c15c7&n=T&l=monster_menus&o=706357

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]<mailto:[hidden email]>

---

You are currently subscribed to monster_menus as: [hidden email].

To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=706370

(It may be necessary to cut and paste the above URL if the line is broken)

or send a blank email to [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

grahamtk
Has this in any way been implemented yet?

are there any way of removing articles in bulk from one of the pages?
I have a lot of news items directly on a frontpage that also resides in
/news subpage.
I would like to use the frontpage for a one node full view, and needs to get
rid of the long list of news items that resides on both pages.

Øyvind



--
View this message in context: http://monster-menus.2910260.n2.nabble.com/I-d-like-your-opinions-on-a-deletion-dilemma-tp7572960p7573087.html
Sent from the Monster Menus mailing list archive at Nabble.com.

---
You are currently subscribed to monster_menus as: [hidden email].
To unsubscribe click here: http://lists.middlebury.edu/u?id=685503.6b071f880fe6a965a128164e6d09ea81&n=T&l=monster_menus&o=715166
or send a blank email to [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: I'd like your opinions on a deletion dilemma

grahamtk
This post has NOT been accepted by the mailing list yet.
In reply to this post by Adam Franco
Has this in any way been implemented yet?

are there any way of removing articles in bulk from one of the pages?
I have a lot of news items directly on a frontpage that also resides in /news subpage.
I would like to use the frontpage for a one node full view, and needs to get rid of the long list of news items that resides on both pages.

Øyvind
Loading...