CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #3432

Put the pagebrowser where it belongs

Added by Susanne Moog about 4 years ago. Updated over 2 years ago.

Status:Resolved Start date:2009-05-23
Priority:Must have Due date:
Assignee:Susanne Moog % Done:

100%

Category:Templating
Target version:1.0
Votes: 0

Description

The pagebrowser should be a viewhelper.

Associated revisions

Revision 20613
Added by Susanne Moog about 4 years ago

Bug #3432: Moved the pagebrowser into the viewHelpers

Revision 20613
Added by Susanne Moog about 4 years ago

Bug #3432: Moved the pagebrowser into the viewHelpers

Revision 20786
Added by Susanne Moog almost 4 years ago

Bug #3432: Deleted the "leftover" pagebrowser model

Revision 20786
Added by Susanne Moog almost 4 years ago

Bug #3432: Deleted the "leftover" pagebrowser model

History

Updated by Susanne Moog about 4 years ago

  • Status changed from New to Accepted
  • Assignee set to Susanne Moog
  • % Done changed from 0 to 90

The pagebrowser is now a viewHelper, but it still needs proper localization and a better handling of TS related settings (currently the settings are handed over by the model to the template and then to the viewHelper).

Updated by Fabien Udriot almost 4 years ago

What is the status of this issue?

I still notice in the trunk ViewHelpers/PagebrowserViewHelper.php

Updated by Susanne Moog almost 4 years ago

The status is as said above: the pagebrowser is now where it belongs but it still misses proper localization (strings are hardcoded in the viewhelper) and (nicer) access to ts configuration - both things depend on missing features of fluid (I asked concerning both things on the mvc mailing list already, so they have it "on screen").

Updated by Susanne Moog almost 4 years ago

  • Category set to Templating
  • Status changed from Accepted to Resolved
  • Target version set to 1.0
  • % Done changed from 90 to 100

Just added the proper localization with kind of a "workaround". The page browser is now rendered with this snippet:

<addr:pagebrowser totalCountOfAddresses="{totalPages}" maxAddressesToDisplay="{maxItems}" previousLabel="<f:translate key='previousLabel'>Previous</f:translate>" pageLabel="<f:translate key='pageLabel'>Page</f:translate>" outOfLabel="<f:translate key='outOfLabel'>out of</f:translate>" nextLabel="<f:translate key='nextLabel'>Next</f:translate>" />

I'll close this bug and will open one again, if I find a better way to implement this.

Also available in: Atom PDF