Active
Project:
Whizzywig - A complete WYSIWYG Editor
Version:
6.x-2.0-beta6
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
26 Sep 2010 at 21:27 UTC
Updated:
15 Nov 2010 at 05:40 UTC
When I click on "insert image" in the file browser I'm redirect to my user folder and nothing happens.
Checking firebug console I found this
window.opener.document.getElementById("if_url") is null
after the button is clicked.
Permissions are right (the image is uploaded correctly).
Can you help me?
Comments
Comment #1
upupax commentedSorry, I forgot to specify: the issue is related to the "insert image" displayed in the file browser popup window next to each image.
Comment #2
ovidiua2003 commentedsubscribing. have the same issue. nothing happens when i press the insert image button
Comment #3
jim22 commentedMe too. "insert" image (action) button does nothing. However, I am able to browse and upload images.
Thanks.
Comment #4
rlhawk1 commentedSubscribing. I'm having the same issue. Changing priority to 'major' since it's "For issues which have significant repercussions, but do not render the whole system unusable."
Comment #5
drupalnesia commentedHi, please give me more info: which file/image browser do you use?
Because Whizzywig 6.x-2.x comes with 2 file browsers:
- original: this is original file browser from Whizzywig library
- modified: a custom file browser, specified for Drupal
Comment #6
drupalnesia commentedDear, please try:
6.x-2.0-beta5
-------------
Buf fix: error insert image with modified File Browser
Comment #7
Joel MMCC commentedI installed 6.x-2.0-beta5 last night on my in-house testing server, and sure enough, it fixed the WhizzyBrowse3 insert problem.
But when I installed it on the live deployed server just now, it did not fix the problem. It’s still doing what it did before with beta4, namely, clicking the [Insert] button to the right of an image returns the browser to the user’s home (“u#”) directory (which, if they were already there and had not navigated elsewhere, appears to have no effect at all). I even tried Flushing all Caches. I can’t imagine what’s different between the two servers to cause this. I double- and triple-checked to be absolutely sure that the fully updated code in both the “sites/all/modules/whizzywig” and the “sites/all/libraries/whizzywig” directories was uploaded.
It seems for now that the only viable workaround is going to be to go with the IMCE, Wysiwyg, and the IMCE-Wysiwyg Bridge modules. Last time I tried to use those with Whizzywig (6.x-1.x), the resulting editor area replacing the textarea was very small regardless of the physical space available (this is using AdaptiveThemes). Not sure why. I’ll try that again and see if it still does that with 6.x-2.0.
Comment #8
pmflav commentedUnfortunately with 6.x-2.0-beta5 I am still unable to insert image.
Uploading the image with the modified browser works fine, but clicking on insert does nothing.
Comment #9
pmflav commentedsorry to have to do this.
But bump.....
Everything about this editor is awesome except for the image issue.
Comment #10
drupalnesia commented@pmflav: I need more details ...
1. your browser type
2. make sure you have clear all drupal cache and web browser cache
Edit: please click "Set to default" on Whizzywig configuration page, some variables need to overwrite with these default values.
Comment #11
pmflav commentedSorry.
It would seem the error was indeed my end. It all of a sudden started working.
Perfect WYSIWYG. Cheers mate.
Comment #12
Joel MMCC commentedStill not working for me, and this is after clearing all Drupal and browser (latest Google Chrome) caches, updating more modules so I ran update.php again, [ Reset to Defaults ] on the Whizzywig configuration page, etc.
Still doing what it was doing before: clicking any [ Insert ] button in the Modified File Browser sends the user back to their own home directory and does nothing else. Original File Browser works fine, insofar as it works at all (no access to other directories, etc.).
HELP!! It works fine on my in-house test server (same browser, same other modules for the most part, same everything else), but not on the live server! What gives!?
Comment #13
Joel MMCC commentedJust verified that we’re still having the problem on our live server with Beta 6 as well.