Hello,

when I confugure the imagefield to use a default image, the default image is used like a normal image. That means the user can delete it and the default image will be deleted with the node.

Thanks,
dendie

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Deciphered’s picture

Project: ImageField Tokens » ImageField
Version: 6.x-1.0 » 6.x-3.x-dev

Sounds like an ImageField issue.

Cheers,
Deciphered.

braindrift’s picture

deleted

Deciphered’s picture

Status: Active » Fixed

Sorry, what? I don't understand what you are saying.

If it was fixed, you should have closed the issue.
As I said above, it is unlikely (but not impossibly) to be an issue for ImageField Tokens as that is only related to the ALT and Title fields.

And what's a backup of drupal.org got to do with anything?

Apologies if this comes off rude, but it's first thing in the morning and this post seems to make little sense.

Cheers,
Deciphered.

braindrift’s picture

Sorry, it was my fault.

Forget my comment #2.

This issue is only there, as soon as I enable the ImageField Tokens - module.

Deciphered’s picture

Project: ImageField » ImageField Tokens
Version: 6.x-3.x-dev » 6.x-1.x-dev
Priority: Critical » Normal
Status: Fixed » Active

Will look into it and see what I can find.

braindrift’s picture

Thanks

Dmitriy.trt’s picture

Version: 6.x-1.x-dev » 6.x-1.0
Priority: Normal » Critical
Status: Active » Needs review
FileSize
1.93 KB

For my case this bug is critical. I've set up "image linked to original" formatter and redefined theme function to show image without link for default images. And image will never be default...

Also, on node edit form this default image appears as usual image, so you can delete it and leave all you site without default image. Patch worked for my case, it was made from version 6.x-1.0.

You're using mixed line endings in your code (Unix mixed with Windows), this should be fixed to use only Unix line endings.

chinita7’s picture

I have exactly the same issue. I'll postpone using this module for the time being.

ysamoylenko’s picture

Issue summary: View changes

Hello everyone,

Support of Drupal 6 version of the module is stopped.

I recommend upgrading your website to the newer Drupal core version and use a new module version according to your Drupal core.

Anyway, thank you for your report and contribution.

ysamoylenko’s picture

Status: Needs review » Closed (outdated)