I'll quickly chip in and say that I've noticed the same draft bug as Chris and had to apply the same fix in the past. Was actually meaning to check if it was resolved in latest version of core, but looks like we're still working that out!
On Nov 22, 8:24 am, Chris Kent <[email protected]> wrote: > Thanks Blair, I have added comment to the ticket to explain why the extra > condition is still required. > > The problem with not including > <cfif bHasVersionID> > and versionID is null > </cfif> > > Is that for a content item that has been approved and then a draft copy > made for editing. This one content item returns 2 rows in the record set to > objectamdin. > > You see the draft/approved row and then a second row for the same content > item that is draft. > > This does not loot right and also causes problems wit the number of content > items returned. If there are 3 content items, C1, C2 & C3, and the first > item C1 is approved and has a draft copy then all you get back is > C1 draft/approved > C1 draft > C2 > > You do not see C3. > > The code immediately prior to building the record set is determining how > many records to send back, this calculates that there are 3 content items > to return. But the code that returns the content items requires the extra > where condition to not return the draft record for a versioned content > item. > > Chris. -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
