Project:Killfile
Version:6.x-1.x-dev
Component:Configuration
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

How do I view killed files?

My Killfile config settings are:
Log message on deletion: Optional
Purge killfiled content after: Never
Automatically filter out killfiled content from all views: No (unchecked) --- I have tried this both ways.

I currently have "access killfiled content" set to my role.

Instructions in the README.txt file says, "... administrators can access and restore killfiled content when
necessary."

The INSTALL.txt instructions fall short of explaining where to view the killed files.

Am I missing something? Is there a path you can supply to the list of killed files? Do I need create a View with a relationship to the Killfile table?

Thanks for this module. I have some clients that have accidentally deleted nodes when trying to delete a file. It's not an uncommon problem.

Comments

#1

Hello,

The documentation is indeed lacking, but I found how to make it work with views. Partly.

In the killfile config settings:
Automatically filter out killfiled content from all views: No (unchecked)

Your user role should have access to killfiled content

Install Views module (if you have not already done that)

Create a new view for nodes.
Name: killfile

Basic Setting
Style: Unformatted
Row Style: Node
Access: access killfiled content

Relationships
Killfile: Node

Page Settings
Path: killfile

This view shows you all nodes that have been killfiled, or more technical: all nodes that have a corresponding nid in the killfile_nodes table.

I haven't found a "clean" way to restore killfiled content.
But when you killfile a node, it creates a new revision of the node.
What I do is, I revert to the version before the killfile, which restores the publishing state and removes the log message.
Then I manually delete the corresponding record from the killfile_nodes table, using phpMyAdmin.

And now I'm climbing on my soapbox:

In my opinion, what this module needs to become a true "Recycle Bin" module, is:

  1. View of killfiled nodes
    This means a dependency on the Views module, which I find acceptable.
    This means that you wouldn't have to configure your own view.
  2. Easy unkilling (restore) of single nodes
    I suggest automating what I do manually:
    1. Restoring to the version before the kill (or deleting the kill revision?)
    2. Deleting the corresponding record in killfile_nodes
  3. Easy restore of multiple nodes.
    When it's implemented for one node, it's just a simple matter of displaying a table of killfiled nodes, with a checkbox in the first column, similar to mass approval of comments.
  4. Optional: killfiling node revisions.
    I haven't thought this one trough yet, but it seems that the killfile_nodes table is ready for it: it has a nid and a vid column.

Getting off the soapbox.
This module has real kick-ass potential and it's already halfway there.
I reeeeeally hope that the developer appreciates this input.

#2

@amedee: I had thought of doing the same thing with views but thought that there had to be some sanctioned method from the maintainer - but apparently it just sort of drops off from there. I am second your suggestions for the roadmap --- I love the idea for this module. I feel so bad for my clients when all they wanted to do is delete a file from the node and end up deleting the node.

#3

This promising module is still in need of proper help and instructions, and a default view should be provided. Without this issue report and comments offered by others, I would not have been able to use it all.

#4

I support these "soapbox" suggestions.

#5

Status:active» fixed

Views module is the way to view such nodes.

In comment #1, opinions 1-3 are implemented in the D7 version.
D6 version only handles opinion 1.

#6

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.