Which Image module works best with drigg?

Hi,

I am honestly not sure why Drigg seems to have a problem with images :-/
I also heard that the Upload module seems to have problems with it, which is a bit of a pain.

Can anybody else here investigate/have a look?

Thanks,

Merc.

Here's more details about this problem.

I'm confronted with a Dillema:

on one hand I'm faced with Scoop content type's strangest glitch in compatibility with CCK's Imagefield. My users can upload an image together with the scoop. However, when they submit that scoop, that Image will not show up. Later, when they try to edit that scoop again, it's as if that image was never uploaded. And here's the strangest thing: when a user then edits that scoop and tries to add the image for the secong time, that's when the image will appear inside the scoop. Another strange thing is that unlike with other content types, scoop will display the image below the Scoop description, rather than embedded in it (as is the case with other content types' bodies).

[I'm getting the feeling that 'Scoop description' field is written less as a Body, and more as Story's Description, which I remember was behaving quite weirdly too]

The other solution would be to allow the TinyMCE WYSIWYG editor and allow to embed external images from that. Yet TinyMCE is very capricious with "Ctrl+V" pasting, which is what most people use to pase scoop description. Hence, the paragraphs come out all funny. So I'd rather keep Scoop description without the TinyMCE wisiwig.

I think there's a need to come up with some sort of solution for images for drigg module. Digg.com is a news website, and news websites will always display images in their teasers -- it's a way of already telling what the story is roughly about... so as to attract users to that story and make users click on that story. Text alone is boring and not very engaging (after all, we are a very *Visual* society).

Hi,

I think I said this in the Drigg forums...
By the looks of it, the Imagefield problem is _not_ a Drigg problem, but an imagefield bug.
Therefore, regardless of the number of bold words, there isn't much we can do about it.

http://drupal.org/node/215873
http://drupal.org/node/204682
http://drupal.org/node/154969

About this:

"Another strange thing is that unlike with other content types, scoop will display the image below the Scoop description, rather than embedded in it (as is the case with other content types' bodies)."

Please open a separate issue (since this is a separate bug). Please provide:

* EXACTLY how to reproduce it (which modules to install, what to do, etc.)
* The HTML from a "good" content type, and from Drigg. Maybe pointing out the differences

Please try to see if you can get anywhere by following some of the instructions/ideas from the links above.

Bye,

Merc.

Hi,

I would _love_ to see this one resolved... is anybody here able to look into it?
I have never used the image module, and so have no idea.

Merc.

Hi, Tony,

I've tested drigg and imagefield along with imagecache support. This works just fine without any editing to our node-drigg.tpl. This means that the drigg body embeds the image nicely. Only does need some css love of course to make it nicer.

See the attachment. Thanks as always.

I created imagefield named scoop, so the css can find field-field-scoop class to make it float to our desire, says:

See another attachment after some css love:)

Update: In case you have problem with the image placement, just change the weight of the image thru cck administrations to, says -6. And still inside cck administration, don't forget to set your display to your imagecache presets as well. Good luck!

Hi,

THis sounds _very_ interesting.
But... the way Digg does it is actually fantastic: their system "picks" a bunch on images from the page, and lets you chose which image to use for the story. WIth Imagefield, people actually have to actively submit an image... right?

I am still very interested. Can you explain here what you did to configure this, precisely?

Thanks!

Merc.

Hi gausarts,

I wonder how you got Imagefield to work with Drigg??? Wich version of Imagefield are you using?

I'm using Imagefield 5.x-1.2-rc1 and this is what happens: I create a new scoop (url, title, body etc). I browse for the image that I wish to put into my article and Upload that image. The imagefield AJAX shows me a thumbnail preview of that image. I then click submit, and the scoop is created, but the image is not in the node. Then I go to Edit that scoop (no trace of the image can be seen) and I upload that same image again and hit submit, and only then (after second upload) that the uploaded image is nicely embedded inside the scoop. This happens in IE7 and FF.

It may works fine for those who have PHP 5 configured on their servers.

imagecache requires imageAPI that requires PHP 5 !

Thanks

I have PHP 5 - Imagefield 5.x-1.2-rc1 is still problematic...

I've also tested Imagefield 5.x-2.0-rc8 -- same problem

There seems to be some sort of timing or jquery or AJAX clash...

Hi,

I would _love_ to figure out what gausarts did so that imagefield works with Drigg...!

Merc.

hi merc i have nearlly got images working with drig using the same set up used here but the image will onlly save if you add the image to a post that already exists it will never save the first time i found this article helpful while configuring the above set up

http://www.lullabot.com/articles/image_and_image_exact_sizes_vs_imagefie...

i feel like i am very close and hope gausarts will shed some light

Hi, All

The never ending ajax loading didn't happen to me before, but suddenly after installing other modules, this happened. I had no idea which the guilty is, since I deploy several other ajaxified modules. I suspect there seems to be a bug with imagefield 5.x-2.0-rc8, the latest one I used. But in the background it actually finished after sometime. I submit the image, and after a given necessary time! it appears as it should. There is no second time need for me, only submit after sometime, then it works. Perhaps when imagefield gets matured, this should be fine. Anyway, I am not in a hurry now:)

Nothing's wrong with drigg.

After considering the best placement of the image, I finally come up to the latest design, see attachment. This unfortunately needs some hack to node-drigg.tpl to my desire.

If you are interested, here's what I did:

1. I add an imagefield named scoop, give it a resolution 1024x1024 and size 1000 kb (such a waste to be user friendly since I only need thumbnails) and make it single. And also the directory scoop/[user] to easily maintain.

2. I manage the Display thru CCK settings to hide the label, and only display the imagecache preset thumbnail to the size of around 80x80 or less.

3. I want to separate the image handling this time, so I comment line 38 of node-drigg.tpl

and change it to:

Note: I have't seen any problem yet with this. At least I haven't tried to embed any video this far. So any further investigation would be very helpful.

4. And place the code below right after the call to the links variable (

5. Give a css class

That's it. Now I have a perfect placement of the submitted image along with the link stuff. Much nicer and cleaner than digg way.

hi gausarts this may bay a dumb Quest,, but when you refrence the cck administration were do you mean i dont seem to find an admin panel for cck or didyou just mean the area of the content type example scoop were you add the extra fields sorry but i dont know if i am having an eror or not thanks rod

Yes, rod. It's admin/content/types/drigg where you can add the imagefield.

Hi,

Shall I close this issue?
If so, do we have "closing notes" which wil actually "solve" this issue?

Merc.

err well no unless i have missed a solution on another post i think this isue is not really resolved on all the installs i have done i havent yet resolved the post having to be saved once before the image can upload to that post so i am all ears if any one has clear instructions to geting inline image uploads working with drigg thanks

I'm having the exact problem #8 and #12 have. Otherwise imagefield works great with drigg. http://kepplah.com/drigg/ Anyone have any success getting the upload to work on initial submission?

CCK 1.7
ImageField 2.1
ImageCache 2.0
ImageAPI 1.1
JQuery Update 1.0
Drigg 1.31
Drupal 5.7

Hi gausarts,

How did you get the image to resize in step 2?

And what css file did you put '.field-field-scoop' in? Was it nodes.css??

Thanks

Hi Ryan,
You have to create a new imagecache preset, says thumbnail to the size 80x80, scale n crop. Those presets will be available in CCK Display option. Since I merged drigg into garland, I place .field-field-scoop class (remember, you have to name your imagefield to scoop! Well, actually whatever, just keep that name in mind) into style.css. You can always place it wherever drigg calls for it, base.css, etc.

Has anyone had any success trying to find the issue drupalina is experiencing? I've checked the database, and the CCK field data is in fact stored properly to the DB when "submit" is clicked. However it does not appear in the $node when I print_r. When you edit the scoop and fill in the CCK field, it still does not fill the fields, but when you enter data and hit submit this time, the CCK fields do appear in the teaser and full page as expected.

Is there any info I can provide to help fix this bug?

I can use CCK on the Story type just find, so this is somehow related to drigg. And I'm pretty sure I had this working at one time, but something messed it up, some incompatibility?

Hi,

kepplah, I have no idea where to start. HOWEVER, I have an idea...
Could it POSSIBLY be drigg.js that is conflicting with the image upload module?

Can you run some tests and have a look?

THANK YOU!

Merc,

Hello,

I have tried to disable drigg.js (I have renamed it so that it is not working) and the problem occures anyway.
I am not sure though if this is the correct approach of testing :)
If not please tell me how to test it.

