5.6.2.2 coming?
Permalink 1 user found helpful
I wonder if this has been discussed before..? The 5.7 WIP is gaining lot of attention and is being developed intesively but what about the few major (and many minor) bugs in 5.6.2.1, I mean will there be 5.6.2.2 to fix those bugs?
I'm pretty sure there are lots of developers/webmasters who are not willing to jump to 5.7.0 right away and sites that will not be 5.7 compatible without major changes in custom packages for example.
I'm pretty sure there are lots of developers/webmasters who are not willing to jump to 5.7.0 right away and sites that will not be 5.7 compatible without major changes in custom packages for example.
That's good to hear.
There are a few minor ones that are more like "nuisance", but would be nice to have fixed. Particularly these:
http://www.concrete5.org/developers/bugs/5-6-2-1/groups-removed-fro...
http://www.concrete5.org/developers/bugs/5-6-2-1/url-slug-suggestio...
http://www.concrete5.org/developers/bugs/5-6-2-1/composer-wont-publ...
However, if you look at the list of resolved ones, there are quite a few. If I understood correctly, these are fixed in Git, but not in the official version on download page until the next release?
There are a few minor ones that are more like "nuisance", but would be nice to have fixed. Particularly these:
http://www.concrete5.org/developers/bugs/5-6-2-1/groups-removed-fro...
http://www.concrete5.org/developers/bugs/5-6-2-1/url-slug-suggestio...
http://www.concrete5.org/developers/bugs/5-6-2-1/composer-wont-publ...
However, if you look at the list of resolved ones, there are quite a few. If I understood correctly, these are fixed in Git, but not in the official version on download page until the next release?
I am happily waiting for the page level control of block caching :)
I second this if this means that when you include individual blocks from stack to a template, the caching is not working correctly.
When including whole stacks, there is no problem but including individual blocks by name is not working correctly for example in AutoNav.
When including whole stacks, there is no problem but including individual blocks by name is not working correctly for example in AutoNav.
Since it will likely take some time until version 5.7 is ready for productive use, i might not be the only one how would LOVE to see yet another version 5.6.[..] with an improved stacks system (duplicate, copy from clipboard, sorting and grouping of stacks)!
What about the faulty propagation of area/block permissions from Page Type Defaults to pages?
http://www.concrete5.org/developers/bugs/5-6-2-1/block-permissions-...
http://www.concrete5.org/developers/bugs/5-6-2-1/block-permissions-...
At the moment nothing looks critical enough in 5.6.2.1 to justify shifting our energy over to a release on it.. perhaps I'm missing something tho...
http://www.concrete5.org/developers/bugs/5-6-2-1/?keywords=&dis...
Something in particular that's problematic?