Log message #899983

# At Username Text
# Jul 20th 2009, 03:33 Phally alkemann: you got kicked out
# Jul 20th 2009, 03:31 Phally i'll make the login work, the current users plugin was just passing the Auth login fields to the form and foreach them, so no problems there
# Jul 20th 2009, 03:29 alkemann now.. how am i gonna be able to run that schema file of yours
# Jul 20th 2009, 03:29 alkemann if the plugin includes the user stuff, including login form etc. then it can also have renamed the password field for the app that uses it without any extra work on the developer using the plugin. i dont think we need to spend mroe time on this issue ;)
# Jul 20th 2009, 03:28 alkemann say what you mean then, dont jsut mean what you say
# Jul 20th 2009, 03:27 Phally alkemann: i'm looking at the bigger picture, since the users plugin has set a standard
# Jul 20th 2009, 03:26 Phally alkemann: i meant the first indeed
# Jul 20th 2009, 03:24 alkemann Phally: if you by app mean the implementation in the plugin then yes, but not app as in bakery, code and book having seperate suers table.
# Jul 20th 2009, 03:23 Phally psword still is an app dependent choice, since Auth defaults to password
# Jul 20th 2009, 03:23 alkemann but if the field is psword or password. there is still no app dependant users table
# Jul 20th 2009, 03:22 Phally sure, but not if a table has more apps reading from it, you will have to change both
# Jul 20th 2009, 03:21 alkemann the book will have to move to the plugin at some point. it can use the old table until it does i guess
# Jul 20th 2009, 03:20 alkemann renaming a column is trivial
# Jul 20th 2009, 03:20 Phally eh, that will fuck up the manual
# Jul 20th 2009, 03:20 Phally yes there is... psword vs. password
# Jul 20th 2009, 03:20 alkemann we migrate the one that exists today into the new one made for the plugin
# Jul 20th 2009, 03:20 alkemann there is no app dependent users table
# Jul 20th 2009, 03:19 alkemann i do not understand what you mean by that
# Jul 20th 2009, 03:19 Phally of course we have one users table, but schema's for two, one example/default for the users plugin and one for the bakery itself (which is app dependent)
# Jul 20th 2009, 03:18 Phally eh, that isn't what i had in mind
# Jul 20th 2009, 03:17 alkemann we certainly will not have both an app and a plugin 'users' table
# Jul 20th 2009, 03:16 alkemann we make the users table in the users plugin the way it should look. we export the needed fields from the existing table. putting profile fields as wanted in an app specific UserProfile model
# Jul 20th 2009, 03:16 Phally i didn't bake the models yet, still they seem to be loaded
# Jul 20th 2009, 03:16 alkemann one of us is confused
# Jul 20th 2009, 03:16 Phally *missing table errors
# Jul 20th 2009, 03:15 Phally i think i know what might be the problem with those fields
# Jul 20th 2009, 03:15 Phally why i/we chose to keep a separated users table which is app dependend
# Jul 20th 2009, 03:14 alkemann what am i looking for?
# Jul 20th 2009, 03:14 Phally ehm yeah, that is well weird
# Jul 20th 2009, 03:14 Phally alkemann: read up :p
# Jul 20th 2009, 03:14 Phally alkemann: http://irc.cakephp.org/logs/link/897885#message897895
# Jul 20th 2009, 03:13 alkemann stupid getting an error saying missing table "conversation" when thats what im trying to create
# Jul 20th 2009, 03:12 alkemann didnt work either..
# Jul 20th 2009, 03:12 Phally the schema needs somework though i figured, since there is no way to see if a message is new
# Jul 20th 2009, 03:11 Phally or something like that, i ran it yesterday
# Jul 20th 2009, 03:11 Phally cake schema run create -path d:\www\bakery\plugins\users\config\sql -name Messaging
# Jul 20th 2009, 03:10 alkemann messaging.php could not be loaded
# Jul 20th 2009, 03:10 alkemann cake schema run update -dry -path d:\www\bakery\plugins\users\config\sql -file messaging.php
# Jul 20th 2009, 03:09 alkemann so we do an whatchamacallem.. convertion
# Jul 20th 2009, 03:09 Phally alkemann: the users table i would use for the plugin would look different from the existing one... i.e. for the plugin i would use a field named 'password' and not 'psword' because it follows Auth conventions
# Jul 20th 2009, 03:07 alkemann thats kinda the whole point of the plugin