WordPress.org

Forums

Simple Subscribe
[resolved] Parse Error after 1.3 installation -- plugin broken. (13 posts)

  1. AFOdom
    Member
    Posted 2 years ago #

    I updated the Simple Subscribe plug-in to v1.3. I am using WordPress v3.9.1. Like many others, I am getting the following error instead of the subscription form:

    Parse error: syntax error, unexpected '[' in (personaldataremoved)/wp-content/plugins/simple-subscribe/libs/SimpleSubscribe/Frontend.php on line 49

    If the fix isn't incoming soon, is there a way to revert the update?

    https://wordpress.org/plugins/simple-subscribe/

  2. czeller
    Member
    Posted 2 years ago #

    Same here- hoping for resolution-

  3. morgainebrigid
    Member
    Posted 2 years ago #

    Me three!
    I really need this to work. Please fix it.

  4. tanaylakhani
    Member
    Plugin Author

    Posted 2 years ago #

    Hi,

    Do you still receive the error after the recent update?

  5. AFOdom
    Member
    Posted 2 years ago #

    I'm in the middle of a web hop writing event, so I won't be testing any updates until it's over. I can't afford to have a fail and deal with the roll back. Maybe others will have time to test it.

  6. tanaylakhani
    Member
    Plugin Author

    Posted 2 years ago #

    Okay. Others can shed some light on issues you face after recent update. If you still get, please let us know.

    A quick fix would be: find this line
    $email = $form->getValues()['email'];

    Change that to $email = $form->getValues()->email;

  7. morgainebrigid
    Member
    Posted 2 years ago #

    Installed the update. Still got an error:

    Parse error: syntax error, unexpected '[' in /home/u420523890/public_html/wp-content/plugins/simple-subscribe/libs/SimpleSubscribe/Frontend.php on line 55

    However, I tried the quick fix posted above and it worked fine.

  8. tanaylakhani
    Member
    Plugin Author

    Posted 2 years ago #

    Tried the above fix?

  9. eszter-maura
    Member
    Posted 2 years ago #

    Dear tanaylakhani,
    I had the same issue and tried the fix you proposed.
    Now I get this error:
    "Fatal error: Namespace declaration statement has to be the very first statement in the script in /home/[personal/data]/wp-content/plugins/SimpleSubscribe/libs/SimpleSubscribe/Frontend.php on line 12"

    I checked line 12 and that is indeed the very first thing after the opening php tag and some /*remarks

    Can you help me with wht I'm doing wrong? I'd really like to get this work, could not find anything as a substitute.

    my site: eszter-maura.tk

  10. tanaylakhani
    Member
    Plugin Author

    Posted 2 years ago #

    Hi @eszter-maura

    namespace should be the first statement in the file. Please check and remove any white spaces after the comment line or before the comment starts

  11. eszter-maura
    Member
    Posted 2 years ago #

    Hi tanayakhani,
    I tried what you say took out some spaces, but it still does not work.
    this is the EM:
    "Fatal error: Namespace declaration statement has to be the very first statement in the script in /home/eszham/eszter-maura.tk/wp-content/plugins/simple-subscribe/libs/SimpleSubscribe/Frontend.php on line 10"

    and the first 11 lines:

    <?php
    /**
     * This file is part of the Simple Subscribe plugin.
     *
     * Copyright (c) 2013 Martin PĂ­cha (http://latorante.name)
     *
     * For the full copyright and license information, please view
     * the SimpleSubscribe.php file in root directory of this plugin.
     */
    namespace SimpleSubscribe;

    I even tried taking the part between the /* */ out, but the only thing that changed was that the EM mentioned "line 2".

    If you have any further ides, I'd be glad for help.

  12. Beagle Bookeeping Services
    Member
    Posted 2 years ago #

    I installed this plugin today and got the following error straight away:

    Parse error: syntax error, unexpected '[' in /home2/beaglebo/public_html/wp-content/plugins/simple-subscribe/libs/SimpleSubscribe/Frontend.php on line 55

    Any ideas on how this is to be fixed yet?

    Thanks.

  13. tanaylakhani
    Member
    Plugin Author

    Posted 2 years ago #

    It is fixed in recent update. Let me know if you still get the issue.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.