Support archive

Next entry tag on EE2.5

leeaston 8 May 2012 11:46 question, complete

Can't get Next Entry Tag to work - show up on page. EE2.5 and latest LR.

Does it work (show on page) for you?

Best wishes
Lee

{exp:low_reorder:next_entry set="1" url_title="{segment_2}"}
Next: {title}
{if no_results}This is the last page{/if}
{/exp:low_reorder:next_entry}

Replies

1. Low 8 May 2012 12:00

   It does work for me. Can you paste your complete template code in a http://pastebin.com/ so I can investigate further?
   
   Also, take a look at the Template Debugger, and look for lines with Low Reorder. That might give clues why it's returning an empty string, too.

2. leeaston 10 May 2012 08:04

   Do exp:low_reorder:next_entry and exp:low_reorder:prev_entry have to be used outside the exp:low_reorder:entries tag - like on http://expressionengine.com/user_guid...

3. Low 10 May 2012 08:06

   No, they can be used inside the entries tag. Just make sure you define prefix in the prefix="" parameter, so as to avoid variable conflicts.

4. leeaston 10 May 2012 09:22

   Thanks. Do exp:low_reorder:next_entry and exp:low_reorder:prev_entry have to be used on single entry pages where either the entry id or url title is included in the url?

5. Low 10 May 2012 09:24

   Yes, you have to pass the entry_id or url_title of the current entry, so LR can look for the previous/next entry in the set.

6. leeaston 10 May 2012 09:56

   I've got:
   www.site.com/design/entry1
   
   {exp:low_reorder:entries set="1" limit="1" disable="member_data|category_fields"}
   
   {exp:low_reorder:prev_entry set="1" url_title="{segment_2}" prefix="next_" loop="yes"}
   < a href="{path="bespoke-kitchen-design/{next_url_title}"}">NEXT KITCHEN DESIGN →
   {/exp:low_reorder:prev_entry}
   
   {/exp:low_reorder:entries}
   
   Clicking NEXT KITCHEN DESIGN changes the url to www.site.com/design/entry2, but entry1 is still displayed.

7. Low 10 May 2012 09:59

   The dynamic="" parameter is automatically set to "no" in the low_reorder:entries tag. Either explicitly set it to "yes" or add the url_title="{segment_2}" to the low_reorder:entries tag:
   
   

   {exp:low_reorder:entries set="1" url_title="{segment_2}" limit="1" disable="member_data|category_fields"}

8. leeaston 10 May 2012 10:51

   Thanks it's working now. But I think it works slightly differently to the old version. On the old version I could have www.site.com/design (no url title) and the LR next tag would move on to the next entry as www.site.com/design/entry2 - it could do this because the exp:channel:entries tag was providing the entry id to the next tag.

9. Low 10 May 2012 10:54

   Then you could use something like this:
   
   

   {exp:low_reorder:entries set="1" dynamic="yes" limit="1"} 
      {title} 
      {exp:low_reorder:next_entry set="1" entry_id="{entry_id}" prefix="next_"} 
        {next_title} 
      {/exp:low_reorder:next_entry} 
    {/exp:low_reorder:entries}

   
   
   ...nesting the prev/next tags allows you to use the entry_id generated by the entries tag.

10. leeaston 10 May 2012 11:01

    That dosen't work because {exp:low_reorder:entries set="1" limit="1"} always displays the first entry regardless of the url title in the url

11. Low 10 May 2012 11:07

    Even with the dynamic="yes" parameter explicitly set?

12. leeaston 10 May 2012 11:12

    Been staring at this to long! You're right, I forgot to add in dynamic="yes", now I have it's working.
    
    Many thanks for all your help, and of course your add-ons. I get all my clients to but LR and LV.

13. Low 10 May 2012 11:13

    Excellent. Glad to help, Lee. :)