• WYSIWYG Image upload 6.x-2.0-rc4
  • jQuery Update 6.x-2.0-alpha1
  • jQuery UI 6.x-1.3
  • JQuery UI 1.7.3 = js library
  • Wysiwyg 6.x-2.1
  • TinyMCE 3.3.7
  • ImageCache 6.x-2.0-beta10
  • MySQL 5.1.43-0.dotdeb.1
  • PHP Version 5.2.12
  • Apache/2.2.9

    • If i upload an image with this module and using it on a node A and later choosing the same image from the image browser on a node B, but changing there e.g. the title or imagecache preset in the dialog, and inserting this in node B, it will change also the image of Node A. At the end the image on node A get the same settings as on Node B. So every time if you use an image of the image browser and change the settings while inserting it, it will also change all others references to it.

    I also tested this with a clean drupal 6.17 installation and the modules mentioned above. Same result on this installation.

    If you look at the wysiwyg_imageupload_entity table, after changing the information in the module dialog for an image to insert it in another node, the present entry for the fid will be overwritten.
    Also the nid id is always the same?

    I also tested this with ckeditor and in different browser ie, firefox, safari, always the same.

    Comments

    twod’s picture

    twod
    Primary language Swedish
    Location Sweden
    commented
    Priority: Critical » Normal
    Status: Active » Closed (works as designed)

    This is not a bug, it's how the module works. The tag inserted by this module in place of an actual image is replaced at render time. When the image's metadata changes, it will be rendered differently everywhere it was placed.

    If you want a different/alternate behavior - like something similar to Image Assist maybe, change this to a feature request and describe how you want it to work in detail.

    eugenmayer’s picture

    eugenmayer commented
    Status: Closed (works as designed) » Active

    Well in this case, this is not by design - actually iam not planning this.

    When you reuse an image it will only mean reuse the fid, so the raw file - all settings are separated. thats why an entity for the editor is identified _inlne_ id. So for every inline-use of an image ( whether in the same node or a other ) you have you very own settings - and thats supposed. This is already build in for revision support. that means if you creata a new revision and then later change a picture which have been in all revisions, it wont affect all the older revisions.

    so actually i was planning it from the start but somehow lost the edge case with the image-browser

    eugenmayer’s picture

    eugenmayer commented
    Status: Active » Fixed

    Fixed in rc5

    eugenmayer’s picture

    eugenmayer commented
    Status: Fixed » Closed (fixed)

    released in rc5