andrew
January 18, 2022, 11:44pm
1
We wanted to do something we don’t do very often – give you a heads up about an upcoming release!
We’re happy to announce that Concrete CMS 9.0.2 is scheduled for release next Monday. This release has many bug fixes, improvements to localization under version 9, and many other minor improvements.
If you have any pull requests for minor items that you’ve been sitting on that are ready, now would be a good time to open them up. Can’t promise they’ll make it into 9.0.2 but I’m actively reviewing a number of still open items.
5 Likes
Thanks for the updated Andrew. I think I’m going to wait till 9.2 to build out new sites with V9. That way most major bug fixes should be found.
@andrew here’s one I just posted.
opened 07:16PM - 20 Jan 22 UTC
This one was found totally by accident thanks to Jack Vanson.
If you enable a… dvanced permissions and use a container that wraps its areas in a list and list items <li> the area edit menu is broken.
If advanced permissions are not enabled or the areas are wrapped in DIVs there is no problem.
Screenshots below. Full explanation and fix in the PR I'll be pushing in a few minutes.
![area-menu-error](https://user-images.githubusercontent.com/1488833/150406551-146fb20f-b7fe-4251-858a-40421d523943.png)
![area-menu-error2](https://user-images.githubusercontent.com/1488833/150406613-5a0bf289-85f6-436d-ba4a-44588c4061b1.png)
And here’s the fix
concrete5:develop
← mnakalay:fix-area-edit-menu
opened 07:21PM - 20 Jan 22 UTC
As explained in #10257 the area edit menu is broken when advanced permissions ar… e enabled and the areas are wrapped in a list and list items <li>
When advanced permissions are enabled the permissions item appears in the area edit menu. That's the culprit so without advanced permissions we can't see the problem.
The divider just before the permissions item in the menu is wrapped in a left-over <li></li> that doesn't belong to any <ul></ul> so when it ends up inside a list it breaks it.
Removing the extra <li></li> fixes the problem. Screenshots below. The third one shows the menu fixed.
![area-menu-error](https://user-images.githubusercontent.com/1488833/150407632-f4245ff9-dfed-45b8-aed4-1aa3d9ce4dec.png)
![area-menu-error2](https://user-images.githubusercontent.com/1488833/150407669-2ee9cd27-9ff0-49c6-a0e5-45c3f1ea09d3.png)
![area-menu-fix](https://user-images.githubusercontent.com/1488833/150407692-8e4a1572-6eca-4ff9-9afe-6ca92fd592af.png)
I’m double posting it here since time seems to be of the essence.