Closed (fixed)
Project:
WYSIWYG image upload - Inline images for your WYSIWYG
Version:
6.x-1.0-beta7
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Jan 2010 at 22:57 UTC
Updated:
29 Jan 2010 at 15:19 UTC
Jump to comment: Most recent file
Comments
Comment #1
kndrThis is my patch
Comment #2
eugenmayer commentedYou are ofc right, i did not thought to well about that one. Thanks of the patch!
Fixed in BETA7
Comment #3
eugenmayer commentedComment #4
kndrPatch hasn't been properly applied in beta7
Comment #5
kndrThe same patch but for beta7
Comment #6
eugenmayer commentedThe patch has been applied, but the preset "Big" has been removed (before in BETA5). The current patch just adds it again, i cant see it changing an logics?
Comment #7
kndrHm. For me, logic is differnet. Look at if statement and its brackets. Function imagecache_presets should be called only once.
Before patch:
After patch:
Comment #8
eugenmayer commentedThats not needed, as its already cached and not called on every request.
The only thing was the raise condition to be cared of, so if cache is clean, we dont get locked.
Convinced, or did i still miss something?
Comment #9
kndrI was trying to reproduce the error WSOD after intstallation WYSIWYG Imageupload (my mistake - white screen of death, not blue :) )
Try reproduce this error in 4 steps:
1) Install fresh copy Drupal 6.15.
2) Enable:
Color
Comment
Database Logging
Help
Menu
Taxonomy
Update Status
3) Install
Image API 6.x-1.x-dev
Image API GD2 6.x-1.x-dev
Image Cache 6.x-2.x-dev
Image Cache UI 6.x-2.x-dev
CVS Deploy 6.x-1.x-dev
Transliteration 6.x-2.x-dev
jQuery UI 6.x-1.x-dev
jQuery Update 6.x-2.x-dev
Wysiwyg 6.x-2.x-dev
JQueryUpdate 6.x-1.0
Drupal works well.
4) Now, install WYSIWYG ImageUpload and you will see WSOD.
Comment #10
eugenmayer commentedkndr thank you a lot for your time!
And you actually think, this is because of this piece of unpatched code? Is it a single case, does it work after it?
Comment #11
kndrProblem has gone when I patch the beta7 with #5 but first try to reproduce this error before you make any decision and commit changes to your code.
Comment #12
EgonO commentedsame problem here - patch from #5 fixed the error.
Comment #13
eugenmayer commentedOk fine, convinced. Will apply the patch to BETA8. Thanks!
Comment #14
eugenmayer commented