One more thing. I am not sure, but initially I had PHP4 installed and it worked i think (but I am not 100% sure).
Know my server is PHP5 and testing show the same problem with imagefield and drigg as mention above #12.
Does anybody has php4 with imagefield and drigg working?

I have made heavy testing with imagefield.

I have found that if you disable promotion method (uncheck active checkbox), problem disapear (this setting >> How many votes before a story goes to the home page?).

Initially I thought that the problem is caused by automated +1 vote, because this doesnt happen with after-edit. I didnt found the way to disable automated +1 vote from submitter.

What else did I found:
- If you fill out the submit form and hit preview (instead of submit), image is there. Image is even written into the file system (i havent check the database).
- PHP4 doesnt help - bug still there (I have set-up PHP4 enviroment).

I am not programmer, but I hope this will help to developers (Merc.) to find and fix imagefield bug.

Thank you for your fix Merc .-)

Hi,

This is *weird*. Can others please confirm this:

"I have found that if you disable promotion method (uncheck active checkbox), problem disapear (this setting >> How many votes before a story goes to the home page?)."

...?!?!?!?!?!?

Merc.

I have put drigg on my other testing drupal installation and the same is happening there (if you disable promotion method, pictures are saved and visible after first submit (with imagefield).

Hi,

Richard_: If others confirm this, and you have _actually_ figured out how to reproduce/fix this issue, I will build a statue in your honour.

Others? Please?

Merc.

Additional info: Imagefield works OK also with promotion (entire) module disabled in module administer section.

P.S. I can only reproduce this behaviour, hardly to fix it Merc. .-) :(

Hi,

Richard: I am not following you. Are you saying that the initial report was incorrect?

Merc.

Hi Merc.

no I just wanted to say that you can disable promotion either way to make imagefield work. You can either enable .module and disable its functionality in the promotion module setting part (which was initial report) with unchecking "activate".
The second option is not to install promotion module or if its already installed, you need to disable entire promotion module (i.e. uninstall) and imagefield then works OK too with first submit.

So the conflict is happening somewhere between promotion module and imagefield.

Hi,

First of all, thank you Richard.

Then... my *god* this is _insane_.

Richard, I have drigg.org at the moment as my test site. Can you please give me a DETAILED (and I mean DETAILED, really, in capital letters) list of operations to do to reproduce the bug AND the fix? Consider that I've never ever installed ImageField, not used it. So, you really really have to guide me in terms of which modules EXACTLY I should install, configure, etc. as well as precise instructions on how to reproduce this.

I can tell you that it's insane that "promotion" is doing this, because it's not doing anything at all to the forms.

Bye,

Merc.

ok .-)

1. you need to have content (CCK) module and NOT to use image module with scoop types. (image crashes with imagefield according imagefield documentation)
2. go to www.drupal.org/project/imagefield and install it

