For Drupal 6

Semi-anonymous user is an interoperability extension for external authentication. Data you wish to store remotely from the Drupal database about users in an external authentication configuration is made available and usable for other modules without needing to be recorded in the users table.

Semi-anonymous user creates real, temporary users in Drupal for Drupal to associate with your external data but it does not give those users any of your external data. $_SESSION and {session} only are used, not {users} and the data persists only as long as your php session ID. Then the semi-anonymous user implements hook_user() to retrieve it's session data, making it available in the global user for other modules to use.

You can use this module's functions to present profile and custom, personal information which can not, or should not reside in Drupal's database safely to the Drupal user as if it did.

How it works - Once your module has gathered it's user data, you should call semianonuser_do_login and pass an associative array.
semianonuser_do_login(array('detail' => 'thing about user', 'email' => 'email address')); Anything passed in will appear in the global user array to all other modules, so pass in anything you wish to see available.

When you are logging out your user or destrying their session call semianonuser_do_logout(). Your data will not be entered into the user table, instead a randomly generated username will be created and entered into the user table with a bare minimum of detail instead. Your data is stored in the php session and merged onto this random user to create the global Drupal user letting all Drupal modules see the details you're hiding.

If a logout occurs, or the session's expiry time elapses this sesion table row is deleted. Cron will clean out all semi-anonymous users 24 hours after their last access. hook_unistall is implemented to clean up after uninstallation.

Link to sandbox project:
http://drupal.org/sandbox/unclebob/1783002

Git Clone
http://git.drupal.org/sandbox/unclebob/1783002.git

Comments

sanchi.girotra’s picture

Hi,

1.Please add git link corresponding to non-maintainer in the issue summary like "http://git.drupal.org/sandbox/unclebob/1783002.git".

2.Please review your module from coder module and see automated review here.

blg@bgreenaway.com’s picture

Status: Needs review » Needs work
blg@bgreenaway.com’s picture

Thanks for your input - I shall update this over the weekend :-)

blg@bgreenaway.com’s picture

Issue summary: View changes

starting to fix for comment #1

blg@bgreenaway.com’s picture

Status: Needs work » Needs review

Thank you sanchi.girotra. I have amended my module and the issue body to reflect the changes you required.
The automated coder and sniffer check seems to pass without comment, which to my newbie eyes suggests the issues were addressed.
And the link to clone the repo is in the form you suggested, and also seems to be correct now.

I am marking it 'needs review' again, hopefully that's the right thing... waiting to hear next Thanks

ayushjn’s picture

It appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.

Follow the following links:
http://ventral.org/pareview/httpgitdrupalorgsandboxunclebob1783002git
http://drupal.org/node/1127732
http://drupal.org/node/1015226
http://drupal.org/node/1066342

Regards.

ayushjn’s picture

Status: Needs review » Needs work

Oops, missed changing the status, doing it.

blg@bgreenaway.com’s picture

Status: Needs work » Needs review

Thank you ayushin - I have followed the instructions in http://drupal.org/node/1127732 and removed the deprecated files from the master branch, switching the default branch to the newly created 6.x-1.x branch.

Assigning 'needs review' once more :-)

Thank you :-)

d2ev’s picture

Manual Review:

The code and syntax looks good and not much to check in code. I implemented for my custom module and it's work for me.

blg@bgreenaway.com’s picture

Thank you D2ev. I hope you found my implementation instructions sufficiently detailed.
Thanks for taking the time to review for me.

blg@bgreenaway.com’s picture

So how does this project get given the sign off...?
D2ev, ayushjn, sanchi.girotra, could one of you clarify the means by which the next stage of my review is reached please?
And would that be marking the status 'reviewed & tested by the community' for sign off or does something else have to happen before that?

d2ev’s picture

blg@bgreenaway.com’s picture

Status: Needs review » Needs work

Thanks D2ev :-)

I read, "Once all issues have been addressed: The reviewer will change the status of the issue to 'RTBC'." from the instructions in your first link.
The second link lists issues beyond syntax, version control, working condition and compatibility with core APIs required prior to granting commit status, so I shall proceed from there. Review Bonus Scheme Participation is listed at item two :-)

Thanks again.

klausi’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. Feel free to reopen if you are still working on this application.

klausi’s picture

Issue summary: View changes

fix 1 to comment #1 - correcting git clone link to non-maintainer