These are chat archives for locomotivecms/v3

25th
Apr 2017
Martin Berggren
@marthings
Apr 25 07:10
Is there any repo thats not private with a larger example loco site? Maybe someone has some cool starter templates / sites they want to share for some inspiration :)? I would love to see an example of the actions api, dunno why but cant figure out when or why i should use the actions api instead of liquid.
Manu
@manuchap
Apr 25 13:18
Here's a quick example: https://github.com/manuchap/loco_templates/tree/update_entry_action. For me the main interest is it allows to modify entries from the frontend (to logged in users for example).
I made a bootstrap 4 template if you want :https://github.com/manuchap/webagency
Manu
@manuchap
Apr 25 13:26
And a basic bookings site with a pretty cool soundcloud player :-) https://github.com/manuchap/Agendastudio
Miha
@dotsi
Apr 25 22:49
I found the confirmation that it is the expected behaviour that all page caches expire when anything within the site is modified: locomotivecms/engine#905
For me this does not make much sense since the bigger more complex websites need caching the most and are also edited the most frequently.
An example: A travel website has many destinations and hundreds of travel packages. All pages list many different content types. Server response time without caching is 2-4 seconds. With caching it is 5-30ms. As soon as a single price is changed in one content entry, hundreds of page caches are lost and every single url needs to be visited again to rebuild the cache.
Since the website is edited a few times daily and most of the pages don't even get views every day the cache only kind-of works for the home page and the top level pages. Other pages are always "on the first load".
I understand that there must be impossible to know what resources a developer loads in a page liquid template so expiring all pages is the best bet. But in this form it also isn't very useful beyond caching simple sites that don't change very often.
Any ideas on how to make caching better?