[wp-hackers] Files associated with table *_users

[Curt Woodard]

Matt, Alex, thanks for the swift replies.

Matt: I don't use linux, I'm on Windows... I suppose I could install
grep for Win32 if it exists...

Alex: I was thinking that as well, I'd just have to figure out how to
write the plugin and then how to interface everything with SMF. I'd
need to be able to replace everything dealing with WP logins with SMF
SSI calls. Do you know of any information available to allow me to
write a plugin that replaces all of this? I've already looked at the
two databases and am in the process of mapping what fields in WP would
match with those in SMF and could probably, very easily, write a
wrapper that places the SMF user data in the format that
wp_get_current_user uses... I'll have to see what I can do.

PS are there archives for this list?

Thanks again for the swift replies.
-Curt

------------------------------
Message: 2
Date: Fri, 17 Aug 2007 13:58:44 -0400
From: "Curt Woodard" <clwoodard at gmail.com>
Subject: [wp-hackers] Files associated with table *_users
To: wp-hackers at lists.automattic.com
Message-ID:
       <a3b809ae0708171058q676d9dacg613ddef3c8bfa625 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Was curious as to exactly which files are affected by and access the
*_users table in WordPress 2.0.

Why?

I'm tired of dealing with multiple user tables for different things
and want to use SMF's user table for WordPress just as I have for
MediaWiki.

I want to disable anything that uses the WordPress tables for user
information and instead use SMF's.

Any information would be greatly appreciated.

Thanks,
-Excalibur


------------------------------

Message: 3
Date: Fri, 17 Aug 2007 11:05:26 -0700
From: Matt Mullenweg <m at mullenweg.com>
Subject: Re: [wp-hackers] Files associated with table *_users
To: wp-hackers at lists.automattic.com
Message-ID: <46C5E366.5020703 at mullenweg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Curt Woodard wrote:
> Was curious as to exactly which files are affected by and access the
> *_users table in WordPress 2.0.

Grep through the code for $wpdb->users and $wpdb->usermeta and you'll
see all the places we query those tables.

--
Matt Mullenweg
 http://photomatt.net | http://wordpress.org
http://automattic.com | http://akismet.com
------------------------------
Message: 4
Date: Fri, 17 Aug 2007 20:17:15 +0200
From: Alex G?nsche <ag.ml2007 at zirona.com>
Subject: Re: [wp-hackers] Files associated with table *_users
To: wp-hackers at lists.automattic.com
Message-ID: <1187374635.6047.3.camel at localhost>
Content-Type: text/plain; charset=ISO-8859-15

On Fri, 2007-08-17 at 13:58 -0400, Curt Woodard wrote:
> I want to disable anything that uses the WordPress tables for user
> information and instead use SMF's.

A better solution for this would be writing a plugin which handles the
authentication against your other system. This will make upgrading much
easier. (Don't forget to write a replacement for the pluggable function
wp_get_current_user().)

Best regards,
Alex

--
Alex Günsche, Zirona OpenSource-Consulting
Blogs: http://www.zirona.com/ | http://www.regularimpressions.net
PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc
------------------------------