LifeType 1.2.11 released
13. Jan. 2011New version 1.2.11 with a couple fixes was released in January 2011.
TinyMCE was upgraded, and a couple of important security fixes. See the release notes page for more details.
New version 1.2.11 with a couple fixes was released in January 2011.
TinyMCE was upgraded, and a couple of important security fixes. See the release notes page for more details.
One significant security bug in 1.2.9 (and all previous versions) forced us to release yet another release in the 1.2.x series. Check out the Release notes for more details. Someday we'll kill off this 1.2 branch and get to the fun 2.0 stuff.
Update: 01/27/2010, 7PM EST: If you already grabbed the release, please see the release note on sourceforge regarding an updated file for a quick bug fix.
Lifetype 1.2.9 is primarily a security release, but also a large handful of smaller bugs that were fixed while waiting for 2.0 to be release.
Official release notes and download pageImportant notes with this release:
If you (or one of your users) is using a login that is on the "forbidden_username" list, you should remove that username from the forbidden list, otherwise that user will not be able to upgrade after installing 1.2.9.
Lifetype 1.2.8 is another security release fixing an XSS vulnerability, a problem with category search in the admin interface and some more minor bugfixes (please have a look at the release notes for details).
Official release notesThese are the links to the full Lifetype 1.2.7 packages:
If upgrading from Lifetype 1.2.7, there are packages available which only include new or modified files and will allow you to upgrade from Lifetype 1.2.7 only. These packages can not be used to upgrade from 1.1.x or any other 1.2.x release:
Lifetype 1.2.7 is primarily a security release, though a number of issues with resources have been fixed as well.
These are the links to the full Lifetype 1.2.7 packages:
If upgrading from Lifetype 1.2.6, there are packages available which only include new or modified files and will allow you to upgrade from Lifetype 1.2.6 only. These packages can not be used to upgrade from 1.1.x or any other 1.2 release:
Lifetype 1.2.6 is the latest maintenance release of the 1.2 branch and though we said that 1.2.5 was "as rock-solid as it gets", there continued to be a number of improvements and at least one significant bug fix. There haven't been very many support requests on the forums and we attribute that to the success of the 1.2.5 release. This release just adds icing to the cake.
These are the links to the full LifeType 1.2.6 packages:
If upgrading from Lifetype 1.2.5, there are packages available which only include new or modified files and will allow you to upgrade from Lifetype 1.2.5 only. These packages can not be used to upgrade from 1.1.x or 1.2 to 1.2.6:
Lifetype upgrade package from 1.2.5 (.tar.gz)
Lifetype upgrade package from 1.2.5 (.zip)
Lifetype 1.2.5 is the latest maintenance release of the 1.2 branch and after five maintenance releases, this is as stable and rock-solid as it gets. Continuing with the trend started in the 1.2 branch, Lifetype 1.2.5 delivers a couple of minor new features and some polish under the hood, specially concerning the API. We have noticed that as of late, there has been a somewhat remarkable increase of support issues and bug reports related to the API, so it finally seems like users and developers have started to realize the potential of the fully-featured and documented API that you get with Lifetype (and for free!) We're happy to see such trend and we'll continue to support and encourage enterprising users to make the best out of Lifetype classes and libraries.
These are the links to the full Lifetype 1.2.5 packages:
If upgrading from Lifetype 1.2.4, there are packages available which only include new or modified files and will allow you to upgrade from Lifetype 1.2.4 only. These packages can not be used to upgrade from 1.1.x or 1.2 to 1.2.5:
Lifetype upgrade package from 1.2.4 (.tar.bz)
Lifetype upgrade package from 1.2.4 (.zip)
The following features have been introduced in Lifetype 1.2.5.
Some screens in Lifetype support filtering based on certain conditions but so far there was no easy way to save those filters so that for example we could quickly access the list of users marked as disabled and whose username starts with "a". As of Lifetype 1.2.5, there is a small icon that looks like a link next to each group of filters. This icon is nothing but a link pointing to the current page with its filtered values, so all you need to do is bookmark this link in your browser for future usage.
So far there was no way to disable the data cache, the layer that is responsible of saving data loaded from the database to disk for faster access later, so we have added some additional code for the very few cases where disabling the data cache is needed.
In order to disable the cache, edit the file config/cache.properties.php and make the following change:
$config["cache_method"] = "null";
Setting cache_method to 'null' will effectively disable the data cache.
When a new blog is registered via summary.php, administrators can now optionally receive a notification message informing them of the new regsitration regardless of the status of the blog.
In addition to the API fixes mentioned above, there's two long standing issues that have been addressed in this release: Lifetype can finally handle backslashes comfortably and the size of thumbnails is correctly calculated when keeping the aspect ratio and using the GD backend. An important issue that was allowing spam comments to be saved to the database instead of being rejected as spam has also been fixed has also been fixed.
This is the full list of issues fixed in Lifetype 1.2.5, extracted from the project's bug tracking system:
1359: Fix for Blogs::getAllBlogs()
1366: Files uploaded to the wrong destination when using the API
1367: "Default article category" not working
1141: Backslashes getting filtered
1356: Font options greyed out after preview
1376: Joomla user data provider not working with Joomla older than 1.0.13
1382: In the edit categories menu, a 0 is shown incorrectly if there aren't any published articles in a category.
1380: Conditionally show categories on the main page is broken.
1386: Spammers are able to post comments even if comments are disabled for a particular post
1387: comments with article_id = 0 created by some spam bots
1392: PluginTemplatedView not using cache anyway
1395: BlogNameValidator() will cause add blog error even the Chinese blog name is valid
1396: Templates directory hardcoded in baserequestgenerator.class.php
1400: PDbResultSet::GetArray() missing
1409: Problems displaying article categories
1413: Dots as part of a category name do not work with custom URLs
1407: final_size_thumbnail is calculated wrong
We released a beta version of the newest bugfix release of the 1.2 branch, Lifetype 1.2.5.
We've upgraded TinyMCE to 2.1.2, worked out some annoying little issues related to using backslashes as part of post contents and fixed a few more minor issues, all to make Lifetype 1.2.5 an even more stable and fine release for our users.
A more detailed list of fixes and improvements will be provided when the final release is available, but in the meantime you can check the list in the project's bug tracker: go to the "view issues" section of our bug tracker and select "Fixed 1.2.5" as the filter.
Packages containing the full Lifetype 1.2.5-beta release are available by following the links below:
Lifetype 1.2.5-beta (.tar.bz2)
If you're already running Lifetype 1.2.4, it is possible to upgrade using an incremental release:
Lifetype 1.2.5-beta upgrade package from Lifetype 1.2.4 (.zip)
Lifetype 1.2.5-beta upgrade package from Lifetype 1.2.4 (.tar.gz)
Please report any issues with this beta via the project's bug tracker, or feel free to discuss any topic in the project's forums.
If there are no major issues reported related to this release, a final release of Lifetype 1.2.5 will take place during the next few days.
Packt Publishing is hosting the 2007 Open Source CMS Awards and LifeType made it to the final in the category "Best Open Source Social Networking CMS". We have some serious competition in our group: Drupal and Wordpress. (Although I don't think Wordpress can be considered "Social Networking CMS" as it's only a single blog installation, but that's another story. ;-)
Please help us win the contest and vote for us (fill in your name and e-mail in the top right corner).