Wolf CMS

Users of Wolf CMS 0.7.5 are advised to patch their systems with the SP1 (Security Patch) patch. You can get the patch from the download page Risk level – Moderate. Description – A number of CSRF vulnerabilities were reported and fixed which ... [More] could allow a remote attacker to abuse certain Wolf CMS functions by manipulating the URL. Exploiting these vulnerabilities depend on the attacker first acquiring a valid session from a user with administrative privileges. Note – Some users might encounter a message “This plugin CANNOT be enabled! It requires Wolf version 0.7.5.” with some third party plugins for 0.7.5-SP1. If you encounter this message, please change the CMS_VERSION variable in index.php back to “0.7.5”. — Martijn [Less]

Users of Wolf CMS 0.7.5 are advised to patch their systems with the SP1 (Security Patch) patch. You can get the patch from the download page Risk level – Moderate. Description – A number of CSRF vulnerabilities were reported and fixed which ... [More] could allow a remote attacker to abuse certain Wolf CMS functions by manipulating the URL. Exploiting these vulnerabilities depend on the attacker first acquiring a valid session from a user with administrative privileges. Note – Some users might encounter a message “This plugin CANNOT be enabled! It requires Wolf version 0.7.5.” with some third party plugins for 0.7.5-SP1. If you encounter this message, please change the CMS_VERSION variable in index.php back to “0.7.5”. — Martijn [Less]

As the next release of Wolf CMS is approaching and we are planning to create a release candidate soon, I thought it was time to explain the new development strategy we will be following as a project after the next release. Rolling releases There ... [More] are many styles of development in this world and so far, Wolf CMS has been using an “its done when its done” approach. Starting with the next stable release of Wolf CMS, we will be adopting a so-called ‘rolling release’ system. For those of you who are not familiar with this system, this will mean that the latest and greatest version of our ‘master’ branch in the git source code repository will also be the latest stable version at all times. As soon as a feature has been tested and deemed stable enough for production use, it will be merged into the ‘master’ branch. The same will apply to bugfixes. As soon as a bugfix has been tested and approved, it will be merged into the ‘master’ branch. This new strategy will mean that features and bugfixes will become available much sooner that has been the case so far. Git strategies and contributors The development of Wolf CMS will continue to happen using git for source control. Details are listed below with the key rules that Wolf CMS will be following for its development on Github. The ‘master’ branch will maintain a stable branch policy All new features will always be merged through branches Each change of the code in the ‘master’ branch will also change the version number All Pull Requests must be made against the ‘staging’ branch, and no requests against the ‘master’ branch will be accepted In essence this means that all contributors will have to send Pull Requests for the ‘staging’ branch in the future. Version numbering With this change in development strategy, Wolf CMS will also be changing its version numbers. At the moment Wolf CMS uses the classical version numbering scheme of major.minor.patch. Starting with the new rolling releases, Wolf CMS version numbers will consist of only two parts: major and patch/build. In essence, the major number is just a general indication of backwards compatibility. If the major version number changes, the most likely reason is either a huge change in the system or a change in the database layout. The patch or build number will increase by one with every addition of a new feature or a bug fix in the ‘master’ branch. For example, by comparing version number “8.121” with “8.125”, you know there have been four new features and / or bug fixes in the system. For the complete details, please see the wiki page on version numbers. What’s next? In the next few days we will be doing some updates on the website with regards to documentation and the wiki. Apart from that we’ll be completely focused on preparing for the first release candidate of what will be Wolf CMS 1.0 (previously 0.8.0) which will be the first release using the new version numbering scheme. We will also be doing more posts on a variety of subjects. If you are interested in a particular topic, feel free to post your ideas / requests in the relevant forum topic. — Martijn, founder and lead developer [Less]

As the next release of Wolf CMS is approaching and we are planning to create a release candidate soon, I thought it was time to explain the new development strategy we will be following as a project after the next release. Rolling releases There ... [More] are many styles of development in this world and so far, Wolf CMS has been using an “its done when its done” approach. Starting with the next stable release of Wolf CMS, we will be adopting a so-called ‘rolling release’ system. For those of you who are not familiar with this system, this will mean that the latest and greatest version of our ‘master’ branch in the git source code repository will also be the latest stable version at all times. As soon as a feature has been tested and deemed stable enough for production use, it will be merged into the ‘master’ branch. The same will apply to bugfixes. As soon as a bugfix has been tested and approved, it will be merged into the ‘master’ branch. This new strategy will mean that features and bugfixes will become available much sooner that has been the case so far. Git strategies and contributors The development of Wolf CMS will continue to happen using git for source control. Details are listed below with the key rules that Wolf CMS will be following for its development on Github. The ‘master’ branch will maintain a stable branch policy All new features will always be merged through branches Each change of the code in the ‘master’ branch will also change the version number All Pull Requests must be made against the ‘staging’ branch, and no requests against the ‘master’ branch will be accepted In essence this means that all contributors will have to send Pull Requests for the ‘staging’ branch in the future. Version numbering With this change in development strategy, Wolf CMS will also be changing its version numbers. At the moment Wolf CMS uses the classical version numbering scheme of major.minor.patch. Starting with the new rolling releases, Wolf CMS version numbers will consist of only two parts: major and patch/build. In essence, the major number is just a general indication of backwards compatibility. If the major version number changes, the most likely reason is either a huge change in the system or a change in the database layout. The patch or build number will increase by one with every addition of a new feature or a bug fix in the ‘master’ branch. For example, by comparing version number “8.121” with “8.125”, you know there have been four new features and / or bug fixes in the system. For the complete details, please see the wiki page on version numbers. What’s next? In the next few days we will be doing some updates on the website with regards to documentation and the wiki. Apart from that we’ll be completely focused on preparing for the first release candidate of what will be Wolf CMS 1.0 (previously 0.8.0) which will be the first release using the new version numbering scheme. We will also be doing more posts on a variety of subjects. If you are interested in a particular topic, feel free to post your ideas / requests in the relevant forum topic. — Martijn, founder and lead developer [Less]

Two new features were added to the plugin repository. The first feature is the ability to display a list of all rated plugins sorted by the number of votes they got and then by the average total rating. You can access the feature by going to the ... [More] plugin repository and clicking on the small “star icon” in the top left. See the screenshot… The second feature is mainly of interest for plugin maintainers/developers. You were already able to add new plugins or edit existing releases of a plugin. It is now possible to add a plugin release. A plugin release is essentially a specific version of the plugin released on a specific date. By adding releases to the repository for each version, your users will be able to download older releases if desired for some reason. This feature was still missing from the repository as new releases had to be created by wolfcms.org administrators up till now. — Martijn [Less]

Two new features were added to the plugin repository. The first feature is the ability to display a list of all rated plugins sorted by the number of votes they got and then by the average total rating. You can access the feature by going to the ... [More] plugin repository and clicking on the small “star icon” in the top left. See the screenshot… The second feature is mainly of interest for plugin maintainers/developers. You were already able to add new plugins or edit existing releases of a plugin. It is now possible to add a plugin release. A plugin release is essentially a specific version of the plugin released on a specific date. By adding releases to the repository for each version, your users will be able to download older releases if desired for some reason. This feature was still missing from the repository as new releases had to be created by wolfcms.org administrators up till now. — Martijn [Less]

As this year is coming to an end, we would like to get your feedback on overall experience and performance of Wolf CMS. Please take 5-10 minutes to answer this survey (9 questions only), it will help us a lot in our future plans. The survey ... [More] will be open until the end of the December and afterwards we will make a short blog presentation from the results. — Dejan Edit: Closed! [Less]

As this year is coming to an end, we would like to get your feedback on overall experience and performance of Wolf CMS. Please take 5-10 minutes to answer this survey (9 questions only), it will help us a lot in our future plans. Wolf CMS annual ... [More] survey The survey will be open until the end of the December and afterwards we will make a short blog presentation from the results. — Dejan [Less]

As this year is coming to an end, we would like to get your feedback on overall experience and performance of Wolf CMS. Please take 5-10 minutes to answer this survey (9 questions only), it will help us a lot in our future plans. The survey will ... [More] be open until the end of the December and afterwards we will make a short blog presentation from the results. — Dejan Edit: Closed! [Less]

We know that we have been very quiet and that the last WolfCMS was out 6 months ago, but hey, we are only humans and the Summer was very hot and we got a bit lazy … And you are probably wondering what is the reason for such a long delay ( beside ... [More] Summer ) and when will the new version be available!? Well, hopefully soon… (akhm) as we are very busy with new admin interface and other less visible improvements. So without further ado, I present you the new WolfCMS admin UI: — Dejan [Less]