done
http://bugs.farcrycms.org/browse/FC-2250
On 12 April 2010 12:45, Jeff Coughlin <[email protected]> wrote:
> I have to agree with AJ on this one. It would be helpful to have the extra
> field in the DB and do it correctly.
>
> In Geoff's defense though, if the feature request was approved it wouldn't
> make it into core until at least the next minor version (ie. 6.1) since
> patch versions don't have database changes. If you put in the feature
> request to have this added to FC6.1, I'll vote for it (+1). Come back here
> with the link to the feature request and we'll see how many votes it gets.
>
> Regards,
>
> --
> Jeff Coughlin
> Web Application Developer
> http://jeffcoughlin.com
>
> On Apr 11, 2010, at 10:30 PM, AJ Mercer wrote:
>
> > comment inline
> >
> > On 12 April 2010 10:12, Geoffrey Bowers <[email protected]> wrote:
> > On 10/04/2010, at 8:39 AM, AJ Mercer wrote:
> > > yeah - I was wondering about datetimelastupdated too.
> > >
> > > Can I get confirmation from the team Daemom
> > >
> > > On 10 April 2010 00:42, Tomek Kott <[email protected]> wrote:
> > > couldn't you use "datetimelastupdated" as a proxy? Since FC reads/sets
> that data at the time it is locked (pretty sure), I think that would be
> exactly what you're looking for... or am I misunderstanding it?
> >
> > No, datetimelastupdated should only be updated on an update. Otherwise
> we'd have "touched" the object every time somebody opened an edit handler --
> even if they hit cancel.
> >
> > Adding something like a datetimelocked would mean adding it to "types"
> abstract class, which in turn would mean adding it to *every* content type
> for now and forever after. I'm not sure there is enough benefit to the
> user.
> >
> > But it wouldn't hurt anyone to have this extra detail
> > Then in the Object Overview, under Sytem Information, it could be added
> after Last Updated by; with pretty date eg 2 minutes ago or 2 days ago
> >
> >
> >
> > A better proxy might be to look at the user who locked it -- which we
> already do. But we could enhance this possibly by looking at whether or not
> the user is logged in, or at least how long ago they logged in. This would
> give you a good handle on whether or not there was a danger of overriding
> their work.
> >
> > -- geoff
> > http://www.daemon.com.au/
> >
> > --
> > You received this message cos you are subscribed to "farcry-dev" Google
> group.
> > To post, email: [email protected]
> > To unsubscribe, email:
> > [email protected]<farcry-dev%[email protected]>
> > For more options: http://groups.google.com/group/farcry-dev
> > --------------------------------
> > Follow us on Twitter: http://twitter.com/farcry
> >
> > To unsubscribe, reply using "remove me" as the subject.
> >
> >
> >
> > --
> >
> > AJ Mercer
> > http://webonix.net
> > http://twitter.com/webonix
> >
> > --
> > You received this message cos you are subscribed to "farcry-dev" Google
> group.
> > To post, email: [email protected]
> > To unsubscribe, email:
> > [email protected]<farcry-dev%[email protected]>
> > For more options: http://groups.google.com/group/farcry-dev
> > --------------------------------
> > Follow us on Twitter: http://twitter.com/farcry
>
> --
> You received this message cos you are subscribed to "farcry-dev" Google
> group.
> To post, email: [email protected]
> To unsubscribe, email:
> [email protected]<farcry-dev%[email protected]>
> For more options: http://groups.google.com/group/farcry-dev
> --------------------------------
> Follow us on Twitter: http://twitter.com/farcry
>
--
AJ Mercer
http://webonix.net
http://twitter.com/webonix
--
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
