Title: Problem moving nested comments Last modified: August 30, 2016 --- # Problem moving nested comments * [kevinthom](https://wordpress.org/support/users/kevinthom/) * (@kevinthom) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/) * I found that moving a nested comment results in the original comment being left in place and the nested comments being flattened out and moved. It’s unfortunate that it doesn’t work because otherwise this plugin would be perfect! * [https://wordpress.org/plugins/tako-movable-comments/](https://wordpress.org/plugins/tako-movable-comments/) Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Author [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * (@renettarenula) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266240) * What do you mean exactly? When you move an original comment, all of the nested comments under that original comment will be move as well (including the original one that you have chosen). * What kind of behavior are you expecting? Are you expecting original comments to be move as well when you move a nested one. For example: * -Original comment #1 -Nested comment 1 to original comment #1 -Nested comment 2 to original comment #1 * So when I move **Nested comment 2 to original comment #1**, you are expecting** Original comment #1** and **Nested comment 1 to original comment #1** to be move as well? * In this case, I don’t think so that is a desired behavior because nested comments can be off-topic and not necessarily related to the original comment. * Thread Starter [kevinthom](https://wordpress.org/support/users/kevinthom/) * (@kevinthom) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266241) * Thanks for replying. I am trying to move the entire thread of comments to a new page/post and preserve its nesting. When I select “Edit” beside a comment that has replies, I get the “Edit comment” screen for that comment. When I select the destination, all of the _replies_ move, but they are no longer nested. The original comment that I tried to move stays in its original location. * I’ve updated to the latest version of the plugin (1.0.5) and the behavior is the same. * Thread Starter [kevinthom](https://wordpress.org/support/users/kevinthom/) * (@kevinthom) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266242) * Here is an example of what is happening: * **PAGE 1** |-Comment 1 |–Nested Comment 1 |—Nested Comment 1a |–Nested Comment 2 |—Nested Comment 2a * I click edit beside Comment 1 and try to move it to Page 2. The result is like this: * **PAGE 1** |-Comment 1 * **PAGE 2** |-Comment 1a |-Comment 2 |-Comment 2a * I would expect this: * **PAGE 1** No comments * **PAGE 2** |-Comment 1 |–Nested Comment 1 |—Nested Comment 1a |–Nested Comment 2 |—Nested Comment 2a * Thread Starter [kevinthom](https://wordpress.org/support/users/kevinthom/) * (@kevinthom) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266244) * WordPress finally showed me the 1.0.6 version as being available so I installed it. It is better but still not exactly as I would expect. * 1.0.6 moves the original, but still flattens out the thread so all nested comments are on the same level. The expected behaviour would be that the moved comments would retain their nesting. * Plugin Author [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * (@renettarenula) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266251) * Thanks for explaining. I am not able to reproduce this error actually but I will take a look into it. * Plugin Author [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * (@renettarenula) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266252) * Oh wow, I managed reproduce this after playing around with it. I was not sure what I did. I was just adding nested comments like the format you have mention. However, I manage to get all the original comment and the nested comments moving as normal. All I did was, I move the original comment once again to the desired post. Once that is done, I checked again and the original comment + nested comments are moved properly without the nested comments being flatten out. * Why don’t you try and move the original comment again and see if it works because moving the original comment works for me after trying it one more time. I am not sure whats causing the nested comments to be flatten out but I will take a look at it. Thanks! * Plugin Author [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * (@renettarenula) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266253) * After tinkering around again, I notice that if I add nested comments (on the dashboard; not through the site) **AFTER** moving comments with the **bulk move comments feature**, the newly added nested comments will be flatten out and will be separated with the original comment. However, moving the original comment to the desired post will remedy this problem and nest the comments out all again. * Is this how you manage to find this bug? U added nested comments through the dashboard? There must be a bug with the templating of bulk comments if this is how you discovered it. * Just try and move the original comment once again and you should get a nicely formatted comment with its children comments. I hope it helps. * Thread Starter [kevinthom](https://wordpress.org/support/users/kevinthom/) * (@kevinthom) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266257) * I did more investigation and figured out what’s happening. If you move an original comment, it preserves the nesting perfectly. However, if you move a sub-comment, the nesting breaks for all the comments below that sub-comment. For example: * **PAGE 1** |-Comment 1 |–Comment 1a |—Comment 1ai |—Comment 1aii * Moving comment 1a to PAGE 2 results in a flat structure like this: * **PAGE 2** |-Comment 1a |-Comment 1ai |-Comment 1aii * instead of what I would expect: * **PAGE 2** |-Comment 1a |–Comment 1ai |–Comment 1aii * It’s not the end of the world, but it just wasn’t what I expected. I thought it would preserve the hierarchy. Nonetheless, I’m perfectly happy to use your fantastic plugin as it is now and give you massive thanks for all the work you’ve saved me already. * Plugin Author [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * (@renettarenula) * [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266261) * Oh wow! Thanks for the heads up, kevinthom. I will check this out and see what can be done to remedy that. That’s what I am expecting as well. It is suppose to behave that way and last time I checked, it did. But with the new WP update and all, it may have messed with this behavior. Thanks for explaining it in detail to me. At least I know what is the problem now. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Problem moving nested comments’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/tako-movable-comments.svg) * [Tako Movable Comments](https://wordpress.org/plugins/tako-movable-comments/) * [Frequently Asked Questions](https://wordpress.org/plugins/tako-movable-comments/#faq) * [Support Threads](https://wordpress.org/support/plugin/tako-movable-comments/) * [Active Topics](https://wordpress.org/support/plugin/tako-movable-comments/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/tako-movable-comments/unresolved/) * [Reviews](https://wordpress.org/support/plugin/tako-movable-comments/reviews/) * 9 replies * 2 participants * Last reply from: [RenettaRenula](https://wordpress.org/support/users/renettarenula/) * Last activity: [10 years, 11 months ago](https://wordpress.org/support/topic/problem-moving-nested-comments/#post-6266261) * Status: not resolved