We designed Foliopress WYSIWYG to work only with the real html image links. Most of our Typepad to Wordpress clients come over with the images already inside the html (we clean it up on the way to be better styled with our default lightbox styling, with some very fancy regex).

Our main commercial clients are usually starting not from Wordpress.

But I see the issue. We’ll try and do something about the parsing to pick up the Wordpress default images.

Thanks for bringing this to our attention. And thank you for the clear and detailed bug report.

[a href="%22default%22"][img src="" alt="" title=""parts"" class="align"right" size-"full" wp-image-"2422""]

I am having the same problem as tom. The core image management no longer works with your plugin enabled. When inserting an image, the shortcodes within the post are the same, but the resulting parsed html gives me an img tag with an empty source. I tried setting permissions for all the images in the ..wp-content/uploads to 777 but this did nothing either (doesn’t seem relevant).

Here’s a sample shortcode produced:
[image title="parts" size="full" id="2422" align="right" linkto="default" ]
Here’s the resulting html:

Any ideas?

what you want to do is to create some classes with different font faces (if you know a bit of CSS you won’t have any problem with this) and then add it into the Custom Dropdown. More on this topic in Installation guide

Hello Jon,

you should be able to hook our editor somewhere the same way as FCK Editor. However it’s relying on WP options, so you will have to take care of that – I think playing with custom-config directory will get you the idea. Maybe it’s enough just to remove it from the fckeditor/ config files. For image management tool, which is based on KFM, you will have to configure your db in configuration.php somehow and maybe also remove some of the WP options.

Thanks,
M.

Any change there’s a standalone version of it? (One that you can plugin in to custom CMS sytems)

You should be setting up the CSS in the back end and in the front end so that your users neither need nor want to mess around with double carriage returns.

If you want to have more white space between paragraphs you should put something like this into your CSS:
#entry p { padding-bottom: 10px; }

If your webpage shows correctly and the problem is just in the editor, make sure you have WYSIWYG mode properly configured using this guide. If there’s some problem with the display even in the WYSIWYG mode, you can enter the above CSS into Custom WYSIWYG CSS in plugin options.

Of course you might want to play with the exact padding value and you must enter the right CSS selector, #entry should work with most templates.

If you really can’t live without extra carriage return, you can use Shift + Enter at the end of paragraph.

If you really need these empty paragraphs, you can just replace line 39 in foliopress-wysiwyg/fckeditor/editor/plugins/foliopress-clean/fckplugin.js with this:

//strChange = strChange.replace (“<p>&nbsp;</p>”,”"); // disabled to allow empty paragraphs

But you have to be careful to do the fix again after each plugin upgrade then.

We really recommend you to go the clean CSS way.

Thanks,
M.

WP & plugins I’m using:
WordPress – 2.9.2
FolioPress WYSIWYG – 0.9.8
Disable WPAUTOP – 1.0
Disable wptexturize – 1.0

Any ideas? Many thanks! -B