Computed Field Drupal 6 port

Hi,

I would like to second the request for a Drupal 6 release.
I am starting a new site, and could definitely use this module with the new CCK for v6

Thanks
Sid

+1

I would be prepared to help

at least with testing if not more

subscribe

subscribe

subscribing

yup. count me in. im in the process of hacking it for d6 as im getting desperate..

subscribe

subscribe

subscribing

suscribing

+1

subscribing

+1

Note that the Upgrade Status module (http://drupal.org/project/upgrade_status) indicates that there is no work in progress on a D6 update.

suscribing

can someone out there just confirm or deny whether this module is being worked on for D6? Perhaps AgileWare? I have made something (much like simonc) but its very buggy and realise that someone out there must have something better in the pipeline.. ??!

I believe Agileware is no longer doing development. Other modules that they are the main dev on (like Taxonomy Redirect) seem to be abandoned as well. I'm applying to take over Taxonomy Redirect this weekend. I really hope someone has time to take Computed Field...

Find attached my version.. it may have a few remnants of simonc's code (He did some better things than my original hack). I've tested it on a small build of mine and it *seems* to work. Things that may need looking at
- case 'load': - I have pulled this together in half an hour before dashing off to work .. I need to work out what this code is doing. Its simonc's and I *think* he is trying to do a caching feature.. (there is some code in the http://drupal.org/node/202384 thread that looks interesting too)
- Views integration (I have only just found this thread: http://drupal.org/node/202384)
- A cron callback (I saw this in the feature requests and I agree its a good idea)

If I get some time this evening I'll try to check this more thoroughly..

Yipes... it looks like I came back late to the party here.

Oh well I'll post it anyways.. Here is my working patch against HEAD to bring it to d6. All seems to be working from what I've tested. (IE. non-db fields, db-fields, formatters, views integration, removal of *old code, etc)

Ahh late but still better...!
My morning hack was just that....found quite a few bugs in mine which I was about to fathom out but hey - yours works! Folks: Use moonshines patch. Works a treat!
Moonshine: I'll be honest this patching thing is new to me - not sure if it matters but got some errors in the info file:

(Stripping trailing CRs from patch.)
patching file computed_field.info
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file computed_field.info.rej
(

Need to get this testing me thinks. I'll try and give it a thorough working through.

Hmm.. I honestly don't see what tripped up the patch on your .info file. I was guessing you might not have been patching against HEAD, but it looks like you were.(?)

In any case the .info just has a couple small changes that I'm sure you know. :)

After some people test the patch a bit we can roll up a zip file or something for more general testing. If anyone else has trouble patching let me know and I'll certainly dig deeper.

Does anyone feel like maintaining/co-maintaining this one with me? It's an incrediably powerful field that should *not* die because of a missing maintainer. I'll put in a request here if someone could help, even with just support issues.

Hi Moonshine - yep was patching against head - not sure what was up and yep managed to work out what should go where :) Not a big problem.

Re: maintainers. I would usually jump to it but don't want to do it a dis-service if I can't dedicate much time. More than happy to help where/when I can.. but certainly can't do this single handedly. I'm being hesistant also because my knowledge of the backend of drupal is rather scant to say the least.. But if nobody else steps up I'll put my neck out :)

Small update here, literally one line changed:

- Changes the way multi-value Computed Fields are handled so CCK doesn't try to put a "label" for them in edit forms when they should be invisible.

Again this patch is against the HEAD code found here from June 18th.

http://drupal.org/node/96559

Hi.

For those of us who are... morons when it comes to using patches is it possible to attach a .zip of the module for testing / user purposes?

You can give this a shot, although there is a handbook page on Drupal.org for patching also that would be really good to check out. You'll see there are lots of patches around :)

(the long version is here: http://drupal.org/patch/apply )

in short, download a module. untar/zip it. grab the patch file and download that to the same directory as the module. open up a terminal (you can need a *nix machine or cygwin to do this with)
cd module_directory
patch < cf_0.diff.txt

done. install the module as normal :)

That's the problem I don't have a nix machine or cygwin which is why I usually ask for a full zip

I'm actually not a maintainer or co-maintainer of Computed Field, so really I don't have any access to make cvs commits which trigger new versions of the project. This was just a module that I needed for a project I'm working on this summer, so I worked on porting it.

I've already requested to takeover another project I made a patch for (Taxonomy Redirect), so I'm hesitant to request this project also. (at this point at least) However if people do find bugs in the patch I'll certainly take a look, and try to fix them. I want it to be as clean as possible.

If nothing changes here in a couple weeks, I'll revisit things to see if I have time to take over the module. Ideally I'd like to find a co-maintainer though, even if it's just someone to help with the support queue.

subscribe

7-zip is a nice little program that will open tar and gz files for windows. It's what I am using.

Now, must go play with computed field :)

This is the diff file from #26 Moonshine.

For what it's worth, I spent some time playing with this last night and it seems to work ok so far. Once I got my fields in the right order :P I got exactly what I wanted working.

Is there a 6.x version in the works, outside of whats been linked on this thread?

I don't think Agileware is active with Drupal development any longer, so this one is abandoned. That said, I have an updated patch here.

This patch just has two differences from the previous one:

1) The "Display Format" PHP code actually gets called now! In looking through the 5.x code, they only had the Display Format code getting called for an old implementation of Views. No idea why. So I've enabled it for the various CCK field formatter options now. So now the Drupal 6 version is officially better :D

2) I've added an additional display formatter option that by-passes the "Display Format" code and just outputs the value you've computed. It's called "Computed Value". Ohhh, again better then Drupal 5. :)

So in a nutshell you can now have a computed field value that's seperate from what is actually displayed via the formatters and choose which you want to output via the formatter options in Views or CCK Display Options.

Again this patch is against the HEAD code found here from June 18th.

I cannot seem to find a version that this patch will work for.... any help?

http://drupal.org/node/96559

After adding so many patches to HEAD version, finally got the working piece of computed field module. This is working fine for my requirements, so iam contributing the same, Please note this may not be the final version.

Thanks
KAMAL CHALLA.

KAMAL,

a) Please don't ever change issue names to be the name of the module. This thread was correctly titled "Drupal 6" so people like you could find it in the first place. How will people find this thread if you rename it to "computed field"?!

b) I'm not sure what you did to created your ZIP file, but it is certainly not from the head version of computed field (see: http://drupal.org/node/96559) with the latest patch (see: #37 above) applied. There are not "so many patches" -- people simply download HEAD and apply the latest patch, which is currently in comment #37, to have the latest working version.

c) Never mark an issue like this as "fixed" when all you've done is create a zip file with presumably several old patches applied. This issue won't be "fixed" until a maintainer of this module actually commits the working code to the project. Neither you, nor I, are that person.

If people really need a tarball of this module with the latest patch applied, I'll attach one here.

Thanks so much for this, Moonshine.

Can I bother you to post a few sample snippets here?

Moonshine - top work. (re: #37). Had any offers of (co)maintaining yet? You've done a stirling job of getting it where it is.. If you fancy sticking me down as a co-maintainer & releasing it then go for it..

there are some features that I must get around trying to add.. in particular: http://drupal.org/node/195013 but wondering if we need to create a release first

subscribing

Willwade,

I'm really slammed here at the moment with a couple projects, but will certainly put in a formal request to take over the project if you're interested in co-maintaining. The process takes 2 weeks, assuming we don't hear back from a maintainer. I'll post the request today to the support queue. When that's done we can make an initial dev/beta release. (Although I'm already using it in a couple live sites :) )

FWIW, I only develop w/ D6 here, so hopefully yourself or anyone else interested can help with the D5 version. D5 people speak up :) I think the D4 version would probably end-of-life'd here though...

subscribing

Moonshine

Thanks for Your support and suggestions, as iam new to drupal it is lession to learn how to contribute the modules and patches

Thanks Again

KC

Is there an argument to be made for integrating Computed Field into the main CCK project? It's hardly as targeted as other satellite projects (e.g., date, email, image, link).

I'd certainly love to see it included. It's really not that far off from other general use fields like nodereference, and really it's quite small. Assuming they re-assign control of the module here, I'll approach Yched and KarenS to see what they think.

Subscribing, and Moonshine, thanks for your work in porting this. I'd love to see you take over as the maintainer here.

@Moonshine : actually we considered that at some point, when it was obvious that computed_field was abandoned.

Computed field in itself would be rightly a part of 'core' cck fields. But I am personnally not willing to take the extra overhead of maintaining / debugging / providing support for the module, though. CCK as it currently stands is already a fair amount of work, as you can tell from the fact that CCK D6 is still not officially released. So I'd very much prefer if someone (wink wink) stood up and took care of the module as a contrib field.

Subscribing. Thanks for the port Moonshine!

I use computed field a lot, so I'm happy to help out, but don't have time to take over responsibility. I'll be glad to help get the D6 version working if someone steps in as a maintainer.

And I don't rule out the idea of moving this into CCK in the future -- I already had put that bug in yched's ear :)

Well it's now two weeks since I made the post:

#293905: Request to takeover Computed Field project

So I'll put in for CVS access tonight and try to get things switched over this week. I'll have to pick up some quick CVS skills (sorry, SVN fan here :) ), but we should be able to at least get up a working dev version for download pretty quickly.

It seems like the port I have in #37/#41 is working well for those who have tried it so far, so that will likely be the starting point. I have about a dozen computed fields built and in service with it currently. (knock on wood).

Down the road, when the time is right to bring it into CCK, I'd certainly be *more* then happy to help. I really do think it belongs there in then end, and can help support it wherever it lives. It's a vital field.

A DEV version is posted now so I'm going to mark this as fixed.

Any issues with it should be marked against 6.x-1.x-dev as we get things rolling towards bets and final releases for d6.