I hope you don't mind if we continue discussion about Image Assist & FCKeditor integration started in #233791: FCKEditor and Image_Assist in a separate ticket.
The integration is done this way:
- fckeditor.module: assign variable where Image Assist can be found (fckImgAssistPath)
- fckeditor.utils.js: when FCKeditor loading is complete, replace all /load/textarea links
- fckeditor.config.js: load plugin for FCKeditor: plugins/imgassist (it replaces [img_assist] with fake image in WYSIWYG mode)
- img_assist_fckeditor.js: little trick here, replace insertToEditor called by Image Assist with new function
I believe that the next minor release of FCKeditor module should be compatible enough to be listed on Image Assist project page (ad I'll do same thing ;)).
It would be great if you could add img_assist_fckeditor.js to the package. This would reduce the number of required steps during installation.
I would be also happy if you could try the latest dev module along with Image Assist and let me know if you have found any issues or have any suggestions.
btw. I have committed just a couple of minutes ago code that integrates FCKeditor 6.x-1.x-dev with 6.x-1.0-beta1 (seems to work fine).
| Comment | File | Size | Author |
|---|---|---|---|
| #17 | imame assist IE error.jpg | 67.84 KB | balik kampung |
| #3 | img_assist_fckeditor.js_.txt | 1.36 KB | StephaneC |
Comments
Comment #1
sifaan commentedI am trying to get FCKeditor 6.x-1.x-dev to work with img_assist 6.x-1.0-beta1, but I cannot get img_assist to insert the code.
Any suggestions?
Comment #2
sun#251175: No code generated has been marked as duplicate of this issue. Contains *lots of* bug reports.
Comment #3
StephaneC commentedHi,
i tested the Image Assist Integration within FCKEditor using the following configuration :
Drupal 6.2
FCKeditor 6.x-1.x-dev
Image 6.x-1.0-alpha1
Image assist 6.x-1.0-beta1
When i clicked on the "add image button", i got a blank frame.
After debugging, i found that the following code, on top of the
img_assist_fckeditor.js, did not work :I replaced it by the following code (see attached file) :
and now Image Assist works perfectly within FCKEditor (i have tested the previous code on Firefox 2 and IE6).
Regards,
Stephane
Comment #4
wwalc commentedAfter applying changes suggested by StephaneC, everything seems to work fine in Drupal 6 using:
Drupal 6.2
+ Image 6.x-1.x-dev
+ Image Assist 6.x-1.0-beta1
+ FCKeditor module 6.x-1.x-dev (actually DRUPAL-6--1 branch from CVS at this moment)
+ FCKeditor 2.6.1
There are no major compatibility problems with Image Assist module and FCKeditor in Drupal 5, tested with:
Drupal 5.7
+ Image 5.x-1.8
+ Image Assist 5.x-1.6
+ FCKeditor module 5.x-2.x-dev
+ FCKeditor 2.6.1
Both FCKeditor 5/6 dev versions will be released soon as stable, so if anyone have still problems with the above versions (or higher), please report this.
I have added Image Assist to the list of supported modules for images manipulation at http://drupal.org/project/fckeditor.
We can think of adding img_assist_fckeditor.js to the Image Assist package to reduce the number of configuration steps.
Comment #5
rismondo commentedWe are using Drupal 6.2 with:
- Image 6.x-1.0-alpha2
- Image Assist 6.x-1.0-beta1
- FCKeditor module 6.x-1.3-beta
- FCKeditor 2.6.2
When an image is inserted in HTML mode all is fine; if we use "Filter Tag", which would be preferable for us as we will eventually move to a new domain name, the image within fckeditor is shown as the generic "imgassist.gif" icon, although preview works as expected. That makes editing rather less practical. Is there a way to convince fckeditor to show the intended image in the editing area?
Comment #6
belmondo commentedIn response to rismondo's question above I would also like to know the answer. In addition does anybody know if this is an error in my setup or is this by design (in image assist the generic "imgassist.gif" icon shows instead of the intended image when using the filter tag).
Comment #7
ctsrutland commentedI've downloaded ALL the versions of img_assist, but none of them contain a file called img_assist_fckeditor.js.
There's img_assist_tinymce.js, but no fckeditor file.. has it been removed from all the downloads?
Answering myself AGAIN!
the js file is in the fckeditor module, but only in the lastest beta version, not in the 6.1.1 version I had.
Thanks,
Comment #8
jacktonkin commentedThis works for me using Firefox 3, but fails in Internet Explorer 7. I am using
Is this a known issue?
Comment #9
sunFYI: I'm inclined to mark this issue won't fix, because I rather would like to see Wysiwyg API evolving, which aims to avoid 3rd party module specific integration code in modules like Image Assist. This means that I will not work on this issue, instead I'm focusing on Wysiwyg API, adding FCKeditor support there, and remove TinyMCE specific code in Image Assist. Regarding IA, this development is happening in v2.x.
@wwalc: You and the rest of the FCKeditor maintainers are welcome to join these efforts.
Comment #10
MTecknology commentedHere was my fix to some of these issues.
Get rid of TinyMCE, and FCKeditor.
Install Image, and Img_Assist.
Set up Input to allow Img_Assist tags.
Use the second input button. The first never input code into the block, but the second worked perfect.
Comment #11
swindsor commentedDITTO: after hours and hours on this subject I did the following to get a baseline starting point with image assist: (it always ends up being some radio button or check box that is somewhere hidden
This is on 6.x drupal install
1- ripped out fckeditor
2 - ripped out IMCE
3 - ripped out img_assist
4 - put img_assist-6.x-1.0-beta1.tar.gz back in to modules
5 - enalbed it in modules admin
6 - went to admin/settings/img_assist
7 - Set Display image assist on text area settings to "Show on only the listed textareas."
8 - These text areas: (this fixes the "the top button doesn't do anything" (get rid of it)
edit-body
edit-comment
9 - (and this is where the radio button comes in) go to admin/settings/filters (input formats)
10 - configure "filtered HTML" type
11 - click "filters inline images"
this fixes the image showing up when you post the page/story/node whatever
Now from this baseline I will go back and startto put fckeditor Etc. back in and trouble shoot that.
Comment #12
irtech commentedI'm just getting a blank popup.
Image assist: 5.x-1.6
Fckeditor: 5.x-2.1
Firefox 3 (in ubuntu) if that matters.
I copied the .js file - but still no luck.
Any ideas?
Comment #13
tehquickness commentedI have this same exact problem? Is there a solution?
Comment #14
WeAreGeek commented@ ctsrutland: img_assist_fckeditor.js does not come with image_assist, but with the Drupal FCKeditor module. According to the documentation you can:
simply copy the modules/fckeditor/img_assist_fckeditor.js file to modules/img_assist/img_assist_fckeditor.js.
Comment #15
sunAs Wysiwyg API evolves further and I'm focusing on #245799: Update TinyMCE integration to 3.x and #319363: Rewrite editor plugin API, this issue most probably won't fix.
Comment #16
marqpdx commentedPer comment #14, the copying of the js module, that worked for me and eliminated the blank screen popup within FCKeditor.
thanks!
Comment #17
balik kampung commentedI have been looking in the image assist issues but could not find a relevant one to my problem.
I have installed image assist and using FCKeditor for body fields. The image assist is working fine in Firefox but it is showing error in IE 7. (image attached)
Basically the content in my website is created by users and i want the images that are posted inline in the body should be displayed as thumbnails in the teaser view in Frontpage and actual size in the full node.
i have been trying various options (image field, image assist, ICME) for few days to put the images/pictures inline in the content and show as thumbnails in teaser view, but nothing is working as per my requirement.
FCKeditor- unable to create thumbnails for display in teaser view in frontpage
image field- unable to place the images inline in the content
image assist- not working in IE (7)
i found image assist more close to what i want but it is showing blank page popup with the error (attached).
Could some one help me in resolving this issue.
Thanks
www.balikampung.com
Comment #18
Typo-1 commentedDrupal 6.8
Image 6.x-1.0-alpha4
Image Assist 6.x-3.x-dev (2009-Tam-08)
FCKeditor - WYSIWYG HTML editor 6.x-2.0-alpha4
Done as suggested in #14
Tried to find what was suggested in post #3 but didnt find anything similar from img_assist_fckeditor.js
Issue:
After clicking "Image Assist" icon/text in FCKeditor I get blank popup with no errors... Whats up with that and anything anyone can do to it?
Comment #19
Typo-1 commentedFound a way around the blank popup!
From looking "the most common page not found errors" I spotted this: "misc/img_assist_textarea.js"
So I copied img_assist_textarea.js from image_assist -directory to /misc/ and it works!
Comment #20
sunForcing a close of this issue. I do not want to see this issue in the queue any longer. Support for FCKeditor is a Wysiwyg API issue, not Image Assist's.
Comment #21
primalmedia commentedWysisyg API is not compatible with many themes, and will not display an editor, therefore it is not a viable solution. So This topic should not be forced closed. The steps to enable image_assist with FCKeditor should be documented as an FCKeditor issue.
Comment #22
sun"Not compatible with many themes"? Not that I know of. Works in all themes for me. So you should probably fix your theme(s) instead.
Repeating for the last time: Starting from Image Assist 6.x-3.x, Image Assist will expose a plugin to Wysiwyg API that is compatible to all editors. All custom support code for particular editors in Image Assist will be removed. Custom editor integration modules like TinyMCE module, FCKeditor module, or BUeditor module will no longer be supported. Wysiwyg API completely and ultimately takes over the integration and interaction with editors. This happens in #319363: Rewrite editor plugin API.
That is the reason why this issue is a) obsolete and b) a waste of time.
Comment #23
AlexanderPop commentedAfter clicking "Image Assist" icon/text in FCKeditor I get blank popup with no errors...
solving:
copy img_assist_textarea.js from image_assist -directory to /misc/
For me works OK. Thanks to Typo
Comment #24
ginga8 commentedThanks for all the help, i have also copied img_assist_textarea.js from image_assist -directory to /misc/ and that worked for me too. How do I get it to work when i am using filter tag. I can insert the image but all I see is the outline .It neither shows up in the editor or the page when viewing. on the page being viewed all I get is the following where the image is to be.
[img_assist|nid=49|title=test|desc=|link=none|align=left|width=100|height=100]
Comment #25
a_d_jackson commentedDrupal 6.9
img_assist-6.x-2.0-alpha2
I get the same issue where Filter Tag just displays [img_assist....
Comment #26
JohnnyHa commentedWhat you mean by to /misc/. There is no folder called /misc. Where should that folder be?
Comment #27
AlexanderPop commented/misc is a folder in the root Drupal directory
Comment #28
jork_zijlstra@hotmail.com commentedI had the problem of the empty pop-up for image assist.
The pop-up script searches for img_assist_textarea.js in the wrong place, due to a bug in the script.
The following line is located in img_assist_fckeditor.js (copied from fckeditor)
script.src = head.getElementsByTagName('script')[1].src.match( /.*\// ) + 'img_assist_textarea.js';head.getElementsByTagName('script')[1]
This means it gets the first script tag. In my case
<script type="text/javascript" src="/misc/jquery.js?l"></script>It uses this source to create the source to look for the img_assist_textarea.js file in the misc folder.
I have created the following fix. (file img_assist_fckeditor.js)
Replace:
script.src = head.getElementsByTagName('script')[1].src.match( /.*\// ) + 'img_assist_textarea.js';With:
var item = null, i = 0;
while(item = head.getElementsByTagName('script')[i++]){
if(item.src.match("img_assist")){
script.src = head.getElementsByTagName('script')[i].src.match( /.*\// ) + 'img_assist_textarea.js';
break;
}
}
Comment #29
agrivas commentedI had the same issue and it turned out that Javascript Aggregator module prevents it from locating the js. I 've got no time to patch it so I am just mentioning it in case someone else runs in to the same situation. I just disabled "Optimize and Minify JavaScript files" from performance and I got it working. You can leave the "GZip JavaScript" option turned on as it does not affect the plugin.