Geeklog 2.1.0 is now available for download.
There are a number of new features and fixes with this version of Geeklog. The major ones include:
- Integrated Caching Template Library original developed by Joe Mucchiello
- Speed increases by added configurable caching support for blocks, staticpages, the topic tree structure and articles
- New OAuth login methods supported (Google, Microsoft, Yahoo)
- Updated to jQuery 1.10.2 and jQuery UI to 1.10.3
- Added a Filemanager
The complete list of features and fixes can be found in the history.txt file located in the release under the docs directory. You can also read this article for more information.
Please note: With Geeklog 2.1.0 plugins developed for Geeklog 1.8.2 or older which install and/or access blocks, or access article topics, most likely will be not compatible. If you use any plugins that perform these functions please check with the plugin developer to make sure they are compatible before upgrading Geeklog. If you are not sure about 1 or more plugins and still wish to upgrade your Geeklog website then either disable the plugin(s) or uninstall it. All Core plugins have been updated and support Geeklog 2.1.0
We decided to go ahead with the Geeklog 2.1.0 release even though there are 2 outstanding issues.
- When template caching is turned on some servers may return a blank for a cached template instead of the actual template. This happens only rarely on some systems. We currently cannot reproduce this. If you can reproduce this bug consistently please add what information you can to the following bug report[*1] to help us fix this problem. If you are experiencing this problem the current fix is to disable template caching in the Geeklog Configuration.
- The CKEditor currently disables itself on certain browsers available for Android devices. Geeklog fails to detect when the CKEditor disables itself and still presents the form (which expects the CKEditor to be running). This means that the user will not be able to submit anything. We need to either display a warning message to the user about his browser or, (the better option) detect when the CKEditor disables itself and have the form default to text mode. If your users tend to use older versions of the Android browser you may want to disable the CKEditor or default your post mode to Text.
If one or more of these issues get resolved in the near future we may either do a service release for Geeklog 2.1.0 or if we have other bugs that have been fixed roll all the fixes into Geeklog 2.1.1.