roles

I've come up against a usability problem that I think is caused by a problem in Drupal's data model.

Example of problem: When setting block visibility settings, it is impossible (without writing custom php), to make a block visible to authenticated users who have no other role, if you don't want that block to show to all authenticated users. In other words, you may want to show the block to all authenticated users except those of belonging to role x. No can do without php.

I am still working on my directory http://justkansas.com.

I have used CCK to create the content type that is listed in the directory. I have a few fields that I would like to make available for paying memberships. I know that we can control the access to CCK fields by roles. But I am looking for a way to theme a node's display according to the author's role.

IF author role=role1 then use this code with all field entries displayed
IF author role=role2 then use this code without a certain field

When I decided I wanted to create a membership site, I realized that Drupal and and the e-Commerce module could probably do what I needed. The membership site will be selling content on a monthly basis. Users that subscribe during a given month will have access to that month's content.

I figured the easiest way to do this would be to use some sort of access control to assign a role -- for example, "200712" -- to a particular node. Then any subscriber with the appropriate role could access that content.

Greetings fellow Michigan Drupal users. I have a question. Let it be noted that I have only been using Drupal for about 2 months, so please forgive my newbisms & lack of knowledge...believe me, I'm trying, and I'm excited to be doing so.

I´ve posted at the Drupal Forum a certain problem that I have, and I would like to know if anyone of you have ever have this kind of issue in the past. And if you have, please give me a clue about how to solve this :-)

I´m running a site (of an NGO) that gives all their users free access to articles and information of a certain area. People do not need to registrate.

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.

I'm copying out jimw's recent comments (http://groups.drupal.org/node/465#comment) to begin a separate thread.

jimw brings up a couple of issues that has been talked about at some length. Specifically he is interested in roles like "volunteer", "presenter" etc. as they relate to Events: