Developers using Fork CMS are constantly looking on how to improve the cms. Ideas such as a marketplace for modules & themes have been on the roadmap for quite a while. The extensions page on the Fork CMS website has grown a lot and lacks several useful features. A revamped Fork CMS extensions app would certainly play a big part in the future of Fork CMS.
When you are writing code, creating advanced Fork CMS modules and themes, or adding new features, sometimes you break things. Fork CMS uses logs and can send you an email when an exception occurred, but for larger websites this isn’t that useful because you don’t know if you’ve seen that issue before, or if it’s been fixed in the past. Moreover, you don’t know the severity of the issue. Has it occurred once or is this error popping up every 10 seconds? In this article, we explore the use of error tracking software such as Rollbar.
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.
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.