This will prevent issues if the roles already existed on the server for other (non-ClassDB) purposes.
Also, createGroupRole() is now called with lowercase role names. This prevents an issue where the roles were wrongly identified as not existing. This was because the parameter in createGroupRole() was referred to with $1, which quoted the role names, making them case-sensitive. This might not be the most ideal fix, depending on future plans or other factors, so please share your opinions here or on Issue #73.
These changes are related to issues #73 and #81
The three main ClassDB role names have had their names changed:
This will prevent issues if the roles already existed on the server for other (non-ClassDB) purposes.
Also,
createGroupRole()is now called with lowercase role names. This prevents an issue where the roles were wrongly identified as not existing. This was because the parameter increateGroupRole()was referred to with$1, which quoted the role names, making them case-sensitive. This might not be the most ideal fix, depending on future plans or other factors, so please share your opinions here or on Issue #73.