Problem upgrading an old bolt 3.7

[levincem]

Hi,

I'm currently upgrading some old bolt 3.7 websites and i have an issue, i don't understand.
In my template, i've got this line

{% setcontent pages = 'articles' where { categories: 'Droit immobilier' } %}

Which seems correct according to the 5.1 docs ?
But bolt give me this error for this line

An exception has been thrown during the rendering of a template ("").

I don't understand what's wrong here ? I thought of the space in the category name ? but it was made like that and i can't change it now, or it will break the links between articles and categories ?

Thanks for your advices

[bobvandevijver]

There probably is a previous exception which has some more details on what is actually going wrong.

[levincem]

Actually i didn't saw, but below i've got this one too

Pagerfanta\Exception\ LessThan1CurrentPageException

I don't know where it comes from either ?

Are spaces ok in the categories in Bolt 5 ?

[bobvandevijver]

Not sure, but I would expect it to work with spaces.

It seems that something is calling the pager incorrectly, for example a zero value: https://www.babdev.com/open-source/packages/pagerfanta/docs/2.x/usage. This might be something in your own template, can't really tell.

[levincem]

Ok, i've made a dump of a setcontent request, like

{% setcontent actus = 'articles' latest limit 3 %}

it returns a PagerFanta object, so it seems normal.

I've checked and i've got an "articles" content type, the categories shows in the right column in the admin and when i click "Droit Immobilier", i've got results. so in the admin, everything seems OK.

I've tried removing everything from this template except this line

{% setcontent pages = 'articles' where { categories: 'Droit immobilier' } %}

And i still got the two exceptions

[LessThan1CurrentPageException]
An exception has been thrown during the rendering of a template ("").
Pagerfanta\Exception\ LessThan1CurrentPageException 

I've also tried to setcontent with a category with no spaces in it, and the same error happens.

I really have no clues but i have to find a way to get back the articles linked to a category.

[levincem]

i've tested all the way, but it's really this line that raises the two exceptions

{% setcontent pages = 'articles' where { categories: 'Droit immobilier' } %}

It calls pagerFanta, behind the scenes and my request SHOULD return results.. Why is it working in the admin area and not in the public one ?

[levincem]

ok, made a walkthru with chatgpt, in case it can help..
Checked taxonomies, checked the DB, made a direct controller to check if the articles where accessible

        $articles = $contentRepository->findBy(['contentType' => 'articles'], null, 5);
        //var_dump($articles);
        return $this->render('test.html.twig', [
			'articles' => $articles,
		]);

Everything seems fine, but

{% setcontent pages = "pages/latest/5" %} or {% setcontent pages = "articles/latest/5" %} gives just NULL whenever the articles / pages are in the DB.

[levincem]

ok i found the source of the problem, i think..
i've got an index.twig, with setcontent working fine.

the page called here is a template which is not linked to any content in the DB. So in my routing.yml, i've got

page:
    path: /page/{page}
    defaults:
        _controller: Bolt\Controller\Frontend\TemplateController::template
        templateName: /pages/default.twig

this because we had to keep old urls for SEO, and we used this in bolt 3.7 like this

page:
    path: /page/{page}
    defaults:
        _controller: controller.frontend:template
        template: /pages/default.twig

I think that's the issue here.. But i don't see how to correct that !

This works in my index.twig :

{% setcontent pages = 'articles' where { categories: 'Droit de la famille' } %}
{{dump(pages)}}

but not in the "page" defined in my routing

[levincem]

ok, it was the routing part the issue.

now with this

oldpages: path: /page/{slugOrId} defaults: _controller: Bolt\Controller\Frontend\TemplateController::template templateName: /pages/default.twig

and this in the template

{% setcontent pages = 'articles' where { categories: 'droit-immobilier' } %}

no more errors, and results found !

Not sure to understand why it was not working before, as my routing config was really.. close ? identical ? and i had tried the slug instead of the name before.. but.. Anyway, happy