-
First, if you can add tags to your plugin on WordPress Extend, I suggest you add ‘TinyMce’ and ‘editor’ to your plugin. I found it only by accident, and such great work should be accessible:)
Second, some related questions on images. First, all my images are remotely hosted for speed, bandwith, handling and maintenance reasons. I have placed captions on all my images according to WordPress ‘[caption= which surrounds the tags and ends with [/caption]‘ specifications but this editor does not recognize them. In fact, if I edit a post, it destroys the caption which no longer shows.
Is this a WordPress 3.0 issue? Or do I need to redo a caption somehow if I edit my posts using the Fckeditor? If so, what is the html, since I see no button to insert captions? Currently my image captions are styled using default WordPress class names.
Thanks for your input. Great plugin.
-
-
FYI, I found this site searching for a solution to TinyMCE regarding toolbar button usage.
When I clicked on tables or image buttons, a blank window appeared and my browser attempted to download the htm plugin file. It appears there are any number of causes for this issue, all poorly documented, and it extended to the TinyMCE advanced plug-in also.
Rather than track down all the issues, I found the solution in your wonderful WYSIWYG editor, with the exception of the caption issue listed above.
Hopefully this comment will direct more WordPress users to your site who experience the same issue as me.
Hi Jim,
Thanks for the tips about our listing in the WordPress plugin database.
We do have an issue with captions as our solution is predicated on being compatible with all CMS not just WordPress. After you’ve published a photo with Foliopress WYSIWYG, you just have When you’ve added images with our plugin you can switch to another CMS with no loss, unlike WordPress’s built-in solution with it’s custom short tags.
Perhaps we can add a converter when opening posts but it will not be two way, it will be one way.
WordPress’s whole way of handling images is very database intensive, clunky and not portable (every included image or attachment is eleven database calls). Our way of handling images means that there are no database calls, even if you add twenty images to a single post. Plus our handling of SEO is much more complete (just name your image properly before you upload it).
Thank you for your reply. I got the caption to work (the editor treats it as text, which is fine).
And yes, it was the WordPress treatment of images that inspired me to offload them to an image site. I use both Picasa and Flickr. There are some good plugins to help upload and access them.
Images and text do not belong together in the same database; the processing is much different. Your editor solves the majority of WordPress issues. In fact, as an old programmer, I can say that the WordPress core could be much more adept and faster at the same time. I believe they have strategy issues which dearly affects usability.
Thank you again for the wonderful plugin. I can tell from your work that your team is thinking:)
Hi Jim,
Thanks for your kind words.
We are working on a one way converter of WordPress images into Foliopress WYSIWYG images on post open (it will be an option in preferences). We will set some intelligent defaults for converting Caption and the other attributes into static format. Once converted images will be straight html and easily managed. It should make people’s posts load more quickly with a lower server load as well (advanced aching can help even the current WordPress system though).
Let us know if you run into any other issues.
Hello Jim,
the setting to convert caption shortcodes into HTML was added into Settings -> Foliopress WYSIWYG -> Advanced -> Compatibility Convert [caption] shortcodes before editing. It’s turned on by default.
Thanks,
Martin
