Pagination not available for Low Events?

I need to output all passed events in descending order, so my low_events tag is pretty straight forward:

{exp:low_events:entries channel="events" unit="passed" show_active="no" limit="12" paginate="both" orderby="low_events:end" sort="desc"}

However this seems to ignore pagination: is it not possible to paginate a low events set? My {pagination_links} seems to be working correctly, but isn't affecting the returned entries.

I should also say that I'm using Structure, if that makes a difference?
1 person has
this problem
+1
Reply
  • Low (Official Rep) August 20, 2013 16:09
    What are your EE and LE versions? Also, can you enable template debugging and copy/paste the lines that mention Low Events here?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • EE 2.6.1 and LE 1.1.4.

    This is what I think is relevant:

    (0.016742 / 8.10MB) Tag: {exp:low_events:entries channel="events" unit="passed" show_active="no" limit="12" paginate="both" orderby="low_events:end" sort="desc"}
    (0.016914 / 8.10MB) Closing Tag Found
    (0.017002 / 8.10MB) Processing Tags
    (0.017054 / 8.11MB) Module Tag: Low_events/entries
    (0.017078 / 8.11MB) Including Files for Plugins and Modules
    (0.020658 / 8.29MB) Files for Plugins and Modules All Included
    (0.021268 / 8.31MB) Beginning Final Tag Data Processing
    (0.021291 / 8.31MB) Calling Class/Method: Low_events/entries
    (0.021852 / 8.32MB) -> Class Called: Low_events
    (0.024529 / 8.49MB) Low Events: Fetching channel fields from API
    (0.055328 / 10.70MB) -> Method Called: entries
    (0.055446 / 10.71MB) Low Events: Working date set to 2013-08-20 18:37
    (0.055480 / 10.71MB) Low Events: Unit: passed
    (0.062427 / 10.90MB) Low Events: Setting fixed_order="173|229|228|239|256|255|257|240|225|227|253|258|226|252|250|251|222|248|247|249|221|243|242|244|245|246|220|270|177|178|179|180|181|182|176|183|184|185|186|162|204|205|206|207|208|209|210|211|212|213|214|171|172|201|202|203|175|195|196|197|198|199|447|200|586|161|474|154|156|157|158|159|388|160|425|635|745|758|759|760|761|762|832|764|765|766|767|768|458|1056|1113|1049"
    (0.062483 / 10.90MB) Low Events: Calling the channel module
    (0.067029 / 11.07MB) Calling Extension Class/Method: Structure_ext/channel_module_create_pagination
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Low (Official Rep) August 21, 2013 07:35
    Yeah, I reckon Structure is causing this. It changes the internal URI so the pagination URI isn't present, so EE can't use it for pagination. If you change the low_events:entries tag with a native channel:entries tag, you'll most likely see the same behaviour.

    You'll need to allow extra segments for the events URI in Structure somehow, although I'm not quite sure how, as I'm not that familiar with Structure.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Yes sorry, you're right: (FYI) it was basically a conflict in Structure where if your page names are the same as the template group/template combo it ignores pagination. Sorry to waste your time.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated