Drupal 6 port of the asset module

I would also appreciate any information about asset module and drupal 6, as we're starting a new web site and we won't do that with drupal 5...

Subscribing

Subscribing

sub

Asset 5.x-1 is nearing its first release candidate. Once asset 5.x-1.0 is released, I will start porting it to Drupal 6.

Great stuff, good to hear progress is being made, clearly this could be the best thing for Drupal since CCK and Views (I can see Asset being used in many of my future projects).

subscribe..

subscribing

sorry, don't want to be pushy here (i know, it very much sounds pushy and probably is ;), but:

When are we going to see Asset for D6?? ... This issue is quite abandoned for a while now...
Drupal 6 is in the mid of its release cycle and many major modules are *at last* running on D6, making it the only reasonable choice for projects that get into development at this moment. If asset module shall be widely used, it is critical that Asset runs on D6 now.

Sooo ... does anyone have a *rough* idea about when a decent running D6 version of Asset module could be available, not for production, just for development? We'll need it primarily for integration into a project currently under development until the end of the year (but integrated into project development in any case *way before* end of the year).
We used Asset on a D5 prototype, and i'd hate to replace it now, cause i think it's great and it's got real potential.

Would be glad to hear something a bit more specific to get a rough idea about Asset-for-D6 timeline....

thanks!!

daniel

Damien Cirotteau is currently working on a Drupal 6 port, you can follow the progress on the g.d.o post on The future of the asset module. I agree that if even panels is in it's first alpha, it's time for asset to move on as well. Our priority was to get a stable 1.0 out for Drupal 5 and now that we managed that, we're ready for Drupal 6.

thanks, Wim, that's great news!

Sounds as if Damien is working on a feature-constant Port, which is very fine for me and should make a D6 Asset.module coming reality a lot faster - cool!

(So, I'll continue development without activating asset.module and then integrate it as soon as a test version is getting out, which should work for most D6 projects starting at the moment, since Damien sounds as if he would have early verison of an asset D6 port ready within a few weeks...).

I confirm both statements : this is a constant feature port and it will be release very soon now. You can expect a test version for the next week.

subscribing

subscribing and waiting...

Hi Wim and/or Damien, is there any update on the status of the D6 port of Asset?

It's comming, thank you for your patience.
We are in debug phase.

great news!
would just beperfect to keep us all informed about your current time plan for the D6-Asset Dev-Version (even if the first commit is taking more time than planned or the work gets postponed - being informed empowers us to adapt to those changes of timeframe).

subscribe, we're waiting D6 version, thanks.

subscribing

Hey Damien and Wim!

I set this back to critical. Partly since this is becoming a project-critical issue for me, but much more so because Drupal 6 ist out now for nine months and there isn't even a dev-version of the asset.module out (and D7 is just around the corner! Meaning D5 won't be developed/supported any longer). So being D6 compatible IS CRITICAL NOW for asset.module's future, that is, from an objective perspective: Will this module be operational in the future? That's the key question of this isseu we now all have to face, and i hope you can at last provide some *rough* hint about that.

Liek always, information is key here. What i *really* like ask you is just an honest status and estimate about the D6-port work of asset.module. So that we all know where we are. So, could you give us a rough status and/or estimate how the D6-port of Asset is doing? (When) Could we expect some test version, so we can provide you with feedback? Or is it out of questions for this year? A simple answer to that question would really help.

I know it's hard to be a module maintainer and being pushed by the community to get new releases out. But much more important than a release is becoming *information*. I'd glad to help out myself, if i would have more insight into the modules guts.... and if i wouldn't be running out of time with my current project and have to stay focused. If both your focuses are way away from asset.module, then this is okay, but please let us know.

For me, personally, my current project's deadline (end of year) is now on the horizon, and i really *need* a solution within the next 3 weeks - is there any chance that a D6 asset.module will be available in a working form? The module would be just the right one, and i'd really like to put my stakes in asset.module for this and coming drupal projects. But i have to confine to reality - regarding asset.module *you* would be the people to give us some hint on the reality of this module, so we can all judge where to put our stakes. As i can imagine, this choice is being made by many others these days, too.

so, i'd glad to hear a little rough estimate from your side: (when) could there be a D6 asset.module this year - or not?

thanks so much for your work,

daniel

Renamed thread to be more appropriate. Plus note if you need the module right away why not consider suppliying patches rather than ranting about your critical needs. don't forget that 95% of development to modules (and indeed Drupal core itself) is done by people in their own time.

