Paging link rewrite not picking up section token/slug

marc · Nov 5th 2019

Hi all

Got a blog setup on Runway which uses sections. Standard index page setup which either displays posts for a section or all.

Can't seem to get the paging to rewrite the section. The link generated just seems to output the next page number without the rewritten section.

Expected url

/en/news/section/events/2/

Current url

/en/news/section/2/

Would it make any difference to have a section.php master page instead of using a conditional?

Routes setup on page

en/news/section/[slug:section]/[i:page]

en/news/section/[slug:section]

en/news/[i:page]

blog/index.php

PHP

<?php
$slug = perch_get('section');
if ($slug) {
perch_blog_custom([
'data' => [
'section' => $slug,
],
'template' => 'blog-grid.html',
'count' => 9,
'sort' => 'postDateTime',
'sort-order' => 'DESC',
'blog' => $vars['lang'],
'section' => $slug,
]);
} else {
perch_blog_custom([
'template' => 'blog-grid.html',
'count' => 9,
'sort' => 'postDateTime',
'sort-order' => 'DESC',
'blog' => $vars['lang'],
]);
}
?>

Display More

blog-grid.html

HTML

<perch:after>
</div>
<perch:if exists="paging">
<div class="row ta-c">
<div class="col-12 ta-c eq-margin">
<div class="h3">
<perch:trans id="lang.global.paging.page" /> <perch:blog id="current_page" /> <perch:trans id="lang.global.paging.of" /> <perch:blog id="number_of_pages" />
</div>
<perch:if exists="not_first_page">
<a class="btn btn--skew btn--fill" href="<perch:blog id="perch_page_path" />/<perch:blog id="prev_url" encode="false" rewrite="{section:/section/%s/}{page:%s/}" />"><span><perch:trans id="lang.global.prev" /></span></a>
<perch:else />
<span class="btn btn--skew btn--disabled"><span><perch:trans id="lang.global.prev" /></span></span>
</perch:if>
<perch:if exists="not_last_page">
<a class="btn btn--skew btn--fill" href="<perch:blog id="perch_page_path" />/<perch:blog id="next_url" encode="false" rewrite="{section:/section/%s/}{page:%s/}" />"><span><span><perch:trans id="lang.global.next" /></span></a>
<perch:else />
<span class="btn btn--skew btn--disabled"><span><span><perch:trans id="lang.global.next" /></span></span>
</perch:if>
</div>
</div>
</perch:if>
</perch:after>

Display More

marc · Nov 5th 2019

If I manually navigate to /en/news/section/events/2/ the correct blog posts display.

The debug has the following:

Code

Matched route: en/news/section/[slug:section]/[i:page]
Using master page: /templates/pages/news/index.php
Page arguments:
Array
(
[0] => /en/news/section/events/2
[section] => events
[1] => events
[page] => 2
[2] => 2
)

Display More

hus_hmd · Nov 6th 2019

I ran into this issue yesterday myself. I'm sure I came across it in the past too. I often end up just using URL query string ?page=. So hopefully drewm will address this in v4 at least!

Thinking about it now, you probably can use Perch conditional tags as the named segments you use in URL patterns are available to you (prefixed with url_)

HTML

<perch:if exists="url_section">section/<perch:blog id="url_section">/</perch:if>

marc · Nov 6th 2019

It's one of those things that i'm pretty sure I have come across in the past before with runway and rewriting. Although I think it was a similar scenario with collections instead of the blog app.

I think in the past I have passed in the cat/section slug into the function using data similar to below and built the url up, but it's good to know that the url tokens are available to use.

Thanks for the clarification hus_hmd

HTML

<perch:if exists="paging">
<div class="pagination">
<perch:if exists="not_last_page">
<perch:if exists="cat">
<a href="/journal/category/<perch:content id="cat" type="hidden" />/<perch:content id="next_url" type="hidden" encode="false" rewrite="{page:%s/}" />" class="load-more button button--primary button--l" role="button">Show more</a>
<perch:else />
<a href="/journal/<perch:content id="next_url" type="hidden" encode="false" rewrite="{page:%s/}" />" class="load-more button button--primary button--l" role="button">Show more</a>
</perch:if>
</div>
</perch:if>