Log message #894880

# At Username Text
# Jul 17th 2009, 07:34 alkemann atm i got two remotes, should i just figure out how to replace origin?
# Jul 17th 2009, 07:33 markstory AD7six wanted to do some fixes on it, change how plugins are handled.
# Jul 17th 2009, 07:33 markstory still hasn' been merged.
# Jul 17th 2009, 07:33 markstory 1.3-bake
# Jul 17th 2009, 07:33 alkemann markstory: great. in 1.3 or 1.3-bake?
# Jul 17th 2009, 07:10 markstory if you get it from code.cakephp.org
# Jul 17th 2009, 07:09 markstory alkemann: bake all should be fixed now.
# Jul 17th 2009, 04:38 alkemann nah, ill be fair and share that with you
# Jul 17th 2009, 04:29 alkemann put it on ur todo :)
# Jul 17th 2009, 04:29 alkemann yea i like it too. lets do that.
# Jul 17th 2009, 04:29 Phally i like the latter, they will have PM's anyway, but indeed ask the user to forward it to his/her email
# Jul 17th 2009, 04:28 alkemann or apps only generate messages, user can opt to have messages forwarded to their email
# Jul 17th 2009, 04:27 alkemann right, generated emails could be part of this thing, users could opt for being notified in the internal message system, email or both
# Jul 17th 2009, 04:27 Phally alkemann: similar to the email component, something you include and send messages with and that sends email out to notify people
# Jul 17th 2009, 04:26 alkemann Phally: right, but it could be concieved a mroe hardcoded version where there were an article_id field in the messages table. but i dont think we should do that
# Jul 17th 2009, 04:26 alkemann Phally: so the apps needs an api to generate messages, and users could get access to them in the same way they do login
# Jul 17th 2009, 04:25 Phally alkemann: well you determine the content of the message in the app and let the plugin handle how it gets to the recipient
# Jul 17th 2009, 04:25 alkemann message content*
# Jul 17th 2009, 04:25 alkemann if the message is "your article has been rejected, and here is the reason why" the link to the article could be part of the message system isntead of a field in the model
# Jul 17th 2009, 04:24 Phally alkemann: it is communication between users, so it could belong to the users plugin indeed
# Jul 17th 2009, 04:24 alkemann also since its directly related to user model twice, and only indirectly linked to other stuff (like an article that is published or moderated) it can fit better there as well
# Jul 17th 2009, 04:23 alkemann get all ur "communication" consolidated. the ability to see "new messages" whatever app ur in etdc
# Jul 17th 2009, 04:22 alkemann err independent
# Jul 17th 2009, 04:22 alkemann gwoo: Phally: the user message thing. maybe that should be part of the plugin to be app agnostic?
# Jul 17th 2009, 03:58 Phally alkemann: will do
# Jul 17th 2009, 03:53 alkemann Phally: add public $displayField = 'username';
# Jul 17th 2009, 03:49 alkemann so u think Article belongsTo User (or UserProfile) ?
# Jul 17th 2009, 03:48 alkemann bah i work from work
# Jul 17th 2009, 03:48 Phally alkemann: no, i'm at work today, off at 15:30, so home at ~16:15
# Jul 17th 2009, 03:47 alkemann Phally: i assume u cant make the changes tothe plugin before later today?
# Jul 17th 2009, 03:11 alkemann dunno
# Jul 17th 2009, 03:11 Phally there was a field named `pos`
# Jul 17th 2009, 03:11 alkemann ?
# Jul 17th 2009, 03:11 Phally pos i.e., still wondering what it meant
# Jul 17th 2009, 03:10 alkemann i removed some
# Jul 17th 2009, 02:59 Phally alkemann: (talking about (user_plug_users))
# Jul 17th 2009, 02:59 Phally alkemann: hmm looks good, are those the existing fields?
# Jul 17th 2009, 02:56 alkemann Phally: http://thechaw.com/bakery/commits/view/adebd98e05ebee3ee8e4922c68268dc7388bc599#highlight
# Jul 17th 2009, 02:53 alkemann right, those cant be in the plugin
# Jul 17th 2009, 02:53 Phally alkemann: yeah exactly
# Jul 17th 2009, 02:52 Phally alkemann: using Modelbehavior::setUp() can be used to