Zphpbb Zikula module version 1.0.0 has been released. This is an integration for well known open source forum solution: phpBB.
Zichat Zikula module version 1.0.0 has been released. AJAX chat and phpFreeChat are used to integrate.
KCFinder Zikula system plugin version 1.0.0 has been released. KCFinder is free open-source web file manager and uploader.
We are happy to announce that a new version of ModuleStudio is available. ModuleStudio 0.6.0 includes several new features and many bugfixes.
The most important improvement is a textual syntax which defines a new and more readable model file format. Also there is a migration function for converting your existing models to this new notation automatically.
I wrote a SystemPlugin for TCPDF. Today the plugins isn't used by any module, but this may change :). Advantages:
Have fun trying out and submit issues and pull requests!
Invitation is a module that allows your users to invite other users via email to your website. You can add some information to the module that is sent with each invitation email.
ContactList is a module for social networks and communities that offers a buddy list functionality.
The module was refactored for Zikula 1.3 and is now published as version 2.0.0.
MUImage 1.0.0 is prepared for Zikula 1.3.4 or higher to download. MUImage is a classic gallery module you can organize pictures in albums and sub albums with. MUImage is conceptual developed with ModuleStudio. So it uses Doctrine 2 already. For the general user group it is possible to set the allowed number of albums, sub albums and pictures. MUImage contains a import function for mediashare. So you can import albums and their pictures. Please read the wiki of MUImage on Github.
My fellow web developers, the state of jQuery is strong.
For more about exciting happenings in the (near) future of jQuery, read the rest of the story...
From Zikula Core 1.4 we have started using Composer and I've been asked to explain the reasoning behind this. Composer is a PHP dependency manager that has taken the PHP community by storm. It is vastly superior to PEAR for a number of reasons I will cover in this post.
Until recently, we've always stored vendor libraries directly in the core repository and it's always been a maintenance chore to update vendor libraries. Using Composer, one can just specify the libraries one depends on and it will not only go and download them for you, but it'll update the packages when there are upstream changes (all controllable). What this means for developers is you must manually run the composer command after cloning a repository and when the composer.json manifest is updated.
But that's not all, because there's also packagist.org which tracks all packages available in Composer (although Composer is not coupled to Packagist). This is great news for library authors because there is immediate exposure to the PHP community. All a library author needs to do is define a composer.json manifest in their Github repository (or any VCS repository for that matter) and then tell Packagist about it. From there on, others can specify your library with just a single line in your project's composer.json manifest.
Where the real magic happens however is they way in which Composer is able to solve dependencies. You might rely on just one vendor library, say "doctrine/doctrine-orm version 2.3.0" - with just that one require, composer will download and manage all the other requirements, like Doctrine Common, Doctrine DBAL, Symfony2 Yaml and Console.
Composer's last piece of magic is it's ability to autoload PSR-0 compliant library, and in fact, most non-compliant libraries also as it generates an autoloader specific to your requirements. Clever stuff!
Next time you get the source version of Zikula Core 1.4, please checkout the README.md for instructions on how to run Composer
In response to a common complaint I am announcing some changes to the recommended module repository structures in GIT. This doesnâ€™t affect modules in Zikula Core 1.3 in any way but this change will make it easier to checkout modules directly into your Zikula modules/ folder.
The other reason is when a module is tagged it at Github, the archive will be autocreated without any
Most modules are currently using following the structure.
src/ modules/ ModuleName/ lib/ ModuleName/ Controller/ Admin.php User.php templates/ modulename_user_view.tpl
The problem with this is that you cannot checkout repositories directly into Zikulaâ€™s modules/ without using cumbersome symbolic links. This vastly complicates things and is a constant source of frustration.
The following structural change should be done now for all 1.3 modules. Here is a simple example using EZComments as an example. Wereâ€™ simply going to move all the files from src/modules/EZComments up to the moduleâ€™s root folder.
git clone [email protected]:/zikula-modules/EZComments cd EZComments git mv src/modules/EZComments/* . git commit -a -m â€œRestructure repository layoutâ€ git push origin master
Footnote: This assumes the 1.3 module version is in the master branch. If you do have lower versions that are 1.3 compatible you should apply the changes to the lower lower branch, then switch to master and merge.
Since we started using GIT some years ago, a branch and tagging convention has grown in the PHP community and been cemented by Composer PHP dependency management. These changes to branch and tag naming are compulsory for Zikula modules and will aid future automation.
Modules must be released with versioning that represents the a.b.c Semantic Versioning (http://semver.org/). For example 2.3.0, 2.3.1 â€¦ 2.3.12 and so on. Where the c is the maintenance (bugfix) version.
If you maintain just one version series, then you should have just the master branch. E.g.
master - Your development branch
If you maintain more than one bugfix branch (e.g. 2.3 and 2.4 series) as well as a current new version, you must name them like this:
2.3 - maintenance branch of 2.3.x series 2.4 - maintenance branch of 2.4.x series master - latest development branch (could be 2.5, 2.6 or even 3.0 doesnâ€™t matter)
When tagging releases you must tag them as the final release version so 2.3.1 would be tagged 2.3.1, 2.4.0 would be tagged 2.4.0. You can optionally prefix it with a â€˜vâ€™, e.g. v2.3.0 but that is entirely optional. Remember Semantic Versioning allows a.b.c-d so you can also tag beta/rc releases if you wish, e.g. 2.3.0-beta1
When making bug fixes youâ€™d always commit to the lowest branch where the fix should be applied, and then merge up. For example.
git checkout 2.3 # commit a set of fixes
git checkout 2.4 git merge 2.3 # merges the 2.3 branch to current checkout (2.4) git checkout master git merge 2.4 # merges the 2.3 branch to current checkout (master)
Renaming branches is as simple as follows. Letâ€™s rename release-3 to 3.4
git checkout -b 3.4 release-3 git push origin 3.4 git branch -D release-3 git push origin :release-3
ClickedMe is a small module developed for social networks / communities. It will offer a block for your users that will show them the last visitors of their profile page.
Please read upgrade information in the docs folder before you upgrade from an old version.
ClickedMe was implemented for Zikula 1.3.x
a bugfix release 3.0.1 for Formicula has been released for Zikula 1.3.x. The list of closed tickets can be found in the github project here. The project has been moved from the github account of Frank (landseer) to the german community zikula-ev. Thanks Frank for the development of this simple yet great module. The new version can be found in the Get Zikula 1.3.5 page.
Zikula Core 1.3.5 (build 20) is available for general release as of today.
This is a bugfix update with some new features.
You are recommended to upgrade to Zikula Core 1.3.5. Please download the latest version from the Get Zikula 1.3 page.
To name a few highlights:
Many thanks of course to the Zikula Core Development Team and Contributors and the users who reported these issues.
Weblinks 3.0.0 is released as of 30 November 2012
This new version requires Zikula Core 1.3+
A special thank you to Petzi-Juist - Klaus Petzka for all his work on previous versions. His unreleased version 2.1.0 was a big step in the development of v3.0.0!
If you are willing to make a 'thank you' donation please Send a private message to craigh. Donations are very encouraging!
The following changes were made for version 3.0.0:
- converted to 1.3 standards (including conversion to Doctrine 2)
- removed need for modrequest and newlink tables through refactoring
- added 1.3-style hooks
- css in forms/buttons re-styled to 1.3-standards
- removed all old deprecated tables (votes, etc)
- removed all import routines (import as needed before upgrade to 3.0.0)
- pending content moved to new standard which requires no configuration. just check
the box in the admin settings
- added more information to the delete category page so it is clear what is to be deleted
- added additional link validation in places where useful
- add Content plugin to display list of links by category
Version 2.1.0 changelog (not released)
- converted to Gettext
- css has changed to Zikula 1.2 style
- little bugfixes
- now it is possible to change the parent of a category
- import function for CmodsWebLinks
- allow multiple use of an URL
- thumbnails with websnapr
PostCalendar 8.0.0 has been released! PostCalendar is a calendar module for Zikula with multiple views, private calendars, Content Module support and much more.
I am thankful to give the community a new version of PostCalendar that incorporates new technologies that are available as Zikula Core improves. In addition new requested features such as special repeating event options and import of data from the TimeIt module have been added. The use of jQuery-UI has made many aspects of the module better - especially the new event form! Also a new iCal view is available!
PostCalendar 8.0.0 requires Zikula >= 1.3.5 (or 1.3.3 with updated jquery_datepicker plugin - see below**)
Zikula Core 1.3.4 (build 35) is available for general release as of today.
This update resolves some issues that were holding people back in upgrading from Zikula 1.2.x, of course a lot of other fixes and some new features. This update makes the Zikula 1.3 release even more mature. In total 91 tickets are closed !!
You are recommended to upgrade to Zikula Core 1.3.4. Please download the latest version from the Get Zikula 1.3 page.
Full details are available in the big closed ticket list for the 1.3.4 milestone.
Many thanks of course to the Zikula Core Development Team and Contributors and the users who reported these issues.
The Downloads module has been updated to version 3.1.3 addressing several bugs present in previous versions.
Zikula Core 1.3.3 (build 70) is available for general release as of today.
This update resolves some minor issues and adds some new minor features.
You are recommended to upgrade to Zikula Core 1.3.3. Please download the latest version from the Get Zikula page.
Addition of jQuery-UI
update of jQuery
Improved cache handling
Improved page/module identification (especially in shorturls)
Conversion of Admin and Blocks module to Doctrine 2
Full details are available in the closed ticket list.
Many thanks to the Zikula Core Development Team and Contributors and the users who reported these issues.
Zikula Core 1.2.9 (build 23) is available for general release from today.
This update resolves some minor issues.
You are recommended to upgrade to Zikula Core 1.2.9. Please download the latest version from http://ci.zikula.org/job/Zikula-1.2.9/23/
Bug fix highlights:
Fixed XSS issue in Users module ajax controller.
Many thanks to Stefan Schurtz who reported this issues.
Downloads 3.1.1 has been released.
Downloads 3.1.1 requires the forthcoming Zikula 1.3.3
Downloads is an upgrade of original (PostNuke) Downloads module for Zikula 1.3.x with significantly reduced functionality. Improvements in this version include corrections to caching (contributed by nmpetkov), addition of List block (supported by M. Doucha [mdee28]), and conversion from Doctrine 1.2 to Doctrine 2.1 as well as various other fixes.
You may download the new version from the Try Zikula page.
[updated 29 April 2012]