It may help to define what you are trying to do better, before hunting for errors in code. Perhaps your approach is sound, but not in line with your functional expectations.

Interpretation: You are trying to find out if $author is in the @admin_users list, and return true/false accordingly. 
if (grep { lc eq lc($author) } @admin_users)
{
     print "$blah";
}
else
{
     print "$uber_blah";
}

[download]
Of course, I would make sure that you prune your @admin_users list, making it all neat and tidy before feeding it to this routine. For example, you will want to strip off extraneous characters, such as dangling spaces and newlines.
@admin_users = map { s/\s+//; $_ } @admin_users;

In reply to Re: Is for the wrong choice here? by tadman
in thread Is 'for' the wrong choice here? by jerrygarciuh

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.