v11 alpha may be coming to bleeding edge releases soon
Should v11 alpha be released as a bleeding edge release?
| Yes, release v11 as bleeding edge in alpha |
  
[6 votes]
|
| No, don't release v11 as bleeding edge until it reaches beta |
[0 votes]
|
Standard member
Patrick Schmalstig said
As a heads-up, a lot of changes (mostly behind the scenes) will occur between 11 alpha2 and 11 alpha3. Some extra considerations may need to be made if you're running a v11 site:
* The names of the fast custom index options have changed. So you will need to set these settings again as they will probably revert to defaults after upgrading to alpha3 (once released). The _fulltext_index tables however should continue to work.
* The format of errorlog.php has changed to include a log level. This will be parsed on the error log UI in the Admin Zone, and each entry will be coloured according to the log level. (Old) records without a log level will default to WARNING.
* A lot of changes behind the scenes are being made to the code to better support rebranding. I'm changing many hard-coded references to Composr or its sites to use generic terminology or get_brand_base_url() / brand_name() functions. Every file will still contain at minimum "Composr" at the top of the copyright comment. A few hard-coded Composr references which would be too detrimental or breaking to change will remain.Once I get the upgrader for v10 to v11 working, it will properly transfer over the values of said config options when upgrading a v10 site to v11.
- This largely will not affect actual operation of the software. However, a few config options which had the word composr in them might be renamed (causing them to revert to default when upgrading to alpha3). And I'm still debating whether or not to rename a few non-bundled addons which contain composr in the name (especially composr_homesite, composr_homesite_support_credits, and composr_release_build).
From “Post #9,873”, 25th April 2024, 1:18 am
Patrick Schmalstig
thanks very much for your work. And thank you for keeping us up to date on the implications and impact of alpha/beta upgrades/updates.
Site director
Please see DOS loop attack vulnerability patched - Composr CMS: Content management meets social media for more information and a very quick fix.
The fix will be included in alpha3, which is still several days away at least (normally a patch would come out immediately for security issues, but given this is still in alpha, I'm not treating this as seriously since I've recommended many times not to run v11 in production unless you're aware of the implications).
This issue does NOT affect v10.
- Need support for version 10? The core development team is no-longer offering it for free (unless it's a critical bug that breaks your entire site or a serious security hole). Please consider hiring me instead if you need v10 support or a non-critical bug fix. Or, ask the community in the forums!
- Do you enjoy Composr? Please consider contributing your talent to the project or recommending Composr to others. Even small contributions make a big impact in the Composr community.
- Do you have feedback for us? You can report bugs, suggest features, or give feedback on the Free support options page.
- Do you need professional service with your Composr website? Please consider contracting me for your needs through my company, PDStig, LLC. Doing so will also help fund Composr development.
- Want to watch live streams of me developing Composr CMS? Please subscribe to me on Twitch to be notified when I stream. Composr development streams are usually spontaneous / not scheduled in advance as work priorities come first.
1 guest and 0 members have just viewed this.