TYPO3 Core

Imho the patch of https://review.typo3.org/51376 does not contain any changes which touches this issue.

It does that by providing iterator viewhelpers capable of returning the slice/next/prev/current/max etc. values that you need when you're creating links that contain for example a page number and number of items per page. With those two values the rest can be calculated with the ViewHelpers that would be added by the patch in question.

We had the same problem with 8.7 LTS and dataprocessors.

I found a way around it by passing values to the extbase subproperties of the FluidTemplate object.

extbase {
        pluginName = Demo
        controllerName = Demo
        controllerExtensionName = website
        controllerActionName = show
}

Then it works perfectly fine. Also adding a rule for realurl based on those values works without a problem.
So apparently there is no need for an actual Environment there.

If we find any issues with this solution in our project I will post it.

Tried to add pagination to a default File Lists content element in TYPO3 9.1 which uses a FilesProcessor. I have customised the Uploads.html template from fluid_styled_content to include f:widget.paginate and the first paginated page is displayed correctly, but all other paginated pages do not work. I realised the same behaviour as described in this issue.
The workaround from comment 6 does help, but is not so obvious I think.

Sebastian Helzle wrote:

We had the same problem with 8.7 LTS and dataprocessors.

I found a way around it by passing values to the extbase subproperties of the FluidTemplate object.

extbase {
pluginName = Demo
controllerName = Demo
controllerExtensionName = website
controllerActionName = show
}

Sebastian: could you share a bit more code for those, who are not so experienced? Where exactly do you add that code? What if my extension has 10 plugins or so? What to do then?
Thank you!

Still the same problem in 9.5.9

It's working with Sebastians approach: https://forge.typo3.org/issues/79430#note-6

A working example can be seen here: https://git.spooner.io/spooner/just_news/blob/development/1.x/Configuration/TypoScript/RenderingDefinitions/NewsList.typoscript#L4

From my point of view this ticket can be closed.

FLUIDTEMPLATE could use a generated string (e.g. from current content element ID) as a default if these values are not set.
That would make f:paginate work out of the box.

I am ready to have a go at that.

As the docs for the ViewHelper are not mentioning that right now, I see that as a BUG, not a FEATURE.

Definitely a BUG since this VH can not be used in the most basic use case :

page = PAGE
page {
10 = FLUIDTEMPLATE
templateName = Mypage
}

Where Mypage.html contains for exemple

<f:widget.paginate objects="{myBlogPages}" as="paginatedBlogs" configuration="{itemsPerPage:6}">
    <f:for each="{paginatedBlogs}" as="pageRecord" iteration="i">
...
    </f:for>
</f:widget.paginate>

BTW : Sebastian's hack only work if you add this to your ext_localconf.php as well :

\TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin(
    'just_news',
    'NewsList',
    [
        'JustNews' => 'list'
    ]
);