WordPress.org

Ready to get started?Download WordPress

Forums

WP MediaTagger
[resolved] Unexpected '}' in mediatagger-admin.php on line 846 (11 posts)

  1. windyjonas
    Member
    Posted 2 years ago #

    I installed version 3.1 and got the following error message when I clicked Settings -> MediaTagger:
    Parse error: syntax error, unexpected '}' in /path/wordpress/wp-content/plugins/wp-mediatagger/mediatagger-admin.php on line 846

  2. phd38
    Member
    Plugin Author

    Posted 2 years ago #

    What's your PHP version ?

  3. windyjonas
    Member
    Posted 2 years ago #

    5.3.?

  4. phd38
    Member
    Plugin Author

    Posted 2 years ago #

    could you try with this version ?

    http://downloads.wordpress.org/plugin/wp-mediatagger.zip

    Did you have the problem with the plugin version 3.0 or 3.0.1 ?

  5. harikaram
    Member
    Posted 2 years ago #

    Same problem on WAMP/PHP 5.2 and it persists when I replace it with the link referenced.

  6. Su
    Member
    Posted 2 years ago #

    Still seeing this under Ampps, running PHP 5.3.8 and WordPress 3.3.1
    Whatever it is, it isn't new. I've dug up older versions, and the problem exists as far back as the last version of this plugin as ImageTagger.

  7. Su
    Member
    Posted 2 years ago #

    I think this is just a dumb syntax issue. There are a couple of spots where the opening PHP tag is in short form, and if your installation is set up to disallow it, execution fails.

    You'll find them at these lines:

    • 814
    • 473 (way over around char 1062 of the line)

    At those two locations, just change the <? to <?php and the settings screen should load. Note: I'm only just starting to review the plugin, so no idea if something else is actually broken.

  8. wavepointmedia
    Member
    Posted 2 years ago #

    Line 814

    Was:
    <? } // end if ($display_options)

    Change to:

    <?php } // end if ($display_options)

    And it works fine.

  9. phd38
    Member
    Plugin Author

    Posted 2 years ago #

    I will include this fix in the next release - thanks for your contribution.

  10. windyjonas
    Member
    Posted 2 years ago #

    Thanks!

  11. phd38
    Member
    Plugin Author

    Posted 2 years ago #

    This is now fixed with version 3.2.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic