after upgrading to 3.6.2 the pagination isn’t working as expected anymore. I followed the cookbook Load more with Ajax | Kirby CMS which went perfectly well in 3.5.7.1.
After upgrading to 3.6.2 the same requests show The requested resource /topicworlds/schulleben.json/page:1 was not found on this server.Any idea where to start debugging?
ok, good to know, that it’s not just me running into trouble … any idea how to move forward? Are you going to investigate things further? Can i help? How?
Are you using PHP to serve the files or built-in Apache? In either case I believe json isn’t recognized as type json and therefore causing the issue. In case of Apache you can use htaccess file to serve the correct MIME type.
I am using plain PHP (starting local kirby with php -S localhost:8090 kirby/router.php).
But something must have changed in kirby from 3.5.7 to 3.6.2 as downgrading makes the whole thing work without changing anything else (except the version in composer.json and issuing composer update).
Then it’d be probably helpful to know when exactly the change was introduced — would you be able to check latest 3.5 version and 3.6.0? Anyway, it’s probably something the dev team knows more about.
I haven’t been able to look into this yet. Maybe create an issue on GitHub, seems to be an issue only related to the built-in server. Cannot reproduce with Valet or MAMP.
Hi @texnixe, any chance you have looked into this further since your last response? I’d really like to implement it on a project I’m working on. (I am using 3.6.2) Thanks
Thanks for your reply! I’ve just tried with 3.6.6, unfortunately still not working. I’ve reverted back to 3.6.0 and it’s all back so I’ll stick with that for now.
In an old Kirby 1/2 project, i was working on, the pagination sign was : , recently was working on Kirby 3.6 project and realized that the pagination sign changed to ;
[Web Server ] Jun 2 12:31:12 |WARN | SERVER GET (404) /news/page:2
[Web Server ] Jun 2 12:31:20 |INFO | SERVER GET (200) /news/page;2
Maybe that’s the issue. You have hardcoded links referring to the page:2 instead of page;2.