3. go to administer/ContentManagement/ContentTypes
4. open scoop
5. Add field to scoop content type
6. Name it and check field type "image" and hit "create field".
7. Go to Manage fields and check "multiple values" in "Data settings" (this is needed for multiple picture upload support - not necessary).
8. Check if you have Drigg promotion module activated, if not install it.
9. Submit new storry and upload one or more pictures into imagefield. Hit preview (you will see uploaded pictures in preview of scoope node), then submit and you will not see any picture within the scoop (although it was uploaded and you will find it in files directory).
10. Lets try it without this bug. Disable promotion module or uncheck "activate" setting in administration of promotion module.
11. Repeat step nr.9 and you will see that there is no problem with images this time.

ONE more funny thing for you. With promotion module enabled, submit new story with picture. Save it. There will be no image in the body. Then hit "EDIT" and in the image field do not browse for new image (let the field blank) and hit "Upload". What you will see is that firstly uploaded picture will appear in the form. Althoug it appear in the form, if you hit submit storry button, image will not be fixed. If you want to fix and show image, you need to upload new picture.

Hope I didnt forget anything :)
Thank you!

P.S. you said that promotion doesnt play anything with form and that it is insane that it is causing this problem. However, I would like to pay your attention to displaying the scoop after submit button rather then processing of the form, BECAUSE images are uploaded with submit form. I guess that bug is somewhere in displaying FRESH images and maybe some voting is involved - because promotion is about number of votes and submit form assign ONE vote to the scoop automatically...

any luck with this bug? My images are working but I would still like to use the promotion module. This trade off is really frustrating.

Merc. will you have a chance (time) to digg into promotion module and see what role plays this at saving and displaying scoop part? Or maybe it is not promotion code itself only hook order conflict or something???

subscribing

Hi Merc:

I cannot confirm, referring to comment #25.

I disabled the promotion method under:

Home >> Administration >> Site Configuration >> Drigg module >> Promotion

I am still unable to upload images on the first submittal using CCK + imagefield.

I believe CCK uses hook_nodeapi to insert extra stuff (read images). Looking at the raw html after submitting a scoop with embedded image reveals no extra stuff. I was hoping to find a skeleton with perhaps incorrect path to the image file, but there was nada.

Still trying to get to the bottom of this one.

--sicjoy

Hi,

This bugs needs to go. I asked for help to the cck people.

http://drupal.org/node/279937

I hope they will be able to help!

Merc.

I made some progress today:

I have imagefield working on my Drigg test site, but I had to cut out some critical code in the drigg_insert_or_update function inside the drigg.module file. The problem is somewhere in the while (true) loop. I would give a line number, but my code has been changed quite a bit. I had to comment out this loop and add a hack so that Drigg doesn't choke due to the missing code.

At least now the bug is narrowed down to a specific section of code. I'll keep you posted on my progress.

Any thoughts Merc?

--sicjoy

Hi,

This is _good_ progress.
I really hope we don't get to the situation where you find the problem, and discover that it's not actually possible to fix it. Fingers crossed.

Now, the problem seems to be at preview time with the image module. Right?
Is it easy enough to create a test environment where you can *easily* and *quickly* see if things are working?

If it is, then I would frankly start changing the code in the while() loop so that:

1) First of all, it's basically *empty*
2) Then, you uncomment a section. Let's say one fifth. Test it
3) Repeat 2), with another fifth. And then again, and again

Now, WHAT could possibly get cck to choke in that code?!?!??

I think the main candidates are:

votingapi_set_vote($content_type, $node->nid, $v, $account_voter->uid );

$res=drigg_send_trackback_ping($node->trackback_ping_url, $node->nid);

In fact, I can't think of anything else that could possibly upset CCK.

This is the worst bug I've ever seen.

Merc.

Hi,

I made:

http://drupal.org/node/264866

A duplicate of this one. It's the same issue with CCK. That bug has some information, which is why I have this link here.

Merc.

Hi,

The CCK people responded:

http://drupal.org/node/279937

I am not sure it helps. I offered some of my own money to get this fixed as well -- fingers crossed.

Sicjoy: any progress with commenting things out?

