Toastmaster not able to print introductions

Ok, could you provide a screen capture of the problem screen?

You provided a screen capture of the ok screen, which I am already familiar with. I need to see the problem screen.

I have logged in as one of your members assigned as the toastmaster and I am still not seeing an issue. I need to see the screen capture of the problem to make sure I know what I should be looking for.

This seems like an elusive issue. Also, the code is set up such that if the print icon is missing then there should not be a speech intro box there either... the two are shown or hidden as one "unit".

Can you log in as Luke Arneson? He is the one that is having the issue.

Can you log in as Luke Arneson? He is the one that is having the issue.

Great idea!

That helped me solve this mystery.

This problem is the result of a design limitation... no really a true bug, but a weakness in the method used to determine who the Toastmaster is for a particular meeting agenda. Not my design (a prior developer), but an issue that I will need to address with a feature change in the future.

The problem has to do with the text matching that is used to find the role corresponding to the Toastmaster so the identity of the Toastmaster can be determined. Text matching is a weak method for doing this, because no matter what pattern and logic is used for the matching, usually sooner or later somebody will come up with an exception to the pattern matching rule that breaks it. (too many variables to try to match and exclude for)

In this case, you have two roles, Introduction of Toastmaster and Toastmaster, and the code looks for the first occurrence of a role containing Toastmaster, unless you keyword the role (put asterisks around the words that actually identify the role title). In your case, the person assigned to "Introduction of Toastmaster" was being found as the Toastmaster, *not* the role called Toastmaster.

While you may consider this to be a bug, as I note above, I consider it a design flaw that there is not an easy fix for except to redo how the role titles are flagged for internal processing. We have had a number of issues with the text matching approach, and I don't want to keep putting band-aids on a bad approach.

Since this design flaw is not something that is going to get fixed quickly (will take a good bit of work and a feature change-out), I can only offer you a workaround.

For now, the workaround for you is just to put asterisks around the Toastmaster role in your agendas, so that it gets found first as the Toastmaster as opposed to the Introduction of Toastmaster role.

OK, I opted to change the first role to Introduction and keep Toastmaster the same. Sorry it took so much explaining, but it is hard to find out exactly what is causing the issue when I, myself didn't have it. Thanks so much for the answer.