The most useful and flexible of all of concrete5's default block types is undoubtedly the Page List block.
We don't actually have to output lists of pages though, in this post I'm going to explain how to use it to output a Google Map of locations.
Concrete5 rss displayer not updating
Under 'Pages and & Themes', in 'Page Types' we should find a new page type called 'Blog Post' and, if we inspect it's defaults, you'll see the two blocks we installed.
In our Sitemap, we should have a new page called 'blog' which is accessible at the URL method.
In this part (Part 1) we'll deal with the package setup and package controller.
Packages are self contained pieces of functionality which can be installed into concrete5 websites.
In this tutorial I want to look at how we'd build a package, and, just for the sake of it, we'll make the package application a very simple blog, similar in almost all respects to the blog that get's installed with the default content.
It's a bit involved so I'm going to break it into a number of parts.In concrete5 5.7 PHP namespacing will be employed, but in 5.6.3 and below you generally have to namespace your code by naming in ways unlikely to cause conflicts.Let's name our package folder ' we keep version information.Naturally we've been creating custom page types, custom attributes and using the composer to manage such listings, this works great.On these sites what we wanted to do was create a Google Map with the property locations on it, being able to click through on the map to the property's page.Just because it's the Page List block, doesn't mean you actually have to _list_ pages on the output!