ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Order By Date field doesn't work beyond a scope.

January 09, 2011 11:25pm

Subscribe [4]
  • #1 / Jan 09, 2011 11:25pm

    Hi all, I’m having an issue with an installation of mine, where a client’s podcasts are being ordered via reverse relationships by a custom date field, (they are using the entry date field for other purposes) and all seems to work beautifully, except for anything before October 01, 2001. Those items show up *first* in the list, followed by everything else in the correct order. This is pretty vexing, since they have their *first* podcast/recording in August 2001. Are there any known bugs or causes of behavior that might cause this? Currently the code I have is:

    {reverse_related_entries channel="podcasts" orderby="podcast_publish_date" sort="desc"}
    {if count == "1"}<h3>Podcasts</h3>
    <p><ul>{/if}<br />
    <li><a href="http://{url_title_path=podcast}">{title}</a> | Published: {podcast_publish_date format="%F %d, %Y"}</li><br />
    {if count == total_results}</ul>{/if}<br />
    {/reverse_related_entries}

    Is there anything I’m missing? Do I need to provide more info? Any help would be *greatly* appreciated!

  • #2 / Jan 10, 2011 10:08am

    Sue Crocker

    26054 posts

    Hi, Christopher. You didn’t mention which build/version of EE2.x your client is using. You can find that out in the bottom of any control panel page in the footer.

  • #3 / Jan 10, 2011 1:10pm

    Sorry, Sue. I’m running EE 2.1.3, build 20101220.

  • #4 / Jan 10, 2011 7:43pm

    Lisa Wess

    20502 posts

    Are those posts stickied by any chance?

  • #5 / Jan 10, 2011 7:47pm

    Unfortunately, no. And if they were, it’d be odd that they’d only show up at the top if they were pre-October 2001.

  • #6 / Jan 11, 2011 9:22am

    Sue Crocker

    26054 posts

    Keeping reverse_related_entries out of the equation for now.. if you use a standard exp:channel:entries loop, do the items display as expected when using that custom field?

  • #7 / Jan 11, 2011 12:07pm

    It flows perfectly fine, as we have it in a podcast feed. It shows perfectly fine there when not displayed as a reverse_related_entry.

  • #8 / Jan 12, 2011 4:01am

    John Henry Donovan

    12339 posts

    Christopher,

    just to rule it out can you add a status to the reverse_related_entries tag

    {reverse_related_entries channel="podcasts" orderby="podcast_publish_date" sort="desc" status="not closed"}
  • #9 / Jan 13, 2011 4:49pm

    John,

    I tried it out, and still have the same issues. Here’s my full code on droplr: http://d.pr/r0I7

    The page in question is: http://nurevolution.net/ee/artists/trey_turner

    The “Broken” entry should not show at the top for the artists’ podcasts.

  • #10 / Jan 14, 2011 12:20pm

    Lisa Wess

    20502 posts

    Hi, Chris!

    The first step in troubleshooting this is going to be making a reduced template with the bare minmum, to isolate the issue.  Can you try this in a test template?  No other code.  It will be a totally unstyled page:

    {exp:channel:entries channel="artists" disable="categories|trackbacks|member_data" limit="1"}                    
    <h1>{title} : {entry_id}</h1>
                        {reverse_related_entries channel="podcasts" orderby="podcast_publish_date" sort="desc" status="not closed"}
                        <a href="http://{url_title_path=podcast}">{title}</a> | Published: {podcast_publish_date format="%F %d, %Y"}
    
                        {/reverse_related_entries}
    {/exp:channel:entries}

    and let’s see if we get the right results?

    Thanks!

  • #11 / Jan 27, 2011 10:18am

    Sue Crocker

    26054 posts

    Hi, Christoper.. how are things going? Any news?

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases