File manager is a tool (for Drupal 7) to administer managed and unmanaged files. Directories can be browsed and files examined. Differences between the database and the filesystem will be pointed out. Operations such as copying, moving, deleting, (batch) renaming and modifying files and directories are possible (not yet).
Sandbox (and more documentation (though incomplete yet)):
http://drupal.org/sandbox/jox/1215500
There is a (quite recent) similar module called File maintenance.
http://drupal.org/project/file_maintenance
So far that is Drupal 6 only though. And there is demand for Drupal 7: #1194214: Drupal 7 port of File Maintenance.
Other differences in File manager:
- Display information about file usage (in nodes etc.).
- Display information about disk space usage.
- Display files that are in the filesystem but not in the database.
- Show thumbnails of images and icons for other file types.
- Support and distinguish available uri schemes.
- The UI aims to provide optimum usability and overview (using Ajax and jQuery).
Screenshots are attached.
Comment | File | Size | Author |
---|---|---|---|
file_manager_configuration.png | 34.94 KB | jox | |
file_manager_browser_options.png | 93.4 KB | jox | |
file_manager_browser.png | 134.04 KB | jox |
Comments
Comment #1
ccardea CreditAttribution: ccardea commentedI conducted an initial review of this project.
Licensing: Did not find any non-GPL code.
Module duplication: I think this is going to be an issue for this project. The Media module is currently a big push to be a unified solution for file management. Could you take a look at this and see if there's a way you can work with Media module?
Overall the code looks good. The waiting time for a full project review can be 4 -6 weeks. You can help to reduce the waiting time by contributing to the code review process. Please visit http://groups.drupal.org/code-review for details on how to participate.
Comment #2
ccardea CreditAttribution: ccardea commentedComment #3
jox CreditAttribution: jox commentedThank you for your initial review.
Yes, Media also manages files. But it does that at a different level. And has another target audience.
I believe File manager does not replace or duplicate the Media module. Rather it's an addition to it. And also an addition to other modules that manipulate managed or unmanaged files (including non-media files) in any way.
Here is a comparison of both projects (from what I can tell):
Their both at different perspectives.
Do you still think it's a module duplication issue?
Comment #4
jox CreditAttribution: jox commentedComment #5
ccardea CreditAttribution: ccardea commentedI appreciate that the focus of your project is quite a bit different from Media module. Actually what I asked was if your project could work with Media module, as opposed to being an alternative. Your screenshots look really good, and I like what you've done, but I think you could still have a problem with duplication issues, because there are a bunch of file managers already. See http://groups.drupal.org/node/20291. The fact that most of them don't have a D7 version yet doesn't necessarily solve the duplication issue for you.
I think the application should go forward, but there's no guarantee this won't be raised again.
Comment #6
ccardea CreditAttribution: ccardea commentedI was thinking about this a little, and I think this would be a better project if it could work with Media module. You would automatically have a much larger potential user base, and that would solve the duplication issue for you. I'm not saying that your project won't be approved unless you do this, but I definitely encourage you to look into it.
Comment #7
jox CreditAttribution: jox commentedThanks again for your opinion. What you say sounds quite reasonable.
However, I was thinking about this too and I find there is also a couple of good reasons to have this as a standalone module.
These are just my thoughts. I don't insist in having it as an own project at all. I'm just not entirely convinced that going with Media would be the best approach (or classification). It would be a good strategy considering the application guidelines and current state of existing modules. But then again, isn't it kind of counterproductive to one of the main goals: having a well organized repertoire of modules?
Regarding the duplication issue I'm a little bit clueless anyway. I totally understand and acknowlege the principle. But even though File manager has overlaps with other modules it is still is a unique tool in my eyes. Where is the boundary for a duplication? And if there is duplication issues, how to solve them? I guess that can be complicated and time-consuming.
At the end I'm open for everything. My concern is to share my work and give something back to the project and the community.
Should we perhaps ask the Media maintainers for their opinion?
Comment #8
ccardea CreditAttribution: ccardea commentedI'm not suggesting that your project merge with Media module and lose its identity. The module duplication issue is not clear cut, its a judgment call. In this case it needs some careful consideration. This is a quote from the Media module FAQ
All I'm suggesting is that your project might have more value as part of a unified effort. It doesn't appear to be a problem of duplication with Media module, but there is the perception that there's a lot of file manager type code out there that needs to be considered.
Comment #9
jox CreditAttribution: jox commentedWaving the priority flag.
Comment #10
13rac1 CreditAttribution: 13rac1 commentedI agree with ccardea. Please focus your efforts. If the module is similar to http://drupal.org/project/file_maintenance then speak with the maintainer malc0mn and request to become the D7 version maintainer.
Comment #11
jox CreditAttribution: jox commented@eosrei: I tried that already 11 weeks ago: #1194214: Drupal 7 port of File Maintenance (#9).
Comment #12
13rac1 CreditAttribution: 13rac1 commentedHmm.. That is frustrating. I've updated the issue. I cannot locate additional contact information for malc0mn.
Comment #13
malc0mn CreditAttribution: malc0mn commentedIt is a bit of crossposting, but I'll reply here as well.
I'm happy to make jox D7 branch maintainer. Just added him to the file_maintenance project.
Apologies for the delay.
mlc.
Comment #14
jox CreditAttribution: jox commented@eosrei: Thanks for pushing the issue forward.
@malc0mn: Thanks for opening for collaboration.
I'll take care of further steps as soon as I find some time.
Comment #15
klausiGreat, so we can close this. Create a new issue if you want to promote other projects.
Comment #16
jox CreditAttribution: jox commentedDoes that mean this will not possibly lead to an approval?
Comment #17
NancyDruIMHO, "Display files that are in the filesystem but not in the database." is a major benefit. It looks like the file_maintenance module does not do that.
Comment #18
13rac1 CreditAttribution: 13rac1 commented@NancyDru This project can't be promoted, because the best option was to merge it with File Maintenance. Jox was added as a maintainer of File Maintenance, so hopefully soon we'll see a D7 version of File Maintenance using Jox's code.
@jox I had the same difficultly when it was requested that my project app be merged with another project app. After a long wait, we were both given Project Promote. In your case you've been added as a maintainer of an existing project, so there isn't justification to confer Project Promote. You'll have better luck getting Project Promote with a different module.
Comment #19
jox CreditAttribution: jox commented@NancyDru: Thanks for your support.
@eosrei: Thank you for you comment. I was guessing something like this. But even though this project is just "merging" with another and I am only added as maintainer, this project is a full project written seperately and from scratch for Drupal 7 complying with all the requirements. There is no real "merging" technically, only the label is reused.
So what's missing to qualify me for promoting full projects (isn't that what it's all about here in Project Applications)? There is no justification? What does that mean?
My point is not to desperately get promoted. I'm just a bit tired of all all this bureaucracy. I understand it and I respect it, but it's not really increasing motivation. And since this is going for months now here, it's also slowing down development and holding back people from useful stuff.
What I hear is: "What you got there is good enough, we'll take it. But please next time prove it again and bring some more patience. Unfortunately there is no button for your case."
Sorry for the bad mood. There might be reasons I'm not aware of. And of course this is not the end of the world, but it's just a bit annoying.
Please nobody take it personally (like I do (I think)).
Comment #20
13rac1 CreditAttribution: 13rac1 commentedJox, I know exactly how you feel. My code from Block Direct View completely replaced the original code in Internal Nodes(http://drupal.org/project/internal_nodes), but only mjpa was originally given Project Promote. I was annoyed about it and demotivated. Weeks later, mjpa was talking on IRC to tim.plunket and he changed my application to Fixed (http://drupal.org/node/1146410)
A lot of the "bureaucracy" is caused by the size of the project application queue. There is simply too much to review and it is all volunteer work. IMHO, also, many Applications should never have been submitted in the first place (not yours! ;) ). There are current discussions about changing the process: http://groups.drupal.org/node/180444 I'm sure you have ideas to add at this point...
I was told "If you need to promote another project in the future, please open a new application and reference these so we can do it faster next time." I can change this issue status back, but I don't know how much it will help considering it really should have been merged with the other module in the first place. So, the next best thing: contact me when you post a new application, and I'll review it ASAP.
Comment #21
NancyDru@Jox: I understand the feeling. I already have more than 20 modules, but I too would be required to jump through these hoops. Before I write any module, I search to see if there's anything similar enough to provide patches. Unfortunately, not all project pages take searching into account and occasionally I miss something that would have worked. Then I get the "similar module" messages from someone. It can be quite frustrating.
As eosrei suggests, maybe talking to that module maintainer will get him to back you for a new project, or even be willing to merge into yours. Can't hurt to try.
Comment #22
malc0mn CreditAttribution: malc0mn commented@jox: although subscribed to this thread, didn't receive any mails. Prolly because it's closed.
In my humble opinion: rename it to file_maintenance, add it to the repository @ file_maintenance and do a release? We can then go for a backport to D6?
Cheers,
mlc.
Comment #22.0
malc0mn CreditAttribution: malc0mn commentedAdded note that it's for D7.