Make a Lasting Impression

Join the Mailing List

Who's Online

17 user(s) are online (1 user(s) are browsing News and Articles)

Members: 0
Guests: 17

more...
ImpressCMS proudly uses SourceForge
ImpressCMS on Ohloh.net
News and Articles > The ImpressCMS Project Announcement > ImpressCMS 1.3.2 Release Candidate 2 released

ImpressCMS 1.3.2 Release Candidate 2 released

Published by Fiammybe on 2012/4/15 (1485 reads)
ImpressCMS 1.3.2 Release Candidate 2 released
We are very happy to announce the second release candidate of ImpressCMS 1.3.2. This will be the last release candidate before we release the next maintenance release in the stable ImpressCMS 1.3 branch.

Some last updates and changes were included to make the 1.3.2 release more polished when it comes out.

* The iFrame support introduced with the upgrade to HTMLPurifier was verified and is tested as working for Youtube, Vimeo and Blip.tv movies. Site owners will need to enable the option in HTML Purifier settings and add the domains you will allow in iframes
* The 'deep searching' option works as expected now
* Module CSS caching was improved
* TinyMCE was upgraded to version 3.4.9 (latest stable) to fix a regression in the first editor where more than one is on a page
* Posting comments does no longer generate a fault
* Comment editing for anonymous users is no longer a possible option

These are the most significant changes. For full details, please have a look at the milestone information you can find on Assembla.

Attention : this is a Release Candidate for test purposes. It should NOT be used on a live server!

Download 1.3.2 RC2

* 1.3.2 RC2 Full Release (zip package, tar.gz package)

* 1.3.2 RC2 upgrade from ImpressCMS 1.3.1 Final (zip package, tar.gz package)

* 1.3.2 RC2 upgrade from ImpressCMS before 1.3.1 (zip package, tar.gz package)



About ImpressCMS

The goal of the ImpressCMS Project is to stimulate and promote the open source nature of the CMS in both the core and its modules and establish itself as the premiere CMS by expanding the system to meet the needs of their users now and well into the future.

ImpressCMS is -

Open Source
Open Development
Open Philosophy
Open Community



Want to get involved?

If you're looking to join the ImpressCMS project, then get on board! All you need to do is head on over and complete the ImpressCMS Team form. We are looking for a lead developer and release manager for both branches.

We'd love to connect with you ...
* Ohloh project
* Facebook
* Twitter
* LinkedIn group
* Delicious
* Flickr
* YouTube

Contact:
The ImpressCMS Project
Steve Kenow
Spokesperson
press@impresscms.org

Navigate through the articles
Previous article ImpressCMS 1.3.2 Final is released! Announcing ImpressCMS 1.3.2 Release Candidate Next article
The comments are owned by the poster. We aren't responsible for their content.
Poster Thread
sato-san
Posted: 2012/4/17 2:56  Updated: 2012/4/17 2:56
Home away from home
Joined: 2007/12/4
From: /home/日本
Posts: 1740
 Re: ImpressCMS 1.3.2 Release Candidate 2 released
debianus
Posted: 2012/4/18 16:14  Updated: 2012/4/18 16:14
Home away from home
Joined: 2007/12/4
From: Spain
Posts: 1241
 Re: ImpressCMS 1.3.2 Release Candidate 2 released
Problems extracting tar.gz (blank file); zip was fine.
Can anyone confirm this?
skenow
Posted: 2012/4/18 23:23  Updated: 2012/4/18 23:23
Home away from home
Joined: 2007/12/4
From:
Posts: 4051
 Re: ImpressCMS 1.3.2 Release Candidate 2 released
I just downloaded the full tar.gz twice - once on Ubuntu and once on Windows - successfully extracted both times. Maybe yours is coming from a different SourceForge mirror site and isn't fully synchronized? Or some other issue?
sato-san
Posted: 2012/4/19 2:31  Updated: 2012/4/19 2:31
Home away from home
Joined: 2007/12/4
From: /home/日本
Posts: 1740
 Re: ImpressCMS 1.3.2 Release Candidate 2 released
I can open the file as well under linux.
debianus
Posted: 2012/4/19 22:59  Updated: 2012/4/19 22:59
Home away from home
Joined: 2007/12/4
From: Spain
Posts: 1241
 Re: ImpressCMS 1.3.2 Release Candidate 2 released
All fine now. Perhaps, as Steve says, it was a sync problem in the SF server