WYSIWYG API - integration w/ FCKEditor and/or Image Resize Filter
| Project: | Image Browser |
| Version: | 6.x-2.x-dev |
| Component: | Plugin: WYSIWYG API |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Thanks for all the good work! Somewhat of a n00b, I've been experimenting with using Image Browser with the WYSIWYG API/FCKEditor. Things seem to work pretty well, but once I choose an image with File Browser, any properties/styles I set on it using the FCKEditor image properties dialog or resize handles don't stick at save time (even though things look right in the editor window before save). Also tried using Image Resize Filter, but that doesn't work either - presumably due to the same underlying issue. Are these issues intentional/expected or am I approaching/configuring things incorrectly?
Posted previously in comments to another issue - dddave suggested creating a new issue and that the problem may be improper input format config.
Thanks for any advice!
#1
That's because you can't do that. Those 'images' you see in FCKeditor cannot be edited because they aren't really 'images'. They are IB Image Tags and hence don't have any of the attributes images nodes have the DOM. This is because all properties/styles should be done through either ImageCache or CSS.
Cheers
#2
Thanks for the reply. I wondered if that might be the case. I'm curious what the rationale is for using the IB image tags as opposed to (I guess) inserting the img src tag so that things would play nice with FCKEditor's dialog, other modules, etc. (please be gentle -- I'm new here and just trying to understand -- I appreciate you taking the time to respond). Is it b/c your images aren't nodes? When do the tags actually get turned into HTML? Save time? Run time? I've no clue about how input filters actually work yet...
I've also been experimenting with the Insert Module and Image Resize Filter following this article:
http://mustardseedmedia.com/podcast/episode29
What I like is that while you can use an ImageCache preset initially, the users can utilize FCKEditor's tweaking and resize handles to scale the image (seems more accessible for your average content creator), and Resize Filter then produces a properly scaled version of the image according to the settings. What I don't like is the lack of the browsing capability for previously uploaded images that your excellent work provides. Thus I was hoping there was a way for everybody to get along.
Again, thanks for your responses and your contribution.
#3
IB is born under the fact that we believe the less control you give to the end user the better. As lets face it the majority of users aren't that web savvy.
You want users to be able to insert images that are of a consistent size to keep uniformity throughout your site. Therefore you setup some ImageCache presets which control the size, cropping and look for images users upload.
Filter tags allow us to set variables which can't be stored in regular tags and greatly help the performance of your site other other methods which could be used.
You also want a set of controls which don't change no matter what editor you use, saying FCKeditor, CKeditor, TinyMCE, etc
And that's the reason IB exists. Sure there are other methods if you want greater flexibility but they come with their shortfalls.
#4
Thanks for taking the time to reply.
#5
+1 to resize filter integration