band of blades – Are Legion roles permanent or reassigned after every mission?

This comes up after the first mission, just as we are discussing who takes what roles. One of the question that comes up is “do we rotate this role, like characters?”. I’ve looked at the Chapter 3, about the roles in the Legion, but it does not say explicitly whether this is something every player can experience – by rotating – or something more permanently assigned to a player in a campaign.

My first guess is the latter, once a player choose a role, they stick with it – just as GM stays GM until the end of campaign. My reasoning would be since roles require bookkeeping, it would be wiser for one player to stick with the role, to avoid confusion.

So, are roles permanent to the assigned player or not?

user roles – Woocommerce Wcvendors – duplicate emails when Vendor approved

I am building a marketplace using WC Vendors on top of Woocommerce. The vendors apply by completing a form, which creates a user with the role ‘pending vendor’. As admin, I then click ‘approve’ or ‘deny’ by their username in the Users table in the backend.

However, when I click ‘approve’ on a user, the two emails that get sent (one to admin, one to the user) are each sent three times.

I’ve tried deactivating the template override for that notification, and the plugin I’d used to style up the emails. But nothing seems to stick.

What is the next step in diagnosing this? Has anyone come across this before?

Cheers, in frustration!

the one ring – Journey Roles when traveling through a mine (specifically Mines of Moria)

I am going to run a group through the mines of moria in a The One Ring game and I am unsure how to have all the roles work in such an environment.

Basic plot is that this group was hired by Balin to frequently deliver supplies. On this trip is when Balin has been killed and the goblins have killed the rest of that party. The PC party sees the horde of goblins from a distance and are going to go the opposite way when there is a light coming from behind (yes, the Balrog). So they flee into the passages where they have never been. Now they must escape the mines of Moria before the goblins choose a new king and they unite into a single horde. Until then they are dealing with tribes who’s main focus is not intruders they may or may not know about.

The guide role still works as intended as they will be choosing the directions and attempting to leave the mines. No, the guide is not going to know the mines or even have complete maps.

The scout role is giving me issues because their job is to set up camp and break new trails. I can see the setting up camp still (because rest is still needed even if your being hunted by orcs), but their not going to be making new tunnels. Anyone playing this role might feel left out compared to the importance of the guide.

The huntsman role is also an issue because their role is to find food. In this environment the party shouldnt split up so it would be mostly limited to deciding whatever they come across is safe to eat. Again, how to make they feel included compared to the guide?

The look out man role is as important as the guide. Observing the surrounds in the tunnels for ambush and all that.

What can I do for the huntsman and scout?

Can we define User roles to view specific customer groups?

Magento 2 Admin ACL panel use an authentication system and a robust system for create Access Control List Rules (ACL) which allows a store owner to create fine grained roles for each and every user in their here, we will find how it work and how to add ACL for our custom module.

Magento 2 Access Control List Rules
The Magento 2 Admin ACL resources are visible under the Magento 2 admin System > Permissions > User Roles area. When we click on the Add New Role button or access to a role.
In this resources tab, you can see a tree-list of all the available resources in your system. You can choose all Resource or some of them for this role and select the user for this role in Role Users tab. All of the user who belong to this role will be limit access to the resource which you choose. They cannot see and access to other one.
To Create Admin Admin ACL

Step 1: Create ACL rule

Step 2: Flush Magento cache

Step 3: Check ACL rule

Step 1: Create ACL rule
Now, we will see how to add our module to ACL role. We will use a previous simple module HelloWorld to do this. As in the Admin Menu and System Configuration article, you saw that we alway have a resource attribute when create it. Now we will register that resources to the system, so Magento can realize and let us set a role for them. To register the resource, we use the acl.xml file which located in app/code/{namespace}/{module}/etc/acl.xml. Let’s create this file for our simple Module:

File: app/code/Ced/HelloWorld/etc/acl.xml

<?xml version="1.0"?> 
<config xmlns:xsi="" xsi:noNamespaceSchemaLocation="urn:magento:framework:Acl/etc/acl.xsd">
        <resource id="Magento_Backend::admin">
            <resource id="Ced_HelloWorld::helloworld" title="Hello World" sortOrder="51">
                <resource id="Ced_HelloWorld::post" title="Posts" sortOrder="10"/>
                <resource id="Ced_HelloWorld::helloworld_configuration" title="Configuration" sortOrder="99" />
            <resource id="Magento_Backend::stores">
                <resource id="Magento_Backend::stores_settings">
                    <resource id="Magento_Config::config">
                        <resource id="Ced_HelloWorld::helloworld_config" title="Hello World"/>

Our resource will be placed as child of Magento_Backend::admin. Each resource will have an Id, title and sortOrder attribute:

Id attribute is the identify of this resource. You can use this when define resource in Admin menu, configuration and limit access to your module controller. This is a unique string and should be in this format: Vendor_ModuleName::resource_name.
Title attribute is the label of this resource when showing in resource tree.
sortOrder attribute define the position of this resource in tree.
After this done, please refresh the cache and see the result on resource tree.

Step 2: Flush Magento cache
Make sure it admin menu items are displayed on Magento 2 admin, you should try to flush Magento 2 cache.

Step 3: Check ACL rule
There are some place where we put the ACL resource to make it limit the access:

Admin menu: Put the ACL resource to hide the menu if it’s not allowed by store owner.

File: app/code/Ced/HelloWorld/etc/adminhtml/menu.xml

<add id="Ced_HelloWorld::helloworld" title="Hello World" module="Ced_HelloWorld" sortOrder="51" resource="Ced_HelloWorld::helloworld"/>

System configuration: Put the ACL resource to limit access to this section page.

File: app/code/Ced/HelloWorld/etc/adminhtml/system.xml

<section id="helloworld" translate="label" sortOrder="130" showInDefault="1" showInWebsite="1" showInStore="1">

We will use Ced_HelloWorld::helloworld_configuration in Magento 2 How to Create System.xml Configuration

With resource it also use on controller.

In admin controllers: Magento provides an abstract type MagentoFrameworkAuthorizationInterface which you can use to validate the currently logged in user against a specific ACL. You can call that object by use the variable: $this->_authorization. In the controller, you have to write a protected function to check the resource:

Example: File: vendor/magento/module-customer/Controller/Adminhtml/Index.php

protected function _isAllowed()

return $this->_authorization->isAllowed(‘Magento_Customer::manage’);


What does it mean by add an existing msdb role to one of the following SQL Server Agent fixed database roles?


To configure a user to create or execute Microsoft SQL Server Agent
jobs, you must first add an existing SQL Server login or msdb role to
one of the following SQL Server Agent fixed database roles in the msdb
database: SQLAgentUserRole, SQLAgentReaderRole, or

I understand that an existing login can be added to one of the above sql server agent fixed database roles.

But what does it mean by add an existing msdb role to one of the following SQL Server Agent fixed database roles?

plugins – Map Custom Registration Fields to WordPress User Roles

How do I map these custom fields to the user profile?

Desired Functionality:
if selected Consumer user role should be the ‘Default- WordPress Role
if selected ‘Wholesale Buyer’ user role should be ‘Administrator’

Here’s – What I have so far?

function iconic_get_account_fields() {
    return apply_filters( 'iconic_account_fields', array(
        'user_url' => array(
            'type'        => 'select',
            'label'   => __( 'Select Field', 'iconic' ),
            'options' => array(
                '' => __( 'Select Customer', 'iconic' ),
                1  => __( 'Consumer', 'Consumer' ),
                2  => __( 'Wholesale Buyer', 'Wholesale' ),
            'required'    => true,
    ) );
 * Add fields to the registration form and account area.
function iconic_print_user_frontend_fields() {
    $fields = iconic_get_account_fields();

    foreach ( $fields as $key => $field_args ) {
        woocommerce_form_field( $key, $field_args );

add_action( 'woocommerce_register_form', 'iconic_print_user_frontend_fields', 10 ); // register form
add_action( 'woocommerce_edit_account_form', 'iconic_print_user_frontend_fields', 10 ); // my account