matthewrlee wrote:It took me a while to figure out LUWS -Support stands for Local Unit Website Support - Support (I think).
Actually, LUWS is L
ite. For the small percentage of LDS members who have made it to this site, there is a list of acronyms here (found at the very, very top of this site): http://tech.lds.org/index.php?option=com_content&task=category§ionid=12&id=35&Itemid=84
But it is a valid point that hardly anyone outside the membership of this site would know these acronyms.
matthewrlee wrote:If an abbreviation slows down comprehension it is best not to abbreviate. It may also help to replace "lookup functions" with "search functions." May be it is technically a lookup function returning values but again, 95% of current and future users will not understand.
I think "search function" gets further from the intended meaning. Being a developer, I think I know what is trying to be stated. It appears it would have been a time consuming call to the Church databases to know if the currently logged in user has administrative privileges just to display a button on every page of the site. So the developers opted to always display the button, and then have the check happen only when they actually click the button (which most people probably don't do or don't even see the button).
I agree the wording is awkward. I imagine that PR or Legal (or whichever group is applicable) should probably come up with the correct text for this screen. It definitely sounds like developer lingo.
To the Church developers, I don't know if I understand why you can't develop a UI smart enough to make the call only once. Perhaps you've already thought of this and there is some issue I don't see or haven't thought of, but I would think you could check once and then put the result on the session. I can see why it may be an issue with concurrent users logged into the site; maybe check on login every time and keep that for the rest of the session. Then if somebody grants administrative rights, you trigger the newly upgraded user to have to log out and login to achieve the new privileges. I don't know, just some thoughts...
Also it should be taken into consideration that this code was probably written some time ago and perhaps there is more experience now with this issue; also, it very well could be that this is fixed in LUWS version 2.0 anyway.