News » Development

Zikula Core 1.4.6 Released!

Contributed by craigh on Feb 11, 2017 - 08:34 PM
Picture 0 for Zikula Core 1.4.6 Released!

The core development team is proud to announce the availabilty of Zikula Core 1.4.6!.


ModuleStudio 0.7.0 released!

Contributed by guite on Dec 31, 2016 - 05:05 PM
Picture 0 for ModuleStudio 0.7.0 released!

Right on time for the new year a new version of ModuleStudio has been released. With ModuleStudio 0.7.0 many innovations become available and simplify the program's handling. The entire user interface has been refurbished and offers new, more powerful editors.


Zikula Core 1.4.3 released!

Contributed by cmf on Sep 02, 2016 - 12:19 AM
Picture 0 for Zikula Core 1.4.3 released!

The core development team is proud to announce the availabilty of Zikula Core 1.4.3.


Serious Core-1.4.2 Upgrade Bug Discovered

Contributed by craigh on Aug 13, 2016 - 11:48 AM
Picture 0 for Serious Core-1.4.2 Upgrade Bug Discovered

Regrettably, a serious upgrade bug has been discovered in the upgrade process for Core-1.4.2. Because of this bug, we cannot currently recommend any upgrades to Core-1.4.2 from any previous version of Zikula.

A straight install of Core-1.4.2 will operate correctly and is not affected by the bug.

The bug has already been corrected in Core-1.4.3 and it is hoped that Core-1.4.3 will be released within the month.

The bug (which again is only apparent on upgrade) will delete all the 'content' data from the Blocks table, rendering all blocks invalid and causing various other problems. There is currently no workaround other than to delete all blocks manually (in the blocks table and the blocks_placements table) and recreate them.

We are very sorry for this inconvenience.


Zikula Core Development Update

Contributed by craigh on Jul 11, 2016 - 02:55 AM
Picture 0 for Zikula Core Development Update

Zikula Core-1.4.3 has been progressing quite well in the last months although, it may not have been obvious to the casual observer of the commit log because most of the serious work was being done in a 'users' development branch.

The User Module in Zikula Core has been entirely refactored to support Twig and Symfony Forms in recent weeks. Not only that, but all functionality relating to the authentication and the registration of users has been separated into a new system module called ZAuth, which is also now included in the core.

As part of the division, new interfaces have been developed to implement independent authentication methods. In addition to the ZAuth module, another example of this is the OAuth module. With the OAuth module authentication may be handled by third party providers like Github and Google (these are already implemented). Future development of this module will include other providers like Facebook and Twitter and the potential for many others through the impressive League of Extraordinary Packages OAuth 2 Client.

Because of these dramatic changes, some BC-breaks have occurred with regard to the old authentication method API and some other minor users module changes.

In addition, work has proceeded on the refactoring most of the other system modules since Core-1.4.2 released. We are aiming toward a completely refactored system for the release of Core-1.4.3. Smarty and all legacy forms and will be gone and fully replaced by Symfony, Doctrine, Twig and new APIs that have been developed since Core-1.4.0.

We anticipate a July release of Core-1.4.3 in keeping with our four month release cycle, but this cannot happen without community support! We need your help in testing development code please!

Finally, the June goal for a Core-2.0.0-beta has been missed. The current goal would be to release a Core-2.0.0-beta shortly after the release of Core-1.4.3 although this will depend somewhat on the ease of removing all legacy code and also updating to Symfony-3.x within the core. At this time, we are unsure of the difficulty involved in these tasks.


Core-1.4.2 Released!

Contributed by craigh on Mar 28, 2016 - 02:40 AM
Picture 0 for Core-1.4.2 Released!

The core development team is proud to announce the availabilty of Zikula Core 1.4.2.


JetBrains Supports Zikula

Contributed by craigh on Mar 11, 2016 - 07:35 AM
Picture 0 for JetBrains Supports Zikula

JetBrains has once again graciously offered their support for ongoing development of the Zikula project by donating licensing of their AWESOME php IDE PhpStorm.

JetBrains makes professional software development a more productive and enjoyable experience.

[They] help developers work faster by automating common, repetitive tasks to enable them to stay focused on code design and the big picture. [They] provide tools to explore and familiarize with code bases faster. [Their] products make it easy for you to take care of quality during all stages of development and spend less time on maintenance tasks.

PhpStorm features a rich and intelligent code editor for PHP that actually "gets" your code and deeply understands its structure, supporting PHP 5.3, 5.4, 5.5 & 5.6 for modern and legacy projects. The IDE provides smart code completion, syntax highlighting, extended code formatting configuration, on-the-fly error checking, code folding, supports language mixtures and more.

Licenses are available to core team members and last one year. If you are interested please contact Craig.

THANK YOU JETBRAINS!


Zikula Core Development Update

Contributed by craigh on Feb 10, 2016 - 02:39 AM
Picture 0 for Zikula Core Development Update

Zikula Core development is moving along at a very nice pace. Since the release of Core 1.4.0 in July 2015 we have moved to a more Symfony-like release process. This means that maintenance releases will be released on a timeline of approximately every four months instead of "when its ready." Already, Core-1.4.1 was released in November 2015, approximately four months after Core-1.4.0. Core-1.4.2 is scheduled for release in March 2016 - again, four months after Core-1.4.1. We intend to maintain this pace going forward.

The status of Core-1.4.x development can always be checked in the consistently updated Changelog. The changelog is also the location to check for newly added features, changes, deprecations and removals. The milestone release schedule is also useful as a general guideline of planned releases, but is not a guarantee of an actual release date.

Additionally, Core-2.0.0 is on pace for a beta release in late June 2016 in parallel with Core-1.4.3. We have also taken a very Symfony-like approach to the development of Core-2.0.0. Just as Symfony 3.0.0 and Symfony 2.8.0 were released together and are essentially the same product but with the removal of backward compatibility in the 3.0.0 product; so to will Zikula Core-2.0.0 be released in a similar way. Core-2.0.0 will be the same as a Core-1.x release (undetermined) with the removal of all backward compatibility. We will then proceed to develop new features into Core-2.x while marking Core-1.x as End Of Life (EOL). The exact timeline of this is yet to be determined.

Core-2.0.0 is essentially an extension of Symfony 3, allowing developers to modularize their approach to development and utilize a Modeling Layer via ModuleStudio to quickly generate features in their application for a fast development curve and easy forward maintenance. The 2.x Core takes advantage of many third party Symfony bundles and other vendor libraries to allow a developer to quickly get up and running with their custom application.


Zikula Core 1.4.0 Release Candidate 4 ready for testing!

Contributed by cmf on Jul 08, 2015 - 11:53 PM
Picture 0 for Zikula Core 1.4.0 Release Candidate 4 ready for testing!

The core development team is proud to announce a pre-release of Zikula Core 1.4.0 Release Candidate 4. Please help testing and report bugs!


Zikula Core 1.4.0 Release Candidate 3 ready for testing!

Contributed by cmf on Jun 28, 2015 - 05:04 AM
Picture 0 for Zikula Core 1.4.0 Release Candidate 3 ready for testing!

The core development team is proud to announce a pre-release of Zikula Core 1.4.0 Release Candidate 3. Please help testing and report bugs!


Zikula Core 1.4.0-RC2 Released!

Contributed by craigh on Mar 31, 2015 - 05:57 AM
Picture 0 for Zikula Core 1.4.0-RC2 Released!

Zikula Core 1.4 Release Candidate 2 is available as of today, 31 March, 2015.

Immediate testing is encouraged. You may download the RC from our Continuous Integration server. Release testing guidelines may be found in the Core wiki. Installation and upgrade documentation can be found in the /docs directory.

Our Quality Assurance cycle, explained also in the Core wiki, will be followed in order to achieve our General Release. Please register your vote on the promotion of this build in the promotion ticket.

Please report all bugs and concerns to our issue tracker on Github. Please understand that bugs will not necessarily halt the release of this build. Bugs may be fixed or postponed to another release.

Zikula Core 1.4.0 is intended as a transition release between the very popular 1.3.x series and Zikula Core 2.0.0. While maintaining nearly 100% backward-compatibility, 1.4.0 lays the foundations of Symfony, Doctrine, Bootstrap, Font-Awesome, jQuery and Twig which will be the basis of future development. A new namespaced module structure is established that will be the new standard for 2.0.0 extensions as well as providing many new tools and features to make your site exceptional.


JetBrains Supports Zikula

Contributed by craigh on Mar 18, 2015 - 07:58 AM
Picture 0 for JetBrains Supports Zikula

JetBrains has once again graciously offered their support for ongoing development of the Zikula project by donating licensing of their AWESOME php IDE PhpStorm.

JetBrains makes professional software development a more productive and enjoyable experience.

[They] help developers work faster by automating common, repetitive tasks to enable them to stay focused on code design and the big picture. [They] provide tools to explore and familiarize with code bases faster. [Their] products make it easy for you to take care of quality during all stages of development and spend less time on maintenance tasks.

PhpStorm features a rich and intelligent code editor for PHP that actually "gets" your code and deeply understands its structure, supporting PHP 5.3, 5.4, 5.5 & 5.6 for modern and legacy projects. The IDE provides smart code completion, syntax highlighting, extended code formatting configuration, on-the-fly error checking, code folding, supports language mixtures and more.

Licenses are available to core team members and last one year. If you are interested please contact Axel or Craig.

THANK YOU JETBRAINS!


Zikula Core 1.4.0-RC1 Released!

Contributed by craigh on Feb 21, 2015 - 03:10 AM
Picture 0 for Zikula Core 1.4.0-RC1 Released!

The day has finally come. Zikula Core 1.4 Release Candidate 1 is available as of today, 21 February, 2015.

Immediate testing is encouraged. You may download the RC from our Continuous Integration server. Release testing guidelines may be found in the Core wiki. Installation and upgrade documentation can be found in the /docs directory.

Our Quality Assurance cycle, explained also in the Core wiki, will be followed in order to achieve our General Release. Please register your vote on the promotion of this build in the promotion ticket.

Please report all bugs and concerns to our issue tracker on Github. Please understand that bugs will not necessarily halt the release of this build. Bugs may be fixed or postponed to another release.

Zikula Core 1.4.0 is intended as a transition release between the very popular 1.3.x series and Zikula Core 2.0.0. While maintaining nearly 100% backward-compatibility, 1.4.0 lays the foundations of Symfony, Doctrine, Bootstrap, Font-Awesome, jQuery and Twig which will be the basis of future development. A new namespaced module structure is established that will be the new standard for 2.0.0 extensions as well as providing many new tools and features to make your site exceptional.


Core Development and Roadmap Update

Contributed by guite on Dec 22, 2014 - 01:26 AM
Picture 0 for Core Development and Roadmap Update

Some of you may have seen that there is continuous activity in the Zikula core project at GitHub. This article gives you a brief update of what is happening and where we are heading to.


ModuleStudio 0.6.2 has been released

Contributed by guite on Aug 07, 2014 - 12:33 AM

We are happy to announce that a new version of ModuleStudio is available. ModuleStudio 0.6.2 includes many bugfixes as well as a few new features.

The primary focus of this release was increased usage of Symfony components for 1.4 applications. For example validation and routing are handled by the corresponding Symfony components now.


ModuleStudio 0.6.1 has been released

Contributed by Guite on Mar 13, 2014 - 12:06 AM

We are happy to announce that a new version of ModuleStudio is available. ModuleStudio 0.6.1 includes many bugfixes as well as a few new features.

The most important new function is the introduction of generator settings: herewith you can control which features are generated for a certain model. Also it is possible to take influence on different behavioural aspects of the generator.


MUNews is Available

Contributed by portugao on Mar 02, 2014 - 12:46 AM

MUNews gives a simple blog functionality, users can submit articles with.

In the backend one can moderate submitted articles. One can approve or reject articles.

MUNews was planned and created with the modulestudio; the fine-tuning it got by programming.


QA Testing for 1.3.7 Begun

Contributed by craigh on Feb 16, 2014 - 05:38 AM

Please consider helping with the Quality Assurance (QA) testing cycle of Core 1.3.7. Details of how you can help can be found in the Core ticket.

You can find the details of what has been updated in the 1.3.7 changelog.


Short development update

Contributed by craigh on Feb 15, 2014 - 04:36 AM

Core 1.3.6 was released on 7 November 2013 as a security patch for the 1.3.5 release which took place nearly a year earlier on 7 December 2012.

The main development was occurring in what was originally intended to be a minor release in the 1.3.x series but this has been taking too long. This has required a change in plans.

As of 15 February 2014 the following changes have been made in the Core repository
  • The 1.3 branch is renamed to 1.4
  • The release-1.3 branch is renamed to 1.3
  • The master branch remains intact as is and is intended as a 2.0 branch

The intention is to release Core 1.3.7 soon with all of the minor patches that have been floating out in the community as well as a couple other minor corrections. QA testing should begin on this release soon.

Core 1.4.0 will include many other improvements and fixes over 1.3.x series and also include a Forward Compatibility layer pointing toward the Core 2.0.0 release. There should be very few (if any) Backward Compatibility breaks from the 1.3.x series.

Core 2.0.0 will drop all backward compatibility for the 1.x series and require new extension structures, reliance on only new core technologies (symfony, twig, etc).

Timelines for anything beyond Core 1.3.7 are of course unknown and should not be assumed based on this information.


New web service for ModuleStudio launched

Contributed by Guite on Sep 03, 2013 - 04:50 AM

We are happy to offer you a new service which is going to even further simplify module development with ModuleStudio: "WebGen" is a web-based generator for ModuleStudio models. It results from the master thesis of our employee Michael Eckes.


ModuleStudio 0.6.0 has been released

Contributed by Guite on Mar 08, 2013 - 10:57 AM

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.


Composer dependency manager

Contributed by drak on Dec 24, 2012 - 11:01 AM

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


Git Repository Layout

Contributed by drak on Dec 17, 2012 - 02:56 AM

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

Done.

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.

Footnote:

Another other benefit is when a module is tagged it at Github, the archive will be auto-created with the right structure.


Changes to Module Branch, Tag and Versioning

Contributed by drak on Dec 17, 2012 - 02:35 AM

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

Zikula Core 1.3.5 released !

Contributed by espaan on Dec 07, 2012 - 10:26 AM

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:

  • The Mobile theme got several fixes
  • Fixes in DBUtil and FormUtil
  • Updates of jQuery (to 1.8.3) and jQueryUI (to 1.9.1)
  • Fixes in the site disabled screen
  • Added check for identical usernames in lowercase
  • Fixes in the advanced block placement
  • Javascript combine option now only uses local scripts
  • New alert dialog with auto-hiding
  • ...
Full details are available in the big closed ticket list for the 1.3.5 milestone.

Many thanks of course to the Zikula Core Development Team and Contributors and the users who reported these issues.

Enjoy it,

Zikula Team

Recent Forum Posts

Go to forum

Latest Comments