user accounts

It is possible to loop through each registered user? What about user roles?

Here's a real use case.

I want to run a club; be it a book club or a night club, doesn't matter. Being a club, it must have members i.e. users with a particular user role applied ("member"). Each user membership lasts for a certain period of time ("membership period"), let it be one hour, 6 months or 20 years, doesn't matter.

[member] users have a field named "expiration" which contains the user creation timestamp with the [membership period] applied.

Hello,

I am going to create a D6-based web site for a huge number of users ( > 800,000). We expect this site to have tens of thousands of nodes (>20,000).

What is the impact on performance of these? I could not find any info on scaling the user accounts number. Does it make absolutely no problem performance-wise to have so many user accounts?

Here is what i managed to gather until now:
- i should use the SOLR module for my search engine, because the vanilla Drupal search engine will not scale to that nodes number,

I notice that there are many modules for manage users.
They associate a user at node.
But is possible when one delete an user , really delete the user's account?
I tested members og and this isn't possible.You can only eliminate members but it remains the drupal account.
Also tested usernode, wher in the view I add an delete field. But not work.

Is there some solutions?

Hello,

48 hours ago we had 2 things working that do not work now. And we must get them back to working.

1) My User, Jeremy, has all rights of the system currently. So do my other programmers. They have the right to change which users see which themes - at least they did have that ability. The one module that was installed was the development module, which we disabled again. Now we have no way to select which user sees which theme (this is an ability which our system must have).

I'm looking for a way to do the following:
* Have a central site the syncs up user accounts with XML feeds (already have working)
* Have sub sites (aka courses) use the user accounts from the central site
* Need to be able to do this without storing accounts locally in any of the course

Has anyone done anything like this or know of any way of accomplishing this? We have webaccess / cosign going so we have a single sign on system, i'd just like to keep everything central because we need to account for people adding / dropping courses via the XML string that gets updated twice a day.

I am about ready to go live with the portion of my site that allows students and parents and teachers to login. I am using the User Import module to import these users, but I have yet to find any module that allows an admin to delete large amounts of users at a time. For example: I picture needing to delete "Class of 2008" along with their parents at the end of the school year. The User menu allows you to filter off of role, permission, or status but not anything like group (og) or a hidden profile_value or something.

What solutions have you found that do this?

Hi, I think this module will be a very good companion: http://drupal.org/project/persistent_login

Hej!

Det är trevligt att höra att det finns så många Drupalmäniskor som engagerar sig i den kommande sajten, givetvis är jag också av uppfattningen att den borde vara på svenska men om det finns starka skäl till att ha den tvåspråkig så är det också OK!
Jag har ett problem och en fråga:
jag har satt upp en sajt åt en organisation och gett moderatorbehörighet åt de som ska driva den, vilket oturligt nog gav dem möjlighet att städa bort mitt administratörskonto (user/1)!!!!!!
Innebär detta några problem?
Är det något som inte kan göras utan detta konto?

Short Project Description:
Creating User SMS registration and notification based on the existing SMS Gateway module, and give some basic SMS-enabled features.

Motivation:
The SMS Gateway module is a good base for SMS integration in Drupal, but it forces the Drupal site creator to write relevant code for any feature needed.

The main idea is to create a basic set of functions and features which will give the site creator set of ready-made features.
The list of features I think that should be implemented are:

<

ul>

UPDATE (Jan 11): Code has been moved from the sandbox to ecommerce CVS pending full integration with the ecommerce system. I'm currently writing upgrade code to move products and the transaction records over to the new format. NOTE: If you are migrating custom solutions you will need to take special care with the upgrade. You may need to manually update the schema revision field in the system table to skip the upgrade and apply your own code instead.

Once the upgrade code is complete i'll be removing the old code from ecommerce. After this i'll send a mail to the ecommerce list to ask for testers.

You can get a copy of the alpha code by using the CVS tag DRUPAL-4-7--3. Alternatively download the tarball.

UPDATE (Oct 12): Thank you to the financial contributors. Code for all modules is now available in my sandbox. Please keep in mind that the code is still in beta and no upgrade code is available for you to upgrade your current 4.7 sites. It is not recommended that you use this code in production. Please post all issues to the Drupal issue queue and it would be very handy if you provided patches. I'd like to get hold of some anonymized production databases using the 4.7 default recurring product system. It'll help me build the upgrade code.

UPDATE (Sep 30): Still waiting on financial contributors. The ec_anon module is ready for trialling. It's available in my sandbox.

UPDATE (Sep 22): I'm excited to announce ec_recurring, ec_roles and ec_mail modules are ready for testing. There is a slight delay on ec_useracc due to some extra feature requirements on EC. That should be available very soon. Financial contributors please forward your second instalment and contact me to obtain code.

UPDATE (Sep 04): Feature Freeze in effect as of September 4, 2006. No more features will be added.
Scheduled UAT date: September 22, 2006. Scheduled completion date: September 30, 2006.

Hi everyone,

I've just finished writing up a specification document from which developers can see what is planned for E-commerce in relation to subscriptions, roles and user accounts being manipulated during checkout. These are highly sought after requirements and many people are scratching their own itch scratch scratch. My aim, though providing a specification document, is twofold. First, I want to make sure everyone knows what we're developing for 4.7 and then for 5.0 (after we do some major changes to E-Commerce core). Second, it provides a solid reference for any developer planning to write anything.