negate (not) condition for role

This would be a great addition to the module, to be able to hide blocks for for example the administrator. For now I will just hack some php together for the olde blocks system:

global $user;
if ($user->uid != 1) {
    return "This block is hidden for the user with the user-ID 1.";
} else {
    return;
}

...and to change the order of the blocks, which is "0" by default, by updating the weight of the block in the database, to for example "3", and then drag and drop the order with Context UI + Admin

I actually did mean !=

But I lifted the code from somewhere else, so the "help" text was false 8o)

This makes more sense:

global $user;
if ($user->uid == 1) {
  // This block is hidden for the user with the user-ID 1.
  return FALSE;
} else {
  return TRUE;
}

This is exactly what I want to do as well, show a membership ad to the users who do not have the subscriber role

+1. Would love to see this feature in context. Need to show a block to everyone who is NOT of "subscriber" role.

Yes. A generalised "NOT" applied to all conditions would be super useful.

+1

El B

Ressa

Ref. Your code. Sorry. I've not quite got this. Is this code added to the Page Specific Visibility Section using the standard /admin/build/block interface, even though the block is not assigned to a region via the Blocks system ?

Cheers

El B

ElB: I did move the block to the desired region via the standard /admin/build/block interface, updated the weight of the block in the database, and dragged and dropped the order with Context UI + Admin. Probably as the last thing I added the php code, to hide it from admin

I just can't seem to reproduce it now... Perhaps a better solution would have been to auto assign a specific role to new users ('new user'), and use the Context interface to only show the block to the roles 'anonymous' and 'new user'?

You can already achieve a negated context. It's a little counter-intuitive, but it's totally possible, as originally pointed out here: http://drupal.org/node/580324#comment-4401174

You create a context based on a positive selection. Let's say a context called "is_member" which uses a Role Condition to see if a user is in the "Community Member" role). Then you create a second context that has a Context Condition which is true if the first context is negative - in this case, "~is_member".

Job done :)

I thought I'd be bold and change the component to UI (implementing this feature would just be an improvement to the interface/workflow for something that's already possible), and change the priority to minor (if it's already possible, then this can't be a high priority).

Apologies if that was too bold -- just trying to help reduce pressure on the issue queues :)

subscribe

Attaching a patch that adds a checkbox to the User Role condition which allows you to make the user condition a negative one. I did some testing and it seemed to work fine, but I didn't have any complicated cases to test it with. Hope it works for y'all.

Looks good @wbobeirne will try it out and report back

I actually went about this how @Mark Nielson mentioned in http://drupal.org/node/996606#comment-5299900 before finding this thread. I did go ahead and test the patch though on D6 and it worked as expected. For sites with lots of contexts keeping it in one option like this makes things a little bit easier to deal with from a UX perspective.

Just in case anyone needs the same functionality that I did, I've updated the functionality so you can negate multiple roles rather then just one. Its on the 7.x version but the code is the same. Thanks to wbobeirne for the original patch!

Patch in #18 updated to apply cleanly against latest code. Also bumping version to 7.x, since thats where new dev work should go.

Last patch had a mistake (duplicate execute() function).

The patch is so perfect, thank you Chappo and mrfelton!

Now can easily negate a role for example user is 'authenticated' but not 'premium'.

Patch works(ish). Doesn't apply cleanly to the latest Dec 7 dev or stable. Probably needs to be rerolled using the latest version. Otherwise the actual functionality works great.

I just applied the patch in #20 manually to the latest official release (7.x-3.0-beta6), and it works great, thanks!

Here is an updated patch, and instructions if others find patching daunting.

I used to think I couldn't possibly patch a Drupal module, but actually three commands from the command line is all it takes. You need to have Git installed on your computer:

• git clone --recursive --branch 7.x-3.x http://git.drupal.org/project/context.git
• cd context
• git diff > context-negate_user_roles-996606-24.patch

The first command you find by clicking 'Version control', right under the title on the Context module main page. Select '7.x-3.x', click 'Show' and copy the lines below and run them, one after the other. Do the updates in the module code and execute the third command, which will create the patch. In this example 996606 is the issue number and 24 is the issue page post number, which will be your post, including the patch attached. That's it!

EDIT: The format of the attached patch has got the wrong syntax, but I can't update it. The example above should be correct though. Sorry about the confusion.

You're right, I just assumed the name syntax in the patch by mrfelton was correct, thanks for the heads up. I am resubmitting the renamed patch, let's see it if it's picked up this time. I will update my erroneous tips above when (if) it works :-)

That makes sense, the patch in post #19 doesn't seem to have been tested by the automated test bot, even though the name of the patch looks correct.
I get an "Access Denied" when I try to access that automated testing page (also, I can't see the tab), but I believe you :-)

Yeah, you probably have an elevated overall access level due to that. And it does explain why patches sometimes are test-botted, seemingly erratically, and others aren't :-)

It is kinda odd though, that auto-testing hasn't been activated for all contributed modules automatically, but there is probably a good explanation for that.

The patch above works but needed a few small fixes:

• The "if ($options['negate_role'] == 0) {" line gave an error for any context that had a role definition prior to the patch being applied.
• Per the Drupal coding standards, booleans should be spelled in uppercase.

This patch fixes both issues.

I took a slightly different approach to this for one of my sites. I needed a context that had both a Role condition and a Not Role condition. So I made a new condition for the not-role part: https://drupal.org/sandbox/petermallett/1962466

#32 working

I just used the option stated in https://www.drupal.org/node/580324#comment-4401174 and whilst it is not really standard it did work.

my use case was to exclude 1 taxonomy term, whilst still allowing the user to add more taxonomy terms without having to go add them to the context each time.

would be good if a negate button was able to be integrated :)

Thank you for this! #32 works like a charm.

Thank you for this! #32 works for me.

#32 works great! RTBC!
Is there an active maintainer who includes this in the next dev release?

Can we have tests for this, please.

Patch in #32 works for me. Thanks! Please commit to dev version!

hi

on drupal 7.53 #32 works for me too.. Just for infos (not in all cases) : it may be necessary to flush cache (drush cc all) to make appear the checkbox

thanks for the nice work

#32 works on 7.64.

Please commit to dev version.

In #63 a maintainer requested that test coverage be written, so putting this back to "needs work".

Adding tests