Is this module being ported to Drupal 6?

Comments

jpetso’s picture

jpetso commented

Yes, but probably only after CCK for Drupal 6 is released. Also, before taking on the D6 port, FileField 5.x-2.3 must go out as a stable version.

nekobul’s picture

nekobul commented

Jakob,

There is already a version of CCK for D6. Are you going to start working on a port for it? I maybe able to help with the porting, but I will need help.

Regards,
Ivan

jpetso’s picture

jpetso commented

Yes, I saw that - although I didn't find a CCK field upgrade guide, is there none or did I just miss that one?

Anyways, I'll surely support any porting effort as good as I can - just want to avoid two different branches in active development, and that's probably the foremost reason why I personally don't want to do the D6 port yet. However, if someone needs filefield sooner than I do and helps by providing patches, I can do my part and make sure that all improvements from the 5.x-2.x branch are ported to the 6.x-1.x version as well.

yched’s picture

yched commented

@jpetso : There's http://drupal.org/node/191796. It's a little buried in the 'CCK doc' book, we might want to provide a clearer link on cck's project page at some point :-)

yched’s picture

yched commented

I should also add that, fielfield / imagefield being 'special' (in that they tie to non-db resources), feedback from those modules is precious to validate the api refactorings that have taken place in CCK for D6, and make sure they get all they need to function.

nekobul’s picture

nekobul commented

Yves,

I'm reviewing the filefiled module, but the changes in CCK are so many that porting it to D6 is not a trivial job. Also the documentation is not very useful either. I see you are one of the main developers of CCK and I think it will be easier for you to review it. And just like you said it will give you useful feedback regarding the current state of CCK. Can you find time to review it?

Regards,
Ivan

drewish’s picture

drewish commented

subscribing...

mscdex’s picture

mscdex commented

I noticed that Views D6 seems to be fairly mature by now (despite being beta as of this writing), as they've removed the warnings about missing upgrade paths and such from the project description. So I assume CCK should be pretty well caught up and stabilized now, since the two seem to have kept in sync with each other throughout Views' development. Has there been any developments with regards to the filefield for D6 since last month?

jpetso’s picture

jpetso commented

Not yet, but we're getting to this soon (like, sometime during May probably). quicksketch has a working port of imagefield in the imagefield issue queue, and porting filefield will mostly be transferring those changes to filefield where appropriate.

finex’s picture

finex commented

+1 for update the module to the 6.x version.

encho’s picture

encho commented

++ for update. subscribing

jpetso’s picture

jpetso commented

I don't want to be anal, but +1'ing the port does not get you *any* outcome. Neither positive nor negative. We'll port it when we've got time and motivation to do it, not when the score is +7, mmkay? Please refrain from doing that - I know it's meant in an encouraging way and I want to thank you for that intention, but in practice it just adds noise to this issue. Thanks for listening, your anal filefield co-maintainer.

liquidcms’s picture

liquidcms commented

i think the +1 thing is not just meant for friendly encouragement - but it also serves the purpose of subscribing to the issue so that you can get emailed updates.

maybe there is a cleaner way to "subscribe" cuz i agree a pile of subscribes and +1's clutters the issue info that gets posted - but i have never stumbled upon another way :(

jpetso’s picture

jpetso commented

Nope, there's no cleaner way to do that at the moment. I think the Project* dudes will come up with something better once drupal.org runs on Drupal 6 (and the new subscriptions module) but for now, there's no other way than the plain old "subscribe" comment. dopry can't stand that one, but it's the only way to get notified apart from subscribing to all issues of a module (which is not what most people want, naturally).

Moonshine’s picture

Moonshine commented

subscribe

smh67’s picture

smh67 commented

How about mime-detect? I don't see that one moving towards 6.x? Will a ported fileField be able to do without that being ported? Sorry for asking, but if you guys actually manage to port it in May, I'd be perfectly fine. If it has to wait for mime-detect after that i should probably look for some other solution :)

drewish’s picture

drewish commented

smh67, rather than asking about mime-detect over in this issue, the smart thing would have been to look in the mime-detect issue queue where you would have found #233005: Update for D6.

smh67’s picture

smh67 commented

My apologies. I did check, but obviously did not look closely enough (i.e. at more than the topmost item). Sorry.

jonfhancock’s picture

jonfhancock commented

Awesome. So, any new news on this one?

Oh, and... subscribe ;)

fellow’s picture

fellow commented

++ for update. subscribing

dopry’s picture

dopry commented
Status: Active » Closed (fixed)

Ok you subscribers... Either post patches or shut up and come back to the issue queue when you want an update... Noise for your convenience doesn't help get any work done... I'm sure update_status will be happy to tell you when a D6 version of this module is available and any questions about the time period for a completely porting will be summarily closed.