I'm using the dev version of image_browser and I've got jquery ui 1.6 in my jquery_ui module and I'm using WYSIWYG API with TinyMCE.

The image browser seems to work just fine - I have the nice little button in my TinyMCE WYSIWYG and when I click it it lets me upload and then select an image. Once I set everyhthing (imagecache size, style, etc.) and click insert I then see the image in my WYSIWYG and everything looks great. However, when I save/submit the node then where the image should be I just see the code below:

[ibimage==1==member_large==none==self==null]

btw, "member_large" was the name of the image_cache preset I chose on insert.

Am I missing something here?

I LOVE the direction of image browser and have been looking for and thinking of something like this for a while now, so thanks!

Comments

dman’s picture

Category: bug » support
Status: Active » Fixed

README
- enable the input format :-B

(I'm pretty confident I can call this fixed - follow up if not)

jponch’s picture

Can you describe what you mean when you say "enable the input format" for me? I had an input format which used WYSIWYG already on my site prior to setting up image_browser. I then added the image_browser option/button the WYSIWYG preset/profile for that input format and the image_browser icon/button immediately began showing on the WYSIWYG when creating/editing nodes. The input format was enabled already prior to that and in use. Perhaps I'm missing something or just ignorant, so I apologize if this is a stupid question.

Attached are two screenshots, one editing the page and one viewing the page. Thanks for your help.

jponch’s picture

ahh ha! never mind. I just realized there's an additional option that needs to be checked on the input format setting itself. I had only added the button to my WYSIWYG without checking the image browser option for my input format. Thanks again.

dman’s picture

I probably meant to say enable the appropriate input filter on your input format.
I could have been clearer.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.