We are migrating from an old concrete 5 site to 9.4.8. We installed and were creating the site with the Enlil page list block, which we really like the flexibility for display options and filtering. But once we migrated over our hundreds of pages from the old site, any page that contains that block loads extremely slow: 4-10 seconds. I’ve added all kinds of caching to the pages, the site and the block itself. This does help (except when cache is cleared obviously), but since the block is cached, the topic filter and the paging no longer work. I installed the basic atomik page list block to see if it would be good enough and the page loads so much faster - BUT, when I change the block template to Blog Entry Grid, the pages that were migrated over do not display (though the number of pages makes it seem that they are there). They all show in the default block template. I did notice that if I edit a page and re-publish it then it appears, but I can not go through hundreds of pages and do this one by one.
Can someone please give us some suggestions to either speed up the Enlil page list block or get the atomik one to function? Thanks!
Have you contacted the developer of the Enlil Page List? It says it’s compatible with Concrete CMS 8.5.2+ so it doesn’t specifically mention Version 9. Yes, the ‘+’ sign implies that it is but I like to see addons that have been specifically updated for version 9.
https://geneticoncrete.com/members/profile/1/
There’s a ‘Connect’ button you can try.
Yes, I have reached out a couple times but haven’t heard back. He gave me his email when I was initially having issues installing it so I used that (couldn’t use the connect button you suggested - it requires a login). It was working great until we went from 10 test pages to hundreds of migrated pages.
Humm… interesting that you say “if I edit a page and re-publish it then it appears”. There is POTENTIALLY a way to ‘rebuild’ all the pages without doing each one individually. Head to Dashboard → Pages and Themes → Page Types and click “Output” on the page type you’re using for these troublesome pages. Then add a useless block to an area such as an empty HTML block (add the HTML block but leave the contents blank). Before saving anything or exiting, click on the empty HTML block you just added and choose ‘Setup on child pages’. That should add that empty HTML block to all those pages and, hopefully, trigger a page rebuild but it’s hard to know if this will work the same as editing the page ‘for real’ but it’s worth a try.
Thanks for the idea, I gave it a try but after it pushed the new block to all 1000 pages, still only the ones that had been manually edited are showing in both the blog entry and resource list template. And all the pages show up fine with the default or basic list templates.
In the dashboard, try running the search index task to rebuild the site search index (Updating the search index entry for a page is a side effect of editing a page).
AArgh!! I’m able to take a look into what is going on here. It’s been a couple years, and without having looked, it’s likely the way I’m grabbing the pages for the block. In order to create some of the edge case lists that the block can, I start by grabbing all the available pages in the site. I’ll be taking a dive in and seeing what can be done to only load pages this way if we’re asking for one of the edge case scenarios! @karilynae I have read your emails and will be getting back to you!
Great suggestion! This worked for getting the pages to display in the Atomik block with the grid entry template. Thanks!
Thanks for looking into this!