Important: This website is now read only (except to admins) to comply with the UK Online Safety Act. Composr CMS is in the process of migrating to a new Constitutional governance model and Bazaar development model, with functionality of the old website (constructed by ocProducts Ltd, the prior copyright holder, a UK company) spread between GitLab and the new website (which has no connections to the UK).
Composr 10.0.3 released
This news article has not yet been validated by our staff, so we cannot accept responsibility for it. You followed a direct link to get to it.
Version 10.0.3 has now been released. This version is a patch release that introduces a number of bug fixes since the last release. Upgrading to this release is not necessary.
To upgrade follow the steps in your website's http://mybaseurl/upgrader.php script. You will need to copy the URL of the attached file (created via the form below) during step 3.
Your upgrade to version 10.0.3
You can generate an upgrader from any version of Composr to any other version. If you access this upgrade post via the version information box on your Admin Zone front page then we'll automatically know what version you're running.
If you'd prefer though you can enter in your version number right here:
This fixes an issue in the Setup Wizard introduced in 10.0.2 that affects a proportion of users, as well as some very minor fixes to the upgrader code.
I agree that having release notes, especially when functionality is changing in some way, would be a help.
Unfortunately we just don't have the resources to do that right now. I have to dive in and make fixes very quickly, and I don't have the time to really document each individual fix. It wouldn't take me that long to do (maybe 10% longer), but it's still time I don't have unfortunately.
If we had more volunteer developers doing bug fixes, or more support on my Patreon, more time could be dedicated to it in the future. I expect this will be the case at some point.
Anything people can do to help us grow our community is very welcome . If things aren't depending on me, or I am able to dedicate more time to pure development rather than client work, we can do a smoother job. Until then I'd recommend people who are more nervous about updates have their own test sites to trial updates on.
I think like most upgrades performed by other applications.... maybe listing off the changes made or what has been updated would be helpful. Since you state that you can read what has been updated but nothing shows but that an update has been released. Kind of makes me feel like this is just a small patch with no info. Just pointing this out....
This would be useful, but you can see what's been fixed by looking at the bug tracker and other changes in the git commits. The other applications you're thinking of probably have much larger teams.
Yeah, it's a lack of resources to be honest. Trust me, a lot of things get fixed constantly . It's such a huge system with a lot of permutations of configuration, maybe 6 bug fixes per day at the moment.
"I" understand that... but that is us. I am thinking noob and how they see this. I know where to find the info but if you look at how and what these pages are stating it does look like you can view this info from here.
Edited
Comments
I agree that having release notes, especially when functionality is changing in some way, would be a help.
Unfortunately we just don't have the resources to do that right now. I have to dive in and make fixes very quickly, and I don't have the time to really document each individual fix. It wouldn't take me that long to do (maybe 10% longer), but it's still time I don't have unfortunately.
If we had more volunteer developers doing bug fixes, or more support on my Patreon, more time could be dedicated to it in the future. I expect this will be the case at some point.
Anything people can do to help us grow our community is very welcome