subscribing

Marc, i hoped to have made it clear not to try ranting about the availability of the module but to (repeatedly, hence to urgent tone) *ask* for the availability for *information*. All I'm asking for is that the people that took on the D6 port responsibility to give a *little* reliable hint about what to expect when. Nothing more. Knowing how workloads develop and things sometimes turn out, and being glad that so many high-profile developers in the drupal community commit so much time for the needs of this community, i'm not demanding at all. Just asking for some simple information, that can be given in 2 a minutes posting.
Critical in my context - and i imagine in many others, too - means that the time window is closing on the decision whether or not to rely on asset.module or look for/develop alternative solutions. Starting to port a large module that you don't know very well on your own (maybe in parallel to existing efforts of Wim or Damien!!) while being tied to a project's other constraints is illusive for most. Helping in existing efforts would be more realistic - and again only possible if some information would be made available.
i hope that through all the justification above the important message get's through:

We all rely on the information of those who took responsibility even more than on the results.

Some update :
the module is ported and functionnal.

It will go on prod on a website for one of our clients in december and it is already activated on the beta.
This is for the good news.

As for the bad ones, I have asked the module owner (Roger Lopez) to grant me the CVS rights for my drupal CVS account. I am waiting on it. I will wait a couple of days more and if I have no reply I will see with Wim if he can commit on my behalf. Still I would like to be able to do it by myself as it would be much more easy to commit further improvement.

The port is nearly and 1<->1 from Drupal 5 with some improvement on the asset cck module (imagecache integration mainly).

I do understand the impatient people here (if I were you I would feel the same). But we are in the final phase of a project and out time as to be dedicated to this project before public releasing on the module.

wow, that's great new, Damien!

Thanks a lot for the information, which is helping me (and probably many others) making a decision.
And thanks even more that you took responsibility here, and for your effort and hard work for this module and this community!!
Hope you get your CVS access, and looking forward to help test and/or further improve the module once it's commited :))

Just to make it clear : We (Rue89) have done that port but I am not the guy who actually had put is hand on that.
I am the technical lead of Rue89 and I'm taking care of publishing it on behalf of our dev team.

okay, even better, then you share the kudos with your dev-team - thanks all you guys!

For your pleasure :
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/asset/?path...

This is too be considered as a pre-alpha software of course. Use it at your own risk.

This version is now added to the asset project page: http://drupal.org/node/337025.

Thanks so much Rue89 and Damien!

Hi!

Just wondering if anybody had tried the dev version... I'd like to use it on a very simple site, but it would be a productions site.

Cirotix said:

The port is nearly and 1<->1 from Drupal 5 with some improvement on the asset cck module

but I am not sure if I could assume it works without problems.

Thanks a lot

Hi,

There hasn't been a release since November. There is a discouraging message on the project page that this module may break your system.

Whats the current status...of asset end January... can someone tell us? We are not demanding the port, rather want to get *information* about the port :-)

Thanks,

Sidharth

subscribe

I tried it just now, I only get a button called "More assets" in my post where I have added an Asset CCK field. No way to upload that I can find.

Add me to the list of those wanting some info. As a module maintainer myself, I understand that things don't always get done when we like. While I'm disappointed to see no progress on Asset, I recognize that I have done nothing to help it along. But the lack of information makes it difficult to make a decision on whether to continue to wait or move on to something else. Or maybe the lack of information in all these months should be taken as a sign to move on because the project is abandoned?

Michelle

I have the same concern as voiced by Michelle. We have used Asset module extensively on our D5 site and are in the process of upgrading to D6. We have successfully tested upgrading CCK, Imagecache and Views. But since port of Asset module is not ready for production this is holding back our overall upgrade to D6. The lack of infromation is preventing us from making a decision whether to wait a little longer for a 'stable' port or to just move to using some other module to handle images and videos.

Sorry for the lack of feedback.

I am still there, the module is not abandoned and actually used on a couple of production.
It is not perfect yet (and actually should be re-writted) but I will publish a new version of the D6 version soon now.
Time is always missing...

@cirotix: Thanks for the feedback. I can sympathise on the lack of time and certainly won't berate a maintainer for taking too long to get a module finished. But taking a minute to let us know the current status helps a lot so that we can make decisions with complete information. Glad to hear that a new version is coming. Hopefully without the big scary warning that this will break your site if it's being used elsewhere in production. :) As a programmer myself, I can deal with a less than perfect module but when the project page says "don't use this" I take it seriously. LOL

