Viewing 15 replies - 1 through 15 (of 15 total)
  • Same issue here after updating to WP 4.4.2. I’m going to try to go back to the previous version as well.

    Andrea

    (@andreanapier1985)

    I use wpremote.com and I foolishly updated 100 sites – all of which broke because of this plugin. Never using this plugin again!

    Same problem here. I just FTP’d into the plugin, deleted that entire function and it’s working for now. Please fix!!

    Hi Guys,
    I have the same issue how do i fix it?

    @rockyuk,
    I just went back to the previous version. I had it backed up.

    I tried that but i am still getting the same error ??

    Same problem here as original post when upgrading Erident to v3.4 on WordPress 4.2.2. Reverted Erident to v3.3.1 and will wait to see if this thread is acknowledged and a solution provided.

    Ok, i had a backed up version of the plugin but still can’t get it to work, is there a temporary work around if so what is it?

    Plugin Contributor Libin

    (@libinvbabu)

    Hey guys,

    I’m really sorry about this. The new function I added is only compatible from PHP 5.3
    So for all who are on older version of php will getting this error.

    I will release a new version soon with a code fallback for users who are on older version of php. I will keep you guys updated.

    For a quick fix, if you can upgrade your php version to the latest, everything will works fine.

    Thanks for the patience.

    Plugin Contributor Libin

    (@libinvbabu)

    Guys,

    I just released a new version(3.4.1) with a work-around for the function. Please update the plugin and let me know if it is throwing anymore errors. I tested on my server with older php version and it is working fine.

    I apologize that many of you are having errors with just having a lower PHP version. PHP 5.3 was released in June 2009 so this is something that has been throughly tested and is ready for production use by most standards. I request everyone to upgrade your php version to the latest.

    Feel free to comment back or open a new ticket if you are having any issues with the plugin.

    Thank you.

    Just updated to 3.4.1 as soon as the plugin activated it erred and disabled. I also noticed a very long time the site was in Maint Mode and this never has happened before. https://www.savealator.com – Going back to 3.4 until this 3.4.1 issue is resolved.

    Plugin Contributor Libin

    (@libinvbabu)

    Hey Thomas,

    Can post here the error shown?
    Version 3.4 has a compatibility issue with php and it is fixed on 3.4.1

    I updated to Erident 3.4.1 and that fixed the error that I was seeing (Unexpected T_FUNCTION at line 66).

    I then also checked with my hosting provider, and, sure enough, I was on PHP 5.2. I manually updated to PHP 5.3, and the error did not reappear. All appears to be working as expected, and I can only assume that the old version of PHP (5.2) was the original source of the error.

    I appreciate the heads up on the PHP version since I otherwise would never have checked. Most other updates to the software used on the site either occur automatically or generate a notification to me from the hosting provider (GoDaddy) that an update is available. Apparently, that is not the case for PHP, which must be monitored and updated manually by the site administrator (me).

    Thanks!

    This install is on an MS Azure platform. When it doesn’t like plugins i.e activation or conflict..it does not gracefully deactivate the plugin…it basically blows them up and deletes them from the install.

    I did verify the platform is running PHP5.4 and the previous 3.4 runs fine, as son as I update to 3.4.1 …I get the Maint Window on the Front end….the plugin then shows it successfully updated and then bam….it’s Error and deleted…..

    Plugin Contributor Libin

    (@libinvbabu)

    Thanks @seeker2734 for the confirmation.

    @thomas, your issue seems to be a different one. Please open a new ticket for further investigation.

    Thanks.

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘syntax error, unexpected T_FUNCTION in line 66’ is closed to new replies.