Closed (fixed)
Project:
Storage API
Version:
6.x-1.2
Component:
Miscellaneous
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jan 2012 at 05:30 UTC
Updated:
9 Oct 2012 at 14:51 UTC
Not supported!error
Storage API 6.x-1.2
Project not supported: This project is no longer supported, and is no longer available for download. Disabling everything included by this project is strongly recommended!
Includes: Database, FTP, Filesystem, Filesystem / Drupal, Storage API
See screenshot....
| Comment | File | Size | Author |
|---|---|---|---|
| StorageAPI.png | 23.43 KB | joaomachado |
Comments
Comment #1
jbrown commentedIt hasn't really been supported in a year. I don't want any more D6 sites to start using it as the architecture of the module is very poor compared to the D7 version.
Comment #2
jon pollard commentedWill storage API and Blue Droplet Video continue to function on existing sites?
Comment #3
jbrown commentedYes - I may even commit patches. I just don't want them listed in the project pages for download as they shouldn't be used for new projects.
Comment #4
jon pollard commentedThanks for your response. I appreciate that you want to wind these projects up for version 6, but is there another way of doing it? Currently these two modules have this in the update report:
They are also listed as being flagged up as security updates in red.
Comment #5
jbrown commentedOkay - I re-enabled the D6 versions and put a big fat warning about them at the bottom of the project page.
Comment #6
jon pollard commentedThanks!!!
Very much appreciated.
:o)
Comment #8
milovan commentedI was working these days with D6 version when I just realized today that it is removed from the module page again.
Is it now officially dropped or am I missing something? I couldnt find any kind of D6 storage_api notification regarding this anywhere.
Thanks!
Comment #9
jbrown commentedThe D6 branch hasn't been maintained for 18 months now.
Comment #10
jon pollard commentedI think the problem is that there is no way to mark a project as obsolete without having it trigger security alerts. I have a couple of sites set up using this system to store videos. All new video uploads are using a new system - but I don't really want to have to go through and replace all the existing videos...
Maybe I just need to learn to live with having an 'unsecure' module in operation - regardless of the fact that nobody has permission to use it.
Comment #11
milovan commentedI assumed this was the case. Thanks for confirmation and keep up great work on version for D7!