• Resolved David Decker

    (@daveshine)


    Hi there!
    I would really try out your plugin as it looks very promising. However, I’ve got numerous fatal errors upon tried activation. Tried on 2 different test sites on different hosting providers. Both the same. Both sites are on PHP 5.3 if that matters.

    Don’t know what that is.

    Thank you, Dave ??

    https://www.ads-software.com/plugins/client-dash/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter David Decker

    (@daveshine)

    Sorry, the same with v1.6.2 — any tips for me?

    Plugin Contributor joelworsham

    (@joelworsham)

    Hmmm, that is strange. I don’t seem to be able to replicate the situation.

    Could you please give me a little more info on your specific situation?

    -What does the fatal error(s) say?
    -What other plugins do you have activated on your site?
    -What version of WordPress are you running?

    Plugin Contributor joelworsham

    (@joelworsham)

    We have found the error. The error is caused because of some syntax used in the plugin that is only supported in php 5.4 and up. We will be changing this today and releasing a patch with some other minor fixes as well.

    Expect it by the end of the day.

    Thank you for your patience as we resolve this situation!

    Plugin Author Kyle Maurer

    (@brashrebel)

    Hey @dasveshine! Has your problem been fixed? We’ve released a patch which makes the plugin compatible with PHP 5.3. Let us know!

    Plugin Author Kyle Maurer

    (@brashrebel)

    Since we haven’t heard back and have issued an update which fixes this problem for anyone using PHP 5.3, I’m going to close this topic. Please let us know of any other issues and have a great day.

    ihavegotit

    (@adminihavegotitcom)

    Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM in /home/visitbab/public_html/wp-content/plugins/client-dash/client-dash.php on line 634

    were can i download the patch for the latest version

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal error(s) when trying to activate (1.6.1)’ is closed to new replies.