Links cannot be deleted from edit page
Starminder - September 16, 2009 - 19:18
| Project: | Web Links |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Scenario: User submits a questionable weblink. I edit the weblink and in doing so determine it is junk. I go to the bottom of the page and hit the delete button. The weblink is saved and does not get deleted.
I know this isn't the optimal process for deleting a link, but since there is a delete button on the page, it should work.
Thanks!
#1
See #252761: Node does not delete if form has redirect
#2
committed
#3
This may help or be the cause:
User submitted a boatload of Unclassified links
I then enabled forcing a category to be required
As I am going through the unlassified links, I am editing the link - looking, reading, and in some case I want to delete.
If I hit the delete button, I get the error that a category is required.
I select one and hit delete again
The edit page closes, the link is saved and remains in the unclassified category.
Suggestions? :) I'm starting to think maybe I should just go to content and delete all of his links ...
(Used Sep 17 Dev version for test)
Thank you!!
#4
The "category required" check is from the Taxonomy module and there's not much we can do about that. It's actually a minor core bug that I doubt has ever been reported.
I will see if I can set up a test case just like you describe.
BTW, you might find the CMF module useful for handling his content.
#5
Thanks for the tip - CMF looks great! One thing I noticed though as that the "Unclassified" category doesn't show up as a category to refine from - bummer.
Also, I just noticed that despite the updating weblinks to sep 17 Dev, the update page is reporting that I have Sep 13 Dev installed. (?)
#6
Try downloading it again.
#7
I still cannot reproduce this with the latest -dev.
#8
Marking as fixed again. If you get the latest version and it's still a problem, re-open the issue.
#9
Included in 6.x-2.2.