TOPIC:

Hi -

I asked about this before but the problem persists.

I have set my default new agenda Toastmaster of the Week role to "The person assigned to this role can edit this meeting agenda NEW!" (Box checked.)

When I assign the TOW role and save, I can see that the edit box is checked.

However, when the non-admin TOW role holder logs in and attempts to edit a role, such as adding a theme of the week, upon saving, the editing pencil is no longer available and that TOW can no longer edit any roles.

The same thing happens when a member logs in, claims the TOW week role and saves it. Editing becomes disabled.

I made a video of the problem but your system doesn't allow uploading of mp4s, so you can see the video here:

NickNichols.com/fth

Please advise.

Thanks.

Nick Nichols
DTM/VPE club 4182

P.S. I set up a dummy member named All Club Members to test the issue on the 4/12 agenda.

Do NOT have the TOD change the role they are in. They way you are doing it changes the role.
The wording is the key and if they add the theme they change the wording.

Put the theme in the agenda header or in a separate role called theme of the day. Then they can change it and not change their role.

To make sure the agenda prints on one sheet, I use the "Role / Agenda Item" field to add variable items, such as the weekly theme, Word of the Day, speech title, etc. Do I understand that a non-admin TOW cannot edit this line?

Doesn't matter who it is, you can not change the bold line and maintain edit ability.

Try putting asterisks around the role name: *Toastmaster*: Theme......
I’m not able to test that right now, but it might work

Thanks. Not to belabor the point, but I can edit the "Role / Agenda Item" field as admin or TOW without losing editing capability. May I respectfully suggest that you allow non-admin TOWs the ability to edit that field when you are in the next update mode? Thanks for all you do. As a webmaster myself, I know how much work it can be to maintain a CMS site.

As Admin or VPED you can do what ever you want on the agenda.

It is the TOD that will have the issue. Do not change the Bold line or the switch will have to be reset by the admin or VPED

Thanks, I will try that.

Ok, what is being described here is *not* as designed and implemented.

You should be able to put *anything* in a role title and have edit rights as long as the This role can edit... checkbox is set.

Unfortunately, when the TOW - who is authorized to edit by default - edits and saves the "Role / Agenda Item" field for TOW, editing access is lost. See the video that illustrates the issue here: NickNichols.com/fth

Ok, let me look into this... It does seem like there may be an issue here.

Thank you.

Ok, thank you for your report, patience, and persistence. I did not initially pay much attention to this topic because your screen cast link redirected to a page with an advertisement on it, so I thought you were doing forum spam. (keep that in mind for the future)

For the lurkers, the issue was that the agenda editor button visibility was not getting properly changed when someone signed up for a role that had edit rights set for it. Additionally, the edit rights setting for specific roles was getting lost on agenda item updates.

Both of these have been fixed.

However, please keep in mind for the future that only *Agenda Creators* (identified via Access Settings... usually the VPED) can change the edit rights for specific agenda roles. This is by design, so that meeting Toastmasters do not arbitrarily give edit rights to all the other roles in an agenda. Typically, clubs will decide which roles should be able edit agendas as a matter of club policy, and not leave that to the whims of a particular meeting Toastmaster.

So if you want to change the name of a role w/ edit rights to "foobar", that will correctly work now and the edit rights will not be lost.

Thanks for taking a look and fixing this. BTW, my link on #68149 points to a page on my website that contains the link to the video I made to illustrate the issue and is not forum spam. Please see the screenshot.