When implementing Jetsetter I had to authenticate from a REST service,
and the user's data was returned in the response payload from that
call. I was fine with that until I needed to work with JUser, which
stubbornly refused to look anywhere but the jos_users table instead.
Is there an easy way to get around this, or are we all going to be
forced to stuff copies of user data in jos_users to make JUser happy?
Better yet, is there a plan moving forward to break that dependency so
JUser will respect authentication plugins? Or is there a better
approach?
-- Mitch
// Add the include path for the table object.
JTable::addIncludePath(JPATH_ROOT.'/plugins/system/myuser/table');
// Load the table.
JUser::getTable('MYUser');
--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To post to this group, send an email to joomla-...@googlegroups.com.
To unsubscribe from this group, send email to joomla-dev-cm...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/joomla-dev-cms?hl=en-GB.
I'm not storing the user in a database. I'm not storing the user at
all in fact - the user is living in a remote store with a RESTful
service. My authentication plugin passes the data, and the return
payload includes the user's information (assuming login was successful
of course).
So there's no table. JTable is my stumbling block it would seem, correct?
-- Mitch
-- Mitch
-- Mitch
Sent from my iPhone