Michelle

Actually it was published before without the scary message, but I have add it it later because of a user complaining that it was breaking some stuffs. Iin fact it won't really break anything, but it is not for production as it is now (well not really because I do use it on production). I thought that the -dev flag + bg red cross was enough, but apparently not for some developpers.

The trouble is that lots of modules stay in dev for a very long time and some of them are crap and some of them are just fine and should have a proper release. If it's a module you really need sometimes you just take a chance and try it. If you are a programmer, often you can fix things yourself if the module is mostly ok but glitchy. That's why keeping the project page updated is so valuable because you can keep your users aware of how you view the module's status.

In this case, the message would be better to say something like "I use this in production on a couple of sites and it works ok for me but I don't recommend it for general production use and am not offering any support on it. Use it at your own risk." To me that says that I, as a programmer and generally competent Drupal user, could use it knowing I'm on my own if I run into trouble. Whereas someone new to Drupal would see that and (if they're smart) move on to other choices.

It's all about communication. :)

Michelle

Yes I know where the problem is with -dev releases and I do agree on the communication point. I have actually add this message because I was a little bit pissed of by the harsh message against the dev release of asset for D6.

Your message looks very sensible, I will use it with the new release of asset for D6.

Thank you all for your patience.

Thank you for the module. This is the best solution I've found for end users to add images and I was not looking forward to having to find another solution when I upgrade to D6.

Michelle

subscribing.

subscribe.

subscribe

Count me in as well. I really wonder why development isn't so active (last commit in November). It was nice to hear that the module is not abandoned, but the feedback we are getting from the cvs isn't very encouraging. I am a developer myself so the last thing I want is to be annoying, but we have to know if we can rely on this project. This is the perfect solution for image, video and audio handling within a wysiwyg editor. If there is a major refactoring process in the works then It would be nice if we knew. We might even want to help by testing and patching!

Maybe they are working on the new Media module:
http://drupal.org/project/media

Subscribing.

I already installed this Asset module for Drupal 6, I fixed some few problems and all works right, but I noticed other problem, when I change the status of article (publish/unpublish/...) all images are disapear from the fields.
What are you thinl about it, what is the problem?

@blaze: If you fixed stuff, please supply patches so the maintainers can get the fixes into the module. And new questions need a new issue.

Michelle

subscribing

this is a very cool and can be very important module..

subscribing!

Subscribe!

Is this module still being maintained?

Subscribing.

Subscribing

Subscribing.

Subscribing

Just subscribing to this. I'm working on porting a large Drupal 5 site with Asset to Drupal 6, including a conversion from asset to filefield / imagefield. The code has a lot hardcoded (field names and tables etc.), but I can probably post the snippets and some instructions up - then you'd need to tweak it for your own site.

Subscribe.
Still in trouble with asset in Drupal 6.
Did anyone make the "Insert Asset" appear?

I'm getting an error for "Asset Embedded Media" and "Asset Bonus Pack," as follows: "This version is incompatible with the 6.15 version of Drupal core."

@#63 using drush or CVS?
that error recalls me when the .info file misses core = 6.x, that happens when you're not using the download bundles packaged with the download script which adds this line

Here's the asset.info detail from my download:
; $Id$
name = Asset
description = Digital Asset management.
package = Asset
core = 6.x
version = "$Name$"

; Information added by drupal.org packaging script on 2008-11-21
version = "6.x-1.x-dev"
core = "6.x"
project = "asset"
datestamp = "1227268893"

really?!?!

don't know how that happened

try deleting the line version = "$Name$" (that one might be troublesome)

another weirdness is the first line ; $Id$ which I can ensure won't introduce any trouble, but it didn't was modified to reflect the commit time/date/author, which should be there
(nevertheless, that line is not bringing any trouble)

The 6.x version was a one-time commit by cirotix who never maintained it.

Sorry to reopen that.
Does this module mean dead end for drupal 5 sites with lots of nodes with asset images or is there any alternative to exit (eg. updating to filefield or other solution)?
A link to at least one issue that sounds hopeful would be a good start - and a good end of this issue ;-)
Thanks

Maybe this is a starting point:
http://drupal.org/node/941430 (Titel: "Asset module for Drupal 6 and above: migration guide")
;-))))