Release notes for Socialtext 1.8
Please report serious bugs that keep you from getting your job done or small problems that you have noted to email@example.com .
Additions, Changes, and Fixes
This page details the major feature additions and changes in Socialtext 1.8 from the previous version, Socialtext 1.7.2. The Socialtext Documentation page describes these new features in detail.
Socialtext now allows Simple mode editing, which works much like a word processor. When you're editing a page, you can click on the toolbar buttons to format text, and your changes will appear on the screen right away.
You will still need to use Advanced mode for some actions such as editing tables, editing links, and including images in the page.
Simple Editing Known Issues
- You need to format bold, italic, and strikethrough one paragraph at a time. If you select multiple paragraphs, the formatting will be distorted. You can clean up in advanced mode.
- Some things your browser will let you do in Simple mode won't "take" when you Save. Examples are interactively resizing a table or an image, deleting an image, or indenting a list. A few other things, such as deleting an entire table, you may not be able to do at all. Use the Preview link before saving, and Edit More if you need to. Switch to Advanced mode when Simple mode doesn't do what you need.
- Copy and paste from a web page or a word processor will preserve some, but not all, of the appearance of the page once it is saved in the workspace.
- Safari users have access to advanced mode only, not simple mode.
Changes and bug fixes
- When a user navigates away from a page that has unsaved changes, the system provides a warning and lets the user save work.
- A new, top-level email menu has commands for sending and receiving email.
- FetchRSS now supports Atom feeds. See Connections for detail.
- Fixed a bug where sending a page with no title generated an application error.
- Sending email to workspace using Apple mail.app now preserves attachments.
- Strikethrough is less aggressive, so there will be fewer unintended strikethroughs. This happened frequently with emails sent to the workspace.