Version 0.9
0.9.15
- Bug fixes
- 'There is a problem opening your configuration file' warning message removed.
0.9.14
- Bug fixes
- custom-config configuration file replaced by inline JS - less trouble with compatibility issues
0.9.13
- Added language support
- Wordpress caption support
- Autosave glitch fixed
- Image uploader permissions are now configurable
0.9.12
- works with Wordpress 3.0
- working Word count
- Flash/no Flash uploader option fixed
0.9.11
- Wordpress autosave support
- better Wordpress MU support
- HTML entities are not processed by default - keeping your accented characters unchanged
0.9.10
- Image management tool is now using new version of KFM which works with Safari
- Image management tool now allows multiple file uploads via built-in Flash uploader
- Plain text editing option for posts
- Wpautop and wptexturize are disabled on posts edited with Foliopress WYSIWYG - makes sure your posts have the cleanest and untouched HTML possible
0.9.8
- WYSIWYG style configuration now resides in plugin options - easier configuration
- Image management tool now appears with the right year/month/ directory opened
- All uploaded images above certain height and width (check out plugin options) are sized down to fit into it
- Works on sites with secured wp-config.
- Insert FV Wordpress Flowplayer button added
- Pasting dialog receives focus when it appears
- Dreamhost JSON glitch fixed
0.9.7
- Easy Toolbar customization
- Easy Formating dropdown customization
0.9.6
- Multiple image posting
- No need to edit any configuration files
- Available thumbnail sizes are limited by the size of the picture
- Better security
- Automatic wpautop can be turned off
0.9.5
- Safari editor window height issue fixed
- Firefox spellchecker enabled by default
0.9.4
0.9.3
- Introducing the Paste Rich Text Mode button to override standard paste dialog in Firefox and Safari. This lets you select between plain/formated text pasting.
- Automatic wpautop
0.9.2
- Foliopress WYSIWYG now works on secure https sites.
0.9.1
- Bug fixes, new option to hide Wordpress Uploader Buttons.
0.9
- SEO Images are now compatible with FTP uploaded files. Read a manual on how to upload files and prepare them on handling with SEO Images.
10 comments on “Version 0.9”
01
The native WordPress Visual Editor isn’t good for much and I seldom use it but plugins such as NextGen Gallery and CForms add a “button” that inserts a shortcode for a gallery or a contact form. This is a very useful feature. When I activate Foliopress they are missing. Is there a way to turn them in Foliopress?
02
Hello Rick,
The latest version of Foliopress WYSIWYG does work with the extra buttons from Wordpress (and probably NextGen Gallery).
I’ve worked with NextGen Gallery and hated it. It’s really slow. NextGen gallery doesn’t cooperate well with the core Wordpress code.
If load speed matters to you, my recommendation is to use Foliopress WYSIWYG as your gallery software within a post.
If you stick one or two images above the more button, the rest below, you have a very serviceable gallery, combined with SlimBox.
The very latest version of Foliopress WYSIWYG even works with FTP – very hot, you can upload dozens of images at a time – but I’m not sure that version is up here for download yet. If not, we’ll put it up Monday.
Thanks for your question, Rick. We are very actively developing Foliopress WYSIWYG so we appreciate your feedback.
03
I just installed Foliopress (and the 2 disabling plugins) in WordPress mu 2.7 and it works OK. But even with the setting for “full” toolbars, it seems to have less functionality than Advanced TinyMCE, which I was using before. Even simple stuff like non-breaking spaces and custom classes aren’t available.
Am I missing something? Do I still need to install another component? If the sites were just for me, I’d be happy with source code, but some of the people I develop sites for won’t touch the source and really need all those tools.
Though I will say I like the image uploader and the fact that it doesn’t delete empty hard returns or breaks.
04
Hello Bob,
The lack of buttons is deliberate. Those extra buttons produce broken markup. If somebody wants to use   they should be doing it in source code – or usually not at all.
I think you’ll find with the full toolbar absolutely everything you really need is there. We are working on adding some custom classes, which you could do yourself. The custom classes each person needs are different in any case.
Thank you for taking the time to let us know about your concerns.
05
Alec, thanks for responding. The reason I create WordPress sites for clients is so non-technical people can modify content. Some of my clients don’t have trouble making small changes to source code, but most do.
As for custom classes, what would be great is to populate a drop-down list with my own class names. TinyMCE does that, but it has the disadvantage of putting background images and colors into the editing window, which can make text hard to edit.
FYI, another toolbar I find helpful is Viper’s Video Tags. It lets you insert the URL of a video on YouTube, Yahoo, Vimeo and other sites, and it creates the embed code.
Of course, I can’t expect you to re-create every feature that every other editor has, but if your toolbar could be compatible with others, users would have a choice.
06
Hello Bob,
I agree that allowing classes in a drop down menu is a good idea. We’ll do that in June.
I don’t like the idea of integrating video code. It changes often and will be a maintenance nightmare. If somebody wants to insert an external video, they’ll have to be able to copy and past into source code.
As you have noted other editors do lots of other things, but they are difficult to use or ugly. Our stress with Foliopress WYSIWYG is on easy to use, keeping code clean and attractive.
Thank you for the suggestions.
07
Alec,
Thank you for the great plug-ins. They solved the vexing problem with WordPress not supporting commenting out code.
I’ve turned on the full toolbar and the one button/feature I’m not seeing is “Paste as Plain Text.” I also tried pasting in text, highlighting it, and clicking the Remove Format button, but that didn’t get rid of the inherited formatting.
Robert
08
Hello Robert,
Pasting as plain text is a problem we’ve really struggled to fix (we want this feature ourselves). The issue is that Firefox does not allow us to access the clipboard which means we have no way to clean the text before pasting.
Clipboard pasting will work on IE but the workaround is fairly complicated and would introduce non-feature parity which we don’t want as we recommend our clients use Firefox.
The workaround we recommend to people on Windows computers is to open Notepad, paste into Notepad and copy back and then paste into Foliopress WYSIWYG.
An issue that I’m not happy about is that even a plain text paste creates br tags and not paragraphs. That’s a planned fix for the next release.
09
Hi,
Foliopress seems much nicer than the default TinyMCE-editor. Small improvement would be making the plugin work in case the wp-config.php file is moved from the site root to one directory below (eg. from /root/public_html/ to /root/). This is a security measure supported by WordPress since 2.6 and most plugins and instructed by many “securing WordPress” guides.
I’m not sure if its possible to assign css styles to html elements in the editor view. I would like to have css “clear: both;” for all headers, so that left aligned images wouldn’t cause the editor view being a total mess. In my case, each header should start a new line and not float next to an image.
Thanks,
Vinha
10
Hi Vinha,
We’ll look into making Foliopress WYSIWYG work regardless of where WP-Config is (not sure it doesn’t work that way already, as we don’t keep our php files in root either).
You can set up whatever CSS styles you like in your own CSS. That’s the beauty of semantic markup: you fix display with generic tags and without having to add style elements afterwards.
Add a clear: both to your headers or to p tags following paragraphs.
Then when you have a header, there will automatically be clears on it.
Leave a Reply