Merc.

It's the auto-voting (1st vote) that's causing the problem.

If you comment out the call to votingapi_set_vote inside the before mentioned while loop, CCK imagefield works as advertised.

I would say being able to submit images along with a scoop is more important than automatically casting the first vote. Until we come up with a different way to auto-vote, I'm killing this feature.

--sicjoy

Hehe that was my guess in #24, because that is "obvious" difference between submit and edit.

BUT
as I said, when I disable promotion Imagefield works and disabling promotion dont disable 1stAutoVote.

SO
maybe there is some kind of relation between promotion and 1st vote (maybe promotion rely on first vote?) I do not know logic behind it...

Hi,

This comes from this other bug:

http://drupal.org/node/282772

I reported that other one duplicate. I really want to keep all this info in this bug...

-------------------------------------------------
so here's a nasty problem and the fault is Drigg's fault (I'll explain why).

Problem: I have live site ruuning with Drupal 5.7, Drigg 1.33, Extra Voting Forms, Jquery Update, CCK Imagefield 1.2-rc1 and now I installed Organic Groups (OG).

Even though as we know it already Imagefield and Drigg are not really a match made in heaven, I have this combination on my site and it worked (in instructions I told my users to create scoops first, then edit them and upload image in this second step). Then I installed Organic Groups (OG) to allow members to form groups (like on YahooGroups or GoogleGroups or FacebookGroups), and the Imagefield stopped uploading pictures -- I mean it does not even display the uploaded picture in the submission form -- just an empty space!

So initially I thought that this has nothing to do with Drigg and it must be a conflict between Imagefield 1.2-rc1 and OG 7.3. So I did a clean install of Drupal 5.8 and enabled exactly the same copies of both Imagefield and OG -- and they worked perfectly together. Then I enabled the Drigg modules (including User Karma, but NOT Extra Voting Forms) and there we go: the same problem started on my brand new test site: the imagefield images stopped being uploaded and is not being displayed even in the submission form!!! This leads me to conclude that the problem is in the Drigg modules.

Then, on my live site I disabled the OG, and all is back to normal. Enable OG: the problem is there again.

Then I tested to see if this has anything to do with JQuery update. I replaced the core with JQuery 1.0 (which contains JQuery 1.1.2), then JQuery 2.1-rc1 (which supports JQuery 1.2.6), and then the JQuery from the Extra voting forms (even while Extra Voting Forms is not enabled) -- All the same.... the problem persists. Which means that this might not be a JQuery problem at all. And is probably something to do with Drigg js or any other aspect of Drigg.

Additionally: if its of any help, the log etries are filled with "Page not found" errors in files/images/example_name.jpg

Why am I marking this as critical? Because both OG and CCK Imagefield are very important modules for Drupal and are widely used by Drupal community. Many of the Drigg users that I've spoken to often use OG on their sites.

@Richard_

Disabling promotion doesn't work for me. Perhaps I'm misunderstanding how you disable promotion. Can you specifically tell me how you are disabling it? I can see two different ways:

1) go to admin/settings/drigg/drigg_promotion and untick the Activate? checkbox in the Promotion method 1 section. (This is what I did.)

2) go to admin/build/modules and disable the Drigg promoting module.

There is a relationship between auto-1st-vote and the promotion module: drigg_promotion_new_vote is called during that 1st vote via hook_votingapi_insert.

@Drupalina

The problem seems to be between the imagefield and votingapi modules.

--sicjoy

Hi sicjoy, it works for me disabling promotion module both ways. The result is the same, imagefield works.

@merc
hmm I am going to implement OG too, will see what result I get... but right now I am on holiday with limited access...

@Richard_

What version of Drigg, Extra Voting Forms, User Karma, Votingapi, CCK, Imagefield, and Imagecache are you using?

I am using:

