Wygwam 1.1 Released
September 29, 2009
I’m excited to announce that Wygwam 1.1 is out the door! The big new feature? File browsing and uploading. It’s powered by CKFinder, another fantastic product of CKSource, the company behind CKEditor.
Just like Wygwam’s CKEditor integration, you don’t need to worry about the details. Simply grab and install the latest version, and it’ll kick into gear. You can choose which of your EE upload directories each field is tied to within their field settings.
One other feature worth mentioning: you can now choose which individual buttons are visible within your toolgroups. For example, if you want authors to be able to be able to bold and italicize text, but not underline or strikethrough, simply click once on the Underline and Strikethrough buttons within the Toolbar Configurator to disable them. They’ll dim-out in the Configurator, and be completely missing from your fields!
Wygwam 1.1 is a free upgrade for existing customers. Just use the same Download URL from your Wygwam License email, or enter your License Key into the blue box on Wygwam’s Overview page. New licenses remain only $29.
Nine Comments
John Faulds
September 29, 2009 at 1:10 pm
Presumably you still have to buy your own licence for CKFinder when using the latest version of Wygwam?
Julian
September 29, 2009 at 1:24 pm
Works perfectly. Thank you
Brandon Kelly
September 29, 2009 at 1:28 pm
@John – no, I’ve already purchased OEM licenses for CKEditor and CKFinder, so you’re free to use them without any trouble.
Sean
September 29, 2009 at 3:05 pm
Re: choosing buttons for authors to use. Can this be configured on a per field basis and/or per weblog basis or is it a choose once and it’s the same for all fields/weblogs?
Brandon Kelly
September 29, 2009 at 3:07 pm
It’s per-toolbar configuration. And since you could technically create a new toolbar configuration for every field, it could be per-field.
Brandon Kelly
September 29, 2009 at 3:08 pm
I’ve added a note about CKEditor and CKFinder licenses to Wygwam’s Overview page, to clear confusion going forward.
Sean
September 29, 2009 at 3:08 pm
Brandon,
That’s great… will try this out with my next client.
Rolf Johansson
September 30, 2009 at 5:18 am
This just keeps getting better Brandon. Thanks for thinking of the details.
M-J Jones
October 17, 2009 at 10:29 am
Been using FCKeditor for a year + and I would be glad to switch to Wygwam but discovered that one of the major drawbacks of FCK hasn’t yet be corrected, i.e. pix captioned with alt tag rather than title tag. Hence captions don’t show up in Firefox and Chrome unless one fiddles with the code, which is OK for a webmaster, possible for a trained member of staff, but unconceivable for an ordinary outside user.
Also found that the explanations to customize FCK by adding one’s own stylesheet are close to impossible to grasp. Is the procedure clearer and easier now?
Paste should include an rtf (rich text format) routine which would preserve basic formatting (bold, italics, underline, bullets, subscripts, superscripts, links). Imagine you have 500 documents each several pages long to put to the web, you have to:
* either keep the initial Word formatting and have disparate presentation due to the variety of sources
* manually reformat every text, which doesn’t make sense.
So the only solution now is to make a PDF which more or less any user can produce and limit typing to the teaser… In this case, one doesn’t need FCK…
Aside from the fact that it was slow, FCK is neat and pic upload really useful for people who do not know how to ftp. Slow, tho’ (I don’t mean the upload itself but the time it takes to show the windows/pic list).
Noticed from the demo, that the code view is a bit more readable but still loses selection from HTML view.
This is why I have reverted to:
* standard EE html area for users
* a dedicated standalone html editor (like webuilder) for skilled staff which indents and colors code properly, allows to grab code from a library, has preview, is faster, etc..