Closed (won't fix)
Project:
Asset
Version:
6.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Dec 2008 at 09:19 UTC
Updated:
14 Oct 2010 at 12:34 UTC
Jump to comment: Most recent file
Comments
Comment #1
niallhatton commentedsame problem
Comment #2
philb_au commentedYep,
Exactly the same problem here. Hoping that a superhero may drop by sometime in the near future...
Comment #3
DigOurGame commentedSame here
Comment #4
ckani commentedSame issue, 2 days and still looking for a fix.
Please help.
Comment #5
kari.nies commentedSame here. Has anyone gotten the Asset Wizard working in Drupal 6.10?
Comment #6
Bryan76 commentedApparently the funciton asset_wizard_menu is being called without an argument somewhere. The argument it needs is $may_cache. Without looking through the code, in my mind the safer but less efficient answer is FALSE. So I changed it thusly:
Comment #7
spade commentedThanks Brian,
that took care of it for me.
Keep up the good work!
Kind regards,
Frank
Comment #8
nruest commentedThanks Bryan!
It worked for me as well.
Comment #9
willazilla commentedPerfect! Thank you.
Comment #10
seanr$may_cache should just be removed entirely, that's a legacy Drupal 5 hook_menu argument that is no longer relevant in D6. Patch attached.
Comment #11
seanrArgh, this is going to need a LOT more work. This doesn't look like it was even ported to D6 at all, just tagged as such. I don't have time to fix it right now.
Comment #12
ClearXS commentedContinue the good work! (also because D5 core will become non-supported in some weeks or few months & users really should step over to D6)
Please ask for assistance (and integration with other ideas/projects) in the media group, or something?
http://groups.drupal.org/media
I will unpack this D6 version module in my modules dir, so I can track new releases automatically with another module that keeps track of non-activated modules too.
Hope it doesn't do strange database changes for a non-activated module, as I like to remember your strong advice that in this stage the module is too fresh and unstable to use.
Comment #13
wmostrey commentedSean is correct: The 6.x version was a one-time commit by cirotix who never maintained it. I created documentation on a migration guide to port asset content into regular HTML. This should be a good starting point for further migration to FileField, IMCE (and possibly FileField Sources).
Asset module for Drupal 6 and above: migration guide