• drigg-5.x-1.x-dev
• extra_voting_forms-5.x-1.x-dev
• user_karma-5.x-1.x-dev
• votingapi-5.x-1.6
• cck-5.x-1.x-dev
• imagefield-5.x-1.x-dev

I am not using imagecache.

--sicjoy

I think i got same issue here... I have no problem when i'm using the imagecache-1.6. I got this problem after using imagecache-2.1

@ Sicjoy #44
(I think the ability to attach images is WAY more important than having the first vote automatically cast.)

OG + Imagefield work fine together, but the moment that Drigg is enabled the images are not even being uploaded in imagefield preview. I thought that this was a separate bug, but Merc things it's the same issue.

my question is:
Sicjoy, does your Imagefield and commented-out-Drigg work with OG (organic groups) installed as well???

thanks...

Hi Drupalina:

I have not tested with OG, but using CCK + imagefield to add images to a scoop is working.

I'm trying to get the auto-first-vote back in, but it is currently disabled.

The new changes are reflected in the current Drigg-5.x-1.x-dev revision. If anyone would like to test it with OG (hint hint) and offer feedback, that would be nice! ;)

--sicjoy

Hi Sicjoy,

I guess one possible fix is to have the "first vote" as optional, since it seems to clash with CCK. So, people who want to use imagefield & C can disable first voting.

But! Sicjoy, I noticed that the weight reorganisation messed things up a little. Now the category and the tags come before the body which looks a little weird:

http://www.drigg.org/submit (as logged in user)

I think that needs a bit of fixing!

Merc.

Update on OG: I've tested the Drigg 1x-dev (from July 14). Of course OG and Imagefield are installed as well. The imagefield is still not uploading. Then I started disabling the Drigg modules one by one, untill all of the Drigg was disabled, and the strange thing is that now that OG and Imagevield were left alone to each other, the image field _still_ did not upload (whereas before... prior to Drigg being enabled Imagefield and OG worked alright together). Then I tried uninstalling the Drigg modules >> ticked all of them > click "Uninstall" -- nothing happened. And now that the imagefield is left alone with OG they don't work together either, even though Drigg is fully disabled. And that's the odd bit -- does that mean that Drigg is corrupting something while being installed in a way that even when it is disabled, the impact is still there???

Once OG itself is disabled I could upload an imagefield into blog content type.

Hi,

Drigg can't possibly be corrupting anything, However, CCK might clash with OG as well as Drigg does (and remember, this happens for some inexplicable reason).

Can others confirm the same OG->Imagefield problems?

Merc.

OG and Imagefield work together. But as soon as you enable Drigg modules, and afterwards disable them, then Imagefield and OG stop working (until OG itself is disabled).

Hi,

This is insane, Drupalina.
Can you please please please verify that this is 1000% correct?
When you've done so, can you please write out the shortest route to reproduce this, starting from drigg-distr.tgz? I will then reproduce this, and check at db-level what on earth is happening.

Please keep in mind that the instructions need to be _clear_. A person who's never used Drupal before needs to be able to follow them,

Merc.

Hi,

Sicjoy, did you see #53? It's important!

Merc.

Hi Merc:

Ref. #53 - OK good call. That's a better temporary fix. I'll fix the weighting as well.

Drupalina:

I don't know what to say. Imagefield is working flawlessly on my test site. I am not using OG, however. Let's take a step back: Can you confirm that the current Drigg-5.x-1.x-dev version works with CCK and Imagefield? If it is still broken for you, can you give me all the gory details? What modules versions you are using? What version of jQuery? Drupal 5.7 or 5.8, etc. Then I'll duplicate your setup and work from there.

This is insidious!

--sicjoy

Hi,

Guys, the OG stuff is a separate topic.
I have had several reports of people having several problems with CCK, and they have all disappeared once they disabled the automatic first vote.

So... well, I really think this bug is closed. As I said, I would open another one for the OG, with detailed reports etc. This bug has become absurdly long, and now that the problem is gone, i would close it.

Bye,

Merc.

Hi Merc,
Sorry for the silence over the recent few days. Sorry, I have been extremely busy with some of that nonsensical "real life" issues. If Drigg-dev and Imagefield work fine together [Gosh, what a relief], please close it for now (and we can reopen it later if problems return).

As an extra last test you can just upload the main OG module and enable it on your test site where Drigg-dev and Imagefield work together; and see if Imagefield still uploads.

As of my original post, I always believed that the OG problem is a separate one from this CCK problem. Now I keep finding a new (minor) set of OG/Drigg hickups, which I will mention later in a separate issue.

Hi,

Drupalina, I am afraid I am unable to run these tests right now. However, I just want confirmation that imagefiled+Drigg = OK. If others give me their OKs, I will close this bug. Please never reopen it -- if there are more problems, it's best to open a new one, maybe with a link to this one. However, well, I hope that's not gonna happen.

Merc.

How do you disable automatic first vote?

Hi,

You need to download the latest CVS or snapshot, the option is in Drigg's tab.

Merc.

thanks merc

Hi,

*** EVERYBODY ***

Can you (that's EVERYBODY) confirm that we can finally

** CLOSE **

** THIS **

** BUG **

...?

Merc.

well I am not sure this bug should be closed, since there is no real fix. We do not know what or where exactely is the bug.
I am afraid closing this bug will lead to delay in finding the real solution/fix.

Hi,

I am closing this bug, because it's fixes.
Anybody wanting to reopen it, please open a new one.

The thig is, there is some weird conflict between VotingAPI and CCK. both have been majorly rewritten for Drupal 6. Drigg is being ported to Drupal 6. So, the fix is THERE -- to avoid an absurd incompatibility between two THIRD PARTY modules.

Closed.

Amen.

Merc.

Hi, sorry to re-open this bug. I've upgraded to .dev (from Aug 1). The imagefield is uploading *sometimes* and sometimes it doesn't. Averything in the "Autovoting" tab is disabled. The Scoops are still starting from a +1 vote, I don't know how to disable it. Couldn't find the "Drigg's tab" ... where exactly is it? please help, so that I can confirm that at least the latest Drigg .dev is working with Imagefield...

---
Also, maybe irrelevant, but I get the following error with this new .dev version

Thanks...

Hi,

The warning are because there is a module you are using which is misusing db_rewrite -- sorry, I don't know which one it is. I am 10000% sure, however, that Drigg handling the db_rewrite function correctly, and your module isn't (it's calling db_rewrite() on an user query, but it's not specifying the "u" parameter).

Also, there is a NEW checkbox in the drigg configuration, called "Automatically cast the first vote by the scoop submitter." you will need to UNCHECK that if you want to use anything related to CCK.

Please only reopen this bug if there is an ABSOLUTE need.

Merc.

@ gausarts

referring to #6

could u please tell how u got the image to display the way it is displayed in the attached screenshot. the url of the original story isn't displayed did u remove that ?

It looks like the extra fields ARE getting saved when a new scoop is submitted. I verified this using phpmyadmin. The problem is CCK is caching the node before the Drigg module finishes it's business. So when you view the new scoop, you are viewing the cache which does not contain the extra fields. So I simply added some code to the Drigg module to reset the cache after the node is created. The result is the fields show up fine.

The fix to this bug:

In the file "\sites\all\modules\drigg\drigg\drigg.module"
change:

function drigg_insert($node) {
drigg_insert_or_update($node, "insert");
}
to:

function drigg_insert($node) {
drigg_insert_or_update($node, "insert");
// CCK bug work around. We clear the cache so CCK fields will appear in the post.
$cid = 'content:'. $node->nid .':'. $node->vid;
cache_clear_all($cid, 'cache_content');
}

Thanks to sandiegoseo for fixing this problem. For more info: http://www.drigg-code.org/node/611

Thank for all your info. Really help me..
http://gotclutch.com/