WordPress.org

Ready to get started?Download WordPress

Forums

Updated Today Banner
[resolved] Parse error (13 posts)

  1. Scott Grayban
    Member
    Posted 2 years ago #

    Parse error: syntax error, unexpected $end in updated-today-plugin/updated-today.php on line 218

    http://wordpress.org/extend/plugins/updated-today-plugin/

  2. Scott Grayban
    Member
    Posted 2 years ago #

    Parse error: syntax error, unexpected $end in wp-content/plugins/updated-today-plugin/updated-today.php on line 279

    plugin is worthless

  3. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    Hey Scott, sorry for any errors. I am trying to replicate it as we speak, what are your settings for the plugin?

  4. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    @Scott Grayban,

    I've tried this on 3 of my own sites now and can't replicate it. Have you tried uninstalling and re-installing it? Honestly it sounds like a bad download or something, it's showing errors for missing the ending } of functions which the installs I've performed haven't had this problem.

    I've done both direct copy from my development versions as well as installing from the repository. Was this an upgrade or a new installation?

    Just trying to iron out any details to try and replicate it at this point.

    Thanks,
    Chris

  5. Scott Grayban
    Member
    Posted 2 years ago #

    It's a new install with PHP v5.3.10.

    PHP is running as user using fcgid.

  6. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    @Scott Grayban,

    I'm banging my head against the wall here. Looked over my code a few times and I can't find something that would set off PHP into a downward spiral when running as fcgi. It's odd that it's showing in two different areas of the file. One in the admin, the other in the full file.

    I hate asking this, but have you tried it with a base install of WordPress, stock Twenty Ten or Twenty Eleven themes and only this plugin active? I'm trying to narrow down where the issue lies, but I can't get this thing to fail for myself, and converting my entire server over to FCGI isn't feasible at this point in time.

    I want to get to the bottom of this with your configuration so any more info you can provide me is much appreciated.

  7. Scott Grayban
    Member
    Posted 2 years ago #

    The site newly built -- just a week old using a twenty 11 theme.

    Parse error: syntax error, unexpected $end in /home/spokanewcnc/public_html/wp-content/plugins/updated-today-plugin/updated-today.php on line 279

    You must be missing a } or ?> someplace because that's why you would get this error in php.

  8. Scott Grayban
    Member
    Posted 2 years ago #

    deactivated all plugins then made sure twenty 11 stock theme use used then tried to activate your plugin and still same error.

  9. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    @Scott Grayban,

    I know what the error means, I just can't figure out why I'm not getting it on the 4 sites I'm using the plugin on, and you are getting it. I've downloaded the plugin multiple times at this point and am not experiencing this problem at all. Can you email me your version of the updated-today.php file that's on your server? I just want to narrow down a failed installation, I made a couple commits when making the new version (2.5) and wonder if something was caught in the process?

    chris at chriskdesigns dot com

    thanks Scott!

  10. Scott Grayban
    Member
    Posted 2 years ago #

    ok I'm emailing to chris at chriskdesigns dot com

  11. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    After working with Scott, this issue was resolved in version 2.5.1. The error was caused by a missing white space character between some opening PHP tags and the proceeding character and only affected users whose PHP.ini file had the short_open_tag parameter set to "Off"

    If the plugin has caused major issues with your site you'll need delete the plugin from your wp-content/plugins/ folder and reinstall the newest version of the plugin.

    Sorry about this one guys.

  12. Chris Klosowski
    Member
    Plugin Author

    Posted 2 years ago #

    Marking as resolved, Scott if you feel otherwise please let me know.

  13. Scott Grayban
    Member
    Posted 2 years ago #

    Opps forgot to close this. All is good now Chris.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic