unexpected T_GLOBAL error?

Capoeirista

Parse error: syntax error, unexpected T_GLOBAL in blah blah

Hi There -

Am on a Drupal site and have run into the above error with the following code:

<?php if (module_exists('flatforum')) { ?>
      <span class="author-role">
        <?php print t('') . ' ' . GLOBAL $user; print $user->role; ?><br />
      </span>
    <?php } ?>

The error is on the line that says "print t() . ' ' . global etc.

I've tried changing it to this, but really have no idea what I'm doing. I don't get the error anymore, but nothing prints either.

<?php if (module_exists('flatforum')) : ?>
      <span class="author-role">
        <?php global $user; ?>
        <?php print t('') . ' ' . $user .  $user->role; ?>
        <br />
      </span>
    <?php endif; ?>

I'd be so grateful for any help you can give me. Happy New Year everyone!

laserlight

I've tried changing it to this, but really have no idea what I'm doing.

In terms of syntax, your change is correct.

I don't get the error anymore, but nothing prints either.

That implies that the $user variable does not exist. Set error_reporting to E_ALL in php.ini to get a better view of the error.

Capoeirista

Thanks for replying. I hope something terrific happens to you this week.

Error reporting is set to E_ALL-E_NOTICE.

Will look into the status of the $user variable. Thanks!

What does this error normally mean? When I was hunting, there didn't seem to be a consensus. Is there a central place where errors are listed? (php 5)

Thanks again and happy new year!

bradgrafelman

Capoeirista wrote:
What does this error normally mean? When I was hunting, there didn't seem to be a consensus. Is there a central place where errors are listed? (php 5)

Well, there is a sticky dedicated to these general types of errors (Parse error: syntax errors) located here in the General Help forum.

Usually the culprit of these errors is a typo - a missing ending quote, semicolon, or brace leads to the parser finding commands/etc. in unexpected places, thus the exact error message can vary. I don't believe there is a central location listing all error messages; the error message itself gives you as much information as the PHP parser can with the code it was given, and it's up to you to figure out what the exact cause is.