Closed (fixed)
Project:
WYSIWYG image upload - Inline images for your WYSIWYG
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2010 at 04:04 UTC
Updated:
26 Jan 2010 at 02:12 UTC
Comments
Comment #1
domineaux commentedI have been messing with this off and on all day. To be real honest I'm not sure I've got the darn WYSIWYG API installed correctly. I read some of the instructions, but they don't seem to be updated well at all. In fact, the document was created months ago. I read some of the comments and all they do is confuse the installation issues more.
So, I'm not sure the problem is WYSIWYG imageupload module.
Regardless, if you can explain this issue that will be a start in one direction. It may not solve the abiliity to use the FCKeditor with the WYSIWYG API of course.
I forgot to mention in the above posting. I actually created the sites/all/libraries folder and placed the FCKEditor inside the libraries folder. The libraries API didn't create anything. In fact, why it is required is rather dubious to me.
Comment #2
eugenmayer commentedHell Domineux, lets clear things up. It seems like you have several questions.
1. Is the WYSIWYG Module installed correct? (Does the settings menü show up in the admin/settings menü?)
2. Were you able to install your prefered editor? That means, does the Editor show up to be chosen under admin/settings/wysiwyg and under the collapsed "installation instructions" its shown as installed?
3. Does the WYSIWYG image upload button apear in the settings of the editor like shown in the screencast?
Comment #3
eugenmayer commentedIs your problem related to http://drupal.org/node/693234 ?
Comment #4
domineaux commentedYes,,,
I have dl the new dev version and will comment on results in this thread
Comment #5
domineaux commentedI see and can set permissions for wysiwyg_imageupload.
At top of the screen I have warning message as follows:
warning: Missing argument 1 for wysiwyg_imageupload_perm() in /home/domainc/public_html/vine/sites/all/modules/wysiwyg_imageupload/wysiwyg_imageupload.module on line 69.
Comment #6
eugenmayer commentedHmm i have the strong feeling i just messed up the release once again..so dev is older then BETA2. Could you please use BETA3. Iam currently setting up a D6.15 clean with garland as testing enviroment.
And i _really_ appritiate your will for testing and helping. Thanks!
Comment #7
domineaux commentedStill get this error when I try to save:
Fatal error: Call to undefined function dsm() in /home/domainc/public_html/vine/sites/all/modules/wysiwyg_imageupload/wysiwyg_imageupload.file.inc on line 96
Using Garland theme the first popup box shows up. The second popup shows up the top half only, then you scroll and see the bottom of the second popup.
Comment #8
eugenmayer commentedWell i fixed most of the bugs in the new BETA4. Just check for the "fixed" issues.
That error + the other described here are fixed. Thank you very much.
Please check the notes on the release, esp. the dependencies.
Comment #9
domineaux commentedYou definitely have my respect for doing all you can to get this working.
I'll spend some more time with it and get back to you by editing this posting.
OK the first popup seems to float into the Editor screen.
The 2nd popup
The scroll bar on the right is not clearly viewable. It looks like part of the block is cut off on the right side.
The popup box scrolling part appears to be about 3 to 4 CM in height, yet the update blocks are about 6CM further down the page.
By being further down the page users will not be looking down there to finish the entry.
Also, after I save the created content the display does not show the image, only the text.
You do seem to have fixed the error messages at permissions and after you save content.
Comment #10
eugenmayer commentedHey,
coudl you open isssues for the tasks and maybe provide screenshots? First, i fixed that issue regarding that garland theme showing the image details with scrollbars (scrollbars are not supposed to be displayed at all there). Its a floting bug.
Would be great if you could provide me a screenshot and open an issue for that bug (and set this one bag to fix). I dont want to mix issues into one issue, because this makes it pretty hard for others to get an overview. Thanks!
Comment #11
domineaux commentedI will give the screenshot thing a go.
I will make screencapture and reduce to 1MB as per attachment requirements.
Love the ideas behind your latest modules your contributions are needed.
Sorry, you are correct about separating issues. It is easy to get carried away conversationally instead of remembering this is an issues reporting type of board.
Comment #12
eugenmayer commentedComment #13
eugenmayer commented