Elements 1.6.0 (23973)

Hi @ben

it’s true Load More won’t work



Thanks for the hint.

No idea how I could have overlooked that … of course it doesn’t make any sense like this ;-/

Ben has already mentioned in the past that the “load more” and “pagination” components do not work together. So you should use either “load more” or “pagination”.

That makes sense to me.

Correct, I have just added this to the manual on both Pagination and Load More pages.

The Collection Pagination and Load More components cannot be used together. They both control how items are fetched and displayed within a Collection, so enabling both at the same time will cause conflicts. Choose Pagination if you want clear page-based navigation, or Load More if you prefer a progressive, infinite-style experience.

Thanks for the hint.

The reason why the pagination is still there is because of the different sizes in the pagination icons. So @dan and @ben could see if this very small bug has fixed. :slight_smile:

The Load More functionality has nothing to do with pagination. (I have removed the pagination, Load More still not working!) If you load more the pagination won’t update but this site is only my playground, not business relevant.

Your server is returning a "“Template error: Template syntax error on line 21: Unknown “format_datetime” filter in “template” at line 21.”

Which looks like a possible Twig error. Do you know if you’re using the format_datetime filter elsewhere on the site?

Could you send me the project so I can easily test it locally :slight_smile:

If i press Mehr…

image

cms.log
[2025-12-15T14:42:02.583963+01:00] cms.WARNING: Collection directory does not exist {"path":"C:\\inetpub\\cornrow.de\\rw\\elements\\com.realmac.corepack\\api/cms/aktuelles"} []

Preview also don’t work.

format_datetime
.../Page Data/ > grep -rH "format_datetime" * | cut -d: -f1 | sort | uniq -c
  1 236E1171-5C87-4839-9C14-0E7A4760DF0A.json
  1 777A9E39-BC26-428A-A302-6A0AD26B09A6.json

I’ll send the project link via mail.

@ben I have not changed hosts. I do use Chillidog, so I’m wondering if this has anything to do with the hardening they recently performed to counter the attack they experienced.

The only thing that changed on the server was my password.

And yes, the Load More was working correctly before. Although, to be honest, I had not checked this page after the incident.

Should I be reaching out to Chillidog?

@handshaper Could you please look into your cms.log?

This is odd, the path here is wrong. It’s looking for the cms/aktuelles folder inside the shared assets path, it should be looking for it in the web root of your server.

I’ll need to investigate why the path is incorrect. I’ll get back to you as soon as I’ve figured out the issue!

@Ulrich I have found the issue with the following error:

Template error: Template syntax error on line 21: Unknown “format_datetime” filter in “template” at line 21.

That has now been fixed and will be included in the next Elements update. It was a Twig configuration issues that wasn’t allowing the format_datetime filter to be used.

If you need the Load More to work before the next Elements update, you’d have to stop using that filter until then.

Hi @ben thank you very much.

The CORNROW site is my playground; I put everything I need there to learn and understand. :slight_smile:

How did you find the error? Could I have found it too? I always want to provide a perfect and comprehensive error description so I don’t send you down the wrong path. Is it a PHP error message? Then maybe I should display the error messages in the HTML?

I inspected the request in the browser dev tools. I updated the error responses a while back so that they now contain a more descriptive error, and in this case the response was:

{
    "success": false,
    "error": "Template error: Template syntax error on line 21: Unknown \"format_datetime\" filter in \"template\" at line 21.",
    "timestamp": "2025-12-16T09:02:35+00:00"
}

OK, I think I’ve found the issue and it’s essentially the same issue as one we had with the forms a couple of weeks ago.

Again, this seems to be an issue with Chillidog hosted sites due to the security settings they now have. I’ll need to do some work on our end to provide full compatibility with Chillidog hosted sites and the Load More component.

I’ll get this update done ASAP, although it’s not going to make it in to the next release it will hopefully be in the one after! :slight_smile:

@Ulrich Remind me where to find this log?

logs are in /rw/elements/com.realmac.corepack/api/logs

Did you know the Log-Manager? Try https://yourdomain.tld/rw/elements/com.realmac.corepack/api/log-manager.php

Fixed in 1.6.1

Thanks

Aaaah.

@ben Please could you have a look at

In preview the Load More Butten Mehr... works, but not on my site after i published all files.

Btw: To see now what i have changed in the components is the best new feature in this year.

I had forgotten about the Log Manager, thanks.