conjoon

The conjoon development team would like to announce the fourth release candidate for conjoon 0.1.4. This release candidate fixes issues that where recognized when working on the user guide for conjoon. Packed with this release are also fixes for showstoppers which previously occurred in rare cases when downloading email messages.
As always, you can find this release at the download page of the conjoon project home.

Here are the release notes for this version:

Bug

• [CN-351] – At least one header line is too long error
• [CN-413] – Marking Emails as read doesn't work properly
• [CN-414] – Check for base url in install wizard
• [CN-415] – Special chars do not get rendered properly when provided during install wizard
• [CN-422] – Preview Windows do not get updated when using keyboard for navigation
• [CN-423] – Toolbar buttons do not get disabled when email grid reloads
• [CN-424] – Fonts do not get rendered italic when wrapping in slashes
• [CN-429] – Youtube Player keeps playing video when panel/ tab is closed/hidden
• [CN-432] – Marking email item as unread does not work properly
• [CN-434] – Emails without date header cannot be received
• [CN-435] – Confirm dialog when closing an email editor instance is not shown when created from quickpanel
• [CN-436] – Wrong item count for draft folder when removing all messages
• [CN-437] – Sending message from outbox with erroneous server information does not show error message
• [CN-441] – Typo in member "attachmentFacade" in Letterman
• [CN-444] – Refreshing feed items quits with error message "Data too long for column 'content'"
• [CN-445] – Message-Id is generated wrong
• [CN-451] – marking emails as "spam" does not work
• [CN-452] – Marking feed items as read/unread does not work
• [CN-453] – Invalid Mime Messages prevent other messages to be downloaded

Improvement

• [CN-448] – Change references column in groupware_email_items to MEDIUMTEXT

Task

• [CN-430] – Check if timeout for removing iframe when downloading attachment is set to a high enough value
• [CN-433] – Check email address validation for recipients list in email editor
• [CN-442] – Move build.properties to ignore list and instead provide template for this file
• [CN-446] – Look up "2011" strings

We would like to announce the immediate availability of a Hotfix for the issue CN-434.
This fix resolves an issue related to the process of receiving new email messages which suddenly quits with the error message

Problem with value for date "" - Zend_Date threw an exception with the following message: No date part in '' found..

This issue is in consequence of email messages that do not provide a date field in their header. The fix will fall back to add a date field by using the local time the message was received. The fix was applied in r1386 and will be part of the upcoming 0.1.4RC4 release.

Installation Instructions

• Download and install conjoon 0.1.4RC3, if not already done
• Download the file hotfix-CN-434.zip
• unzip the file and copy
  Conjoon/Modules/Groupware/Email/Letterman.php
  to the
  {conjoon_library}/conjoon_libs/Conjoon/Modules/Groupware/Email/-directory.
  Overwrite the existing file.
  The value for {conjoon_library} can be found by opening installation.info.php from the Document Root of your conjoon installation, then look up the last occurrence of $INSTALLATION_INFO and it’s property lib_path
• clear any opcode cache, if needed.

The conjoon development team would like to announce the third release candidate for conjoon 0.1.4. This release candidate fixes issues that previously occurred when working with MySQL as the database backend in “strict” mode. Fixing this issue means also that conjoon stores date time values from now on as UTC dates, which enhances the locale portability of conjoon. The install wizard has been adjusted to let administrators choose a time zone the software runs in, and an additional step for patching existing data to ensure consistency with this -and future – updates.
As always, you can find this release at the download page of the conjoon project home.

Here are the release notes for this version:

Bug

• [CN-396] – MySQL's strict mode prevents overlong dates from being inserted
• [CN-400] – Background not properly rendered when login screen is showing
• [CN-401] – File SystemMessagemanager.js cannot be found during build process of login-target
• [CN-403] – Preset property "default.caching" not properly considered during installation process
• [CN-404] – Wrong doctype declaration in reception's index.html
• [CN-409] – "Fetch Email" button is rendered active when activating Email Tab for the first time
• [CN-412] – Builds do not get generated from proper version

Improvement

• [CN-407] – Improve build process by adding tests / removing file header parts
• [CN-408] – Remove CHANGELOG.txt from repository and let the build-tools auto-generate it

Task

• [CN-402] – Edit build files to consider BC breaks that come with phing 2.4
• [CN-411] – Improve build process for creating packed versions of build

Sub-task

• [CN-397] – The Wizard must provide a default timezone to choose from
• [CN-405] – Create update/patch script for migrating datetime fields prior to 0.1.4

The conjoon development team is proud to announce the immediate availability of conjoon 0.1.4RC2. This is a release candidate for the Twitter oauth release. This will hopefully be the last RC for the 0.1.4 release.

Notable changes from the changelog:

[Email module - client]

• fixed an issue where an email would not be properly referenced when preview window was dragged & droppped into the content panel, then any operation on this panel would have been invoked (reply, reply all, forward) due to the fact that the EditorManager would only accept a record of type EmailItemRecord for creating an editor instance, but not EmailRecord (closes CN-386) (thanks to larissa84)

[Feeds module - backend]

• fixed an issue where the “author” field of a feed entry would not be stored properly in the database, thus, showing the value “Array” as the author name: adjusted backend code to inspect the return value of “getAuthor()” of the feed entry object and apply found values properly (closes CN-387) (reported by e-mike)

[Twitter module - client]

• fixed an issue where replies would not be linked properly due to wrong data type for specific fields; changed those fields to type “string” to make sure that containing ids can be rendered properly (closes CN-384)

[Workbench]

• fixed an issue where the “startup” sound would not play as soon as the workbench is in “ready” state, even if the registry tells that system sounds are enabled: resolved by adding a “onload” listener to the SystemSoundManager that would call attached listeners to tell that it’s ready to be used; previously it was assumed that the driver is ready to be used as soon as the workbench is available (closes CN-385)

[General UI]

• fixed an issue where some regions of a container would not be clickable if it was masked previously by a feed/email preview, and this preview would have been hidden using it’s animation function: adjusted callback so the anim element’s container gets hidden, too (closes CN-388)

[Datastore - mysql]

• fixed an issue where two different indexes would target the same column: changed index “user_id” to operate on column “user_id” (closes CN-390)

The conjoon development team is proud to announce the immediate availability of conjoon 0.1.4RC1. This is a release candidate for a maintenance release which introduces support for Twitter’s oauth features.

Notable changes from the changelog:

[Twitter module - client]

• changed ui of both Wizard/Options panel to consider Twitter’s new oauth
  authorization process

[Twitter module - backend]

• fixed some issues related to deprecated parameters Zend Framework would
  still use when communicating with the Twitter API (see ZF-9215)
• fixed types of fields which would still be set to “int”/”float” whereas
  “string” should be used now

[Vendor]

• Updated Zend Framework to version 1.11.6

We have updated the demo at http://demo.conjoon.org with the latest version of conjoon 0.1.4RC1. This is a maintenance release which enables conjoon’s Twitter client to utilize Twitter’s oauth implementation. The new release will be available tomorrow evening for everyone to download from the official project page at http://www.conjoon.org

With the upcoming release 0.1.4 of conjoon you’ll be able to manage attachments for your Emails. While functionality has been quickly implemented (the GUI has been updated with a number of nifty features), we decided to add full support for storing LOBs in the server’s filesystem.
There are a number of reasons why one would rather not store LOBs into the database – mainly performance wise.
conjoon 0.1.4 will introduce a few new configuration options regarding LOB storage – which can be even changed during runtime. The backend will still maintain relations between the filesystem and the database to keep data integrity – while providing a performance boost and simultaneously reduce space needed by the database to store files, attachments and raw email sources.
So what does this mean for you? First off, the install wizard will be updated to guide you through the needed steps for setting up file system LOB storage. No data has to be migrated, even if you decide to use filesystem LOB storage (resources for LOBs will be determined during runtime). All you have to do is to take proper care of the file permissions to prevent security issues. However, we give advices during setup where necessary – in the end you’re still able to configure your installation to store LOBs in the db.

See http://www.siteartwork.de/2010/06/01/conjoon-dev-notes/ for a related article that describes our new feature more detailed.

We would like to announce the immediate availability of conjoon 0.1.3.2. This is a maintenance release which fixes a showstopper bug. The issue was reported by one of our community members, odomera, who experienced this issue when trying to install the application: Due to an erroneous condition in one of the install scripts, he was not able to proceed to the second step of the installation using the install wizard.

People who could not install any of the releases from the 0.1.3 series are advised to use this release. Other than that, no other changes made it into this release.

We would like to announce the immediate availability of conjoon 0.1.3.1. This is a maintenance release in the 0.1.3 series which fixes an issue with the mysql datastructure script. Due to missing backtickets in a statement, already existing tables for the email attachments would not get properly prepared for the new features introduced in 0.1.3.

This release affects only people who have updated a previous version of conjoon. People who installed 0.1.3 from scratch won’t need this update. All other users are advised to install this version.

The conjoon development team is proud to announce the immediate availability of conjoon 0.1.3. This is a feature release in the 0.1 series which introduces internal download management for handling file downloads.

We have decided to release this feature shortly after the 0.1.2 release due to requests from our community members who’d like to see this feature before the 0.2 version gets released.

Notable changes from the changelog:

[Workbench]

• enhanced “Help” menu, added dialogs for submitting suggestions/bug reports

[Datastore - mysql]

• fixed an issue with datastructure for attachment table, since some attachments could not be saved due to restrictions of content length for “BLOB” fields – changed field “content” in “attachment” table from “BLOB” to “LONGBLOB”

[Email module - client]

• added DownloadManager for queueing downloads in conjoon
• revamped DefaultViewRenderer for displaying email messages to show a resizable and scrollable attachment list

[Email module - backend]

• fixed a security issue where models would not check for proper folder permissions before sending an email message / item to the client
• added functionality for downloading attachments