People following the development of Fork CMS probably noticed that we recently introduced a new Analytics module. We started from scratch to be able to use all the most recent Fork Features in this module.
This blog post will go trough the most notable changes with the new module.
Today we released Fork 3.9.5, check out the changelog. You can also follow Fork on github.
Today we released Fork 3.9.4, check out the changelog. You can also follow Fork on github.
Symfony's Event Dispatcher has been around in Fork CMS for some time now, but is only recently being integrated in our modules. It's not hard to use it though, and it's a great tool to decouple code in your modules. This post will explain in small steps how you can use it in your own Fork CMS modules.
Since Fork CMS version 3.9.2, our Fork modules look a little more like Symfony Bundles. They can now contain a so called "module extension" class that can be used to load module specific configuration or services.
This blogpost explains how you can start using this "module extensions" to write cleaner decoupled code in Fork CMS.
Today we released Fork 3.9.3, check out the changelog. You can also follow Fork on github.
Today we released Fork 3.9.2, check out the changelog. You can also follow Fork on github.
You may have noticed that we cleaned up the labels we use for issues/pull requests on GitHub. We now follow the same structure as the Symfony repository.
Today we released Fork 3.9.1, check out the changelog. You can also follow Fork on github.
Since our 3.9 release, all mail communication runs through the Swiftmailerbundle. This is the officially supported way of sending mails through Symfony. It's based on the widely used and well documented library Swiftmailer.