access

Hello drupal buddies, i have a simple question that i couldn't find the answer (maybe cause i cannot find the right keywords for search). I'm trying my first multisite installation of drupal, i created a folder tmp.mysite for my site in drupal_root/sites, and the installation completed without erros. Now on localhost i can access both the root site (with a url like http://localhost:port/drupal_root )

Please comment on how you are invoking email notifications, in general and for taxonomy subscriptions. Does anyone see a problem with workflow and drupal access model and/or 3rd party modules that supply that type of functionality?

With workflow, the natural point at which an announcement notification message should be sent is when the content changes to a certain workflow state -- e.g. "Posted". And the tools I see available for this task range from "send a tokenized email to a role" via the Token module (token_action.module) to the Subscriptions module.

Something I have had issues with on multiple sites I have worked on is administrative areas and permissions.

Example:
If I build a site for a client and then decide I want the client to be able to edit certain areas of the admin panel ("/admin/settings/site-information") but I don't want them to have full access to the administration area then there really isn't a good solution.

So, I ask... What exactly can be done about the issue? What would be some of the best work arounds?

I've just released the first alpha of a new module called i18n_access. This module aims to fill a gap in access control for sites using i18n.

The module adds a list of checkboxes for each available language to the user add/edit form (only visible to users with 'administer users' permission). These language permissions are combined with the normal user permissions to give more fine-grained access control.

Hej,
Efter att ha installerat drupal stacks för windows från bitnami.org så vill jag komma in i phpmyadmin. går som vanligt till "http://localhost/phpmyadmin/" och får inloggfönstret. men inget lösenord funkar
kruxet är att jag dels inte angivit något lösen i installationen (fick ej frågan) . finns det ett default användarnamn och lösen ??

Testar alla möjliga varianter, men får bara felkod 401 med texten
"Authorization Required

Much like living organisms are classified into groups (say, spiders) where many individual species (say, daddy long legs, black widow, tarantula) exist, we still have some distinguishing characteristics (eight legs, no wings) which separate it from other similar living organisms (say, bees).

I'd like to hear about what you would define as the distinguishing characteristics of a community media organization.

I eventually want to hunt for someone to do development on this idea, but first I'd like to find out how it can be designed to be of greatest benefit to the community.

I want to be able to manage access to a node, with CCK fields. The node should be viewable by both a role and at least a single (ideally multiple) user(s) not in the role.

The "best posts" wiki documents listed at the top of the Newspapers on Drupal group page are valuable resources, and from time to time I want to direct non-members to them (including at times entire classrooms full of students). But it seems they are only accessible to logged in members.

Putting it here, for people to comments and review.

> Hi,
> Please review this tutorial, I hope it's better, implementation-wise, then
> last one :)
> http://drupal.org/node/203377

Yep, that sounds like a cool use case.

I'd suggest that we write the tutorial, so that the nodes always keep
visible for everyone. For that we need content access and set it to
allow anonymous + authenticated users to allow view access.

-> Probably you have that already, but I can't find your figure 1?

I've put some work into a 5.x nodeaccess module. It could be the superior from the current nodeaccess module, and perhaps also from the simple_access module. I'm waiting for feedback from the authors..

So my module provides extended role based access control per content type, but it can be configured to manage per user access control per node - it does this by integrating with the ACL module, as well as role based per node access control.

Like simple_access it doesn't touch any permissions when it's activated. It also does some performance optimizations and tries to keep the UI simple.

Read a more detailed description or download and test the module at http://drupal.org/node/135693.