I’m starting to believe the best approach is just to re-write the block specifically for 5.7 rather than trying to modify the existing code.įive years ago when I first found Concrete5 I was so impressed with its intuitive dashboard and ease of use. Converting blocks can be very time consuming needing to track down the cause of errors created from the old code. Working with controllers and blocks has changed and with the lack of documentation it takes a lot of time experimenting to get things working. The good news for developers working with themes and view.php files, not a lot has changed, many of the ways you are use to doing things still work.
#ITHOUGHTSX 5.7 CODE#
I host a Concrete5 Cheat Sheet () I started by going through the Cheat Sheet and testing code snippets to see which ones worked with 5.7 and began correcting those that did not work to provide versions for both 5.6x and 5.7x.Īt this point I have experimented with themes, files, file sets, attributes, page types, embedded blocks, users and started converting a block to 5.7.
Over the weekend I spent about about 10 hours working with 5.7. I think under the hood some great work has been done introducing new technologies and improving the code base, in time it should be a very stable and robust platform. I’m not an advanced programmer, but I do have almost 5 years experience actively developing with Concrete5. Many people will be disappointed after reading on the download page that “The New version of Cocrete5 is here”, without documentation, add ons, limited community support and still being buggy, this should really be Concrete5.7 Beta 2.
0 kommentar(er)
