Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Adam

    (@adamsassets)

    I assume you are using something like JustHost, where I believe they don’t update there PHP, although you might be able to manually.

    The code uses “goto” which, as I have just read, requires at least PHP 5.3.
    Because I aim to make things very compatible, I will fix this problem today for you.

    Thank you for the feedback. This will be very helpful to the success and reach of this plugin.

    Plugin Author Adam

    (@adamsassets)

    Here is a link to the special PHP 5.2 and under version: http://www.adamsassets.com/aio-cache-php-no-5.3.zip

    Please note, this is a temporary fix, and will be a little bit less in performance than the original. However, I would highly recommend you update to at least PHP 5.3+, due to the better security and performance of PHP 5.3+. I would recommend you ask your host how you can update PHP to 5.3 or greater.

    Thread Starter ramonjosegn

    (@ramonjosegn)

    OK, thanks, I have a partnet for webhosting, are dedicate servers, I ask to my partner whats version of PHP are running, thanks for support

    I think there is not good idea use the last versions of PHP, a lot servers always waiting some time for update

    Thread Starter ramonjosegn

    (@ramonjosegn)

    I look at the PHP version in running my webhosting, there is PHP 3.5, I think the error it could a conflict with another WordPress plugin…

    Plugin Author Adam

    (@adamsassets)

    Well, the error “Parse error: syntax error, unexpected T_STRING in /home/tudinero/public_html/wp-content/plugins/aio-cache/lib/class.minipress.php on line 29” refers to a line of code on line 29 in aio-cache/lib/class.minipress.php and that line of code is “goto output;”. I am running on a business class server with PHP 5.3 as well.

    To help me do some troubleshooting, can I have a list of the plugins you are using, as well as the theme you are using, so I can replicate your situation?

    Plugin Author Adam

    (@adamsassets)

    Update v1.1 fixes this problem.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Fatal ERROR ooppps!!’ is closed to new replies.