Include third party code libraries and other assets in a concrete5 package.
A quick refresher on building URLs for tools files in blocks, packages and the root /tools directory.
Get ecommerce product name and description within a custom block on product_detail page types.
During package installation, check prerequisites and prevent installation if prerequisites are not met.
If you run multiple different concrete5 sites on a same Apache server, do you want to save the disk space? Here is how to.
If you need to change the name/url of a parent page, all old child page urls will automatically redirect to the new parent page url. This shows you how to easily get around this problem by adding a single line of code to your .htaccess file.
Now that you know how to prepare your add-on's backend code for 5.7, let's delve into the user facing stuff.
Enough is changing in concrete5 5.7 that add-on developers will have to go through a little bit of work to make their add-ons work with the new code. It'll be worth it, and this guide will help you get started.