Jump to content

Search the Community

Showing results for tags 'Potential Bug'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. I think I may have stumbled into a bug, or perhaps something has changed since 2.5.3. I have the following function that I refer to in order to obtain the latest journal entry, or the one after that if the latest is currently being viewed: function journalLatestEntry($showNextIfCurrent = true) { global $wire; $return = array( 'page' => $wire->pages->findOne('template=journal-entry, sort=-created'), 'isCurrent' => false ); if ($showNextIfCurrent) { if ($wire->page->id == $return['page']->id) { $return['page'] = $return['page']->next; $return['isCurrent'] = true; } } return $return; } Unfortunately, since upgrading the dev-site to 2.6.0, next is returning NullPage erroneously as there are pages after the one returned. Perhaps something has changed with regards to the way in which findOne() works?
×
×
  • Create New...