Posted by Kami Petersen on June 15, 2010 at 10:11pm
3 followers
Jump to:
| Project: | WYSIWYG image upload - Inline images for your WYSIWYG |
| Version: | 6.x-2.9 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | postponed (maintainer needs more info) |
Issue Summary
Selecting an inserted image in a previously saved node, editing the title in the dialog and then saving the node does not result in an updated display of the title in the image caption. Only after a cache table flush the new title is displayed. Maybe this could be done without administrator intervention?
Comments
#1
whait a second:
1.On node A i insert Image a, with a title "title-a".
2 Then on node B i select image a out of the image browser (title should be the filename now, not title-a)
3. Changing the title to title-b and saving
Now in nodeB the title is not correct? or in node A? The title in node A should actually not change at all
#2
#3
This is a dublicate of http://drupal.org/node/830070 - now iam pretty sure you are talking about changes in node-A. The cache you are talking about is the "filter-cache" and you can configure it on your own or even disable this. It is not planned to share settings ( like titles ) across all this image-uses as you read in the other issue, so this is not needed at all - as not desired to work that way
#4
I don't believe it's a dupe. Anyway it's not fixed. More detailed steps to reproduce:
#5
This is filter cache - not a bug.
#6
This is not only for the title/caption, but also for changes to alignment and image cache preset.
#7
Uh, never heard of filter cache. If i click a button saying "Update" (in the dialog of your module), I expect things to update. It doesn't, hence it's a bug. Did you reproduce the behaviour i described or do I have some strange setup?
You mentioned in #3 that the "filter cache" can be configured or even disabled. How? I can't figure out where to do that (but anyway it doesn't sound like a fix).
#8
The filter cache should normaly be cleared for updated nodes. I cant reproduce your issue. Do you use some odd content caching?
#9
tried it on my installtion and on a clean d.17 with wysiwyG_imageupload. Works in both cases.
Reopen if you have further details or can reproduce it in a clean installation.
#10
Just did a clean install on a different machine just to test. Still the same. Specs:
Drupal 6.17
+ default core modules + OpenID core module
WYSIWYG Image upload 6.x-2.0-rc7
ImageAPI 6.x-1.8
ImageAPI GD2 6.x-1.8
ImageCache 6.x-2.0-beta10
ImageCache UI 6.x-2.0-beta10
jQuery UI 6.x-1.3
+ jQuery UI 1.7.3
jQuery Update 6.x-2.0-alpha1
Wysiwyg 6.x-2.x-dev ( 2010-Apr-08 )
+ CKEditor 3.3.1
+ TinyMCE 3.3.7
JQuery UI Dialog API 6.x-1.8
Added only the Upload image button. Enabled the wiki filter. Added permission. Nothing else installed. No status warnings. Anything you'd like me to try?
Regarding the positioning, this is updated as expected while inside the editor, but not updated in the node view after you resave the node until you flush the cache.
BUT: I have an important clue. The bug is only reproduced if there's no change to anything else in the body (or title...). Theory: Drupal only flushes the cache if it sees the node data is different. And this of course doesn't happen as changes to the image are not saved in the node. (as it's just represented as [[wysiwyg_imageupload:6:]] no matter what changes).
#11
Ah i see, that one makes sense!
Thank you for the detailed feedback and your time!
#12
actually filter cache is not cleared : http://api.drupal.org/api/function/cache_clear_all/6 ( upper case ).
I have fixed this with http://github.com/EugenMayer/wysiwyg_imageupload/commit/d8b3844aae16229a...
#13
Could you please test and review it?
#14
woops :)
#15
verified that it is working, will be released in rc8
#16
released in rc8
#17
as far as i can see this is still a problem in 2.9 (and in 2.x dev as of today)
drupal 6.22
wysiwyg 6.x-2.3
jquery_ui 6.x-1.4
jQuery Update 6.x-2.0-alpha1
jquery_ui_dialog 6.x-1.10
#18
Please try 3.x. I cant reproduce this for me, so you have to debug it yourself and hunt a little :)