DISCLAIMER: You use these plug-ins at your own risk!
I am not responsible for any damage these files may or may not cause.

If you have questions, feature requests, bugs to report, or anything else
related to these plugins, visit My Plugin Disccussion Forum.

Hey, nothing fancy, just listing my plugins for WordPress 2.2.2.!

Slave Me 2 WordPress Version 2.6 BETA (2007-08-30 20:30:40).

About:
Slave Me 2 WordPress (working title, maybe? Sounds too ambiguous at the moment)
is a plugin that allows an administrator to "slave" any number of WordPress
blogs to a master WordPress user table and usermeta table. In addition, it
allows concurrent logins with all of those installations as well as allowing the
admin of the "WordPress Farm" to assign different capabilities to a user based
on the install. So, a user may have admin rights on JimmyBob's WP Stall
but only have subscriber rights on Mary's Needlepoint Blog.

Installation:
Installation is pretty simple: If you have 2 or more installs of WordPress 2.2.2
and you want to use one user table amongst them, just unizp the contents of the
SM2WP.zip file into the wp-content/plugins folder of each of the installs.

Activate the SlaveMe2WordPress plugin in each installation (I'm assuming you
know how to do this). The options are found at Admin Panel > Options > SM2WP.

For the master copy there is nothing to configure.

For an example install, the Master copy will have these settings.
Master Copy Database Name = wp_master
Master Copy Prefix = wpM_

Now, for each of the slave installations, you will need to edit the options on
the SM2WP options panel. Here is an example using the above settings:

Features:
   * Share 1 users and 1 usermeta table amongst any number of WordPress installs
   * Concurrently login to any of the installs
   * Give users different permissions on each install
   * Now with option panels to set the role and database information.
   * ... Have I forgotten anything?

Todo (Possibly):
   * Provide a sub-domain free cookie option

Changelog:
   * 2007-08-30 20:30:40:
      * Found an issue with the auto-detection. While the table names may be the
        same, usually (and I mean usually) the databases are as well. This might
        not always be the case, but to be on the safe side, I set the automatic
        detection of master/slave to check for either different database name or
        different prefix.
      * The %user_level was not being copied over for people who were in the
        user table but not in usermeta. Now the level for the default user is
        also set for the users. Everyone, on a default install, should start out
        as a subscriber with a userlevel of 0. Though, I didn't hardcode this so
        whatever the default role, its taken from the database then the roles
        option is checked and the highest level of access that role has is set
        for the user's level.
      * Stephen & Chris: THANKS! :) At least I have someone testing for me in an
        environment that is not mine :)

   * 2007-08-30 12:16:23:
      * When adding a new user, the blog to which the user is added has the role
        indicated on the form, however, all other blogs do not have the role set
        and instead show the user as "No Role for this User" or some such error.
        I went ahead and added a way to check for users without roles in the
        usermeta table and all users are now assigned a default role based on
        the blog in question. Thanks to Stephen for reminding me about this, I
        had dismissed it as a bug, thinking this would be the proper behavior.
      * Upgraded to version 2.5 BETA.

   * 2007-08-29 23:04:20:
      * Cleaned up the code quite a bit so that there are is only one variable
        declared outside of a funciton in the main script: $sm2wp_options
      * Cleaned up the options so that only two are now available (thanks to
        Stephen for this idea). SM2WP now checks to see if the current install
        of WP has a table prefix that matches that of the master copy. If it
        doesn't, then it's a slave copy, otherwise it is a master copy.
      * Cleaned up the option storage so that it is stored under one entry in
        the options table: sm2wp_options which is a serialized array.
      * Killed off the admin_transfer option. If the install is a slave, then it
        will either have entries in the master usermeta or it won't. If they do
        not, then SM2WP will create them, otherwise it will not.
      * There would be an issue when returning a slave back to master status:
        the user and pass cookies, which are now stored in the sm2wp_options
        array, would still point to the previous master. This has been fixed so
        that during the loading of the options, the correct cookies will be put
        back into the option array.
      * Since I'm now using the table prefix matching method to determine the
        master/slave role of the blog, I also removed all options dealing with
        the role, including the master/slave dropdown on the main option panel.
      * Tested the plugin again to see how stable it is, everything checked out
        fine. There was an issue with multiple copies of the usermeta from the
        slave appearing in the master table. This was fixed. The script should
        be relatively stable now, but test to be sure.
      * Added this readme file and the accompanying images to the plugin's zip.
      * Upgraded to version 2.0 BETA
   
   * 2007-08-28 18:35:23:
      * Added an options panel for configuration
      * Removed hard-coded variables to make the script generic
      * Added options at the beginning that assume a master install.
      * Added this readme file and the accompanying images to the plugin's zip.
      * Upgarded to version 1.5 BETA

   * 2007-08-28:
      * Wrote the plugin, tested the plugin, announced the plugin
      * Version 1.0 BETA, Initial release.
      * Went to Disneyland...

Thanks to...
   * Chris for giving me the idea while asking about the status of SMF
     Integrator.
   * Stephen Rider for trying this out and giving me suggestions, especially for
     pointing out the hard-coded variables at the beginning of the script.

********************************************************************************

SMF Integrator

Work in progress... There are still things that need to be done, I will update
this space when I'm ready to do so. :)

---

You are viewing a mobilized version of this site...
View original page here

Mobilized by Mowser