On second thought, you could create a new file for a new class for the user code, make it extend the class User, and then redifine the one function needed. eg:
class MyUser extends User { ... }
Then change Setup.php as described.
This way, you have one file to maintain instead of two. (I would like to see define's or variables containing the class names to allow these low-level hacks without changing the code.
On 4/17/05, Jamie Bliss astronouth7303@gmail.com wrote:
The thing is the Auth plugin does not have a mechanism for custom session-ing, I think because the PHP functions are used.
You would have to change Setup.php to detect any cookie names changed, and User.php to use this. If you do it right and debug it, it should not break anything. (Keyword: should)
And I would not call this a minor hack.
On 4/17/05, Carlton B carltonb@mindspring.com wrote:
Hi all,
I am a very new MediaWiki user and I am looking for some advice on a minor hack to MW.
I want to set up MediaWiki to accept cookies from other sites as authorization tokens. My question is, in what module would I make this change, and what might break?
My goal is to have MediaWiki accept a third-party cookie to access the web site. The reason is that I have a BBS and a couple of other sites that I want to be allied with a common login, and I do not feel like adding an LDAP module.
I can manage the code required for the hack, if someone will just tell me which modules to start on.
Thanks... Carlton
MediaWiki-l mailing list MediaWiki-l@Wikimedia.org http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
--
http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now had 2GB.