Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Uncanny Owl

    (@uncannyowl)

    Hi zenview,

    Before we investigate further, can you confirm that you’re using PHP 5.6 or higher? That’s the minimum recommended for WordPress. You will definitely get this error if you’re using PHP 5.2. It would also be great if you can confirm that you’re running LearnDash 2.2 and the latest version of WordPress.

    Thanks!

    Thread Starter zenview2000

    (@zenview2000)

    Hi Uncanny Owl:
    Thanks for your reply. I took a look and I’m currently on PHP 5.2. I can upgrade, but it seems like the best I can do with my hosting service (GoDaddy) is PHP 5.5 for Linux. I understand that your requirements are 5.6, but will I get any functionality with 5.5? I asked GoDaddy when they would move to 5.6 and they couldn’t/wouldnt tell me.

    Other than that, I am on LearnDash 2.2 and the latest version of WordPress

    Plugin Author Uncanny Owl

    (@uncannyowl)

    Hi zenview,

    Thanks for confirming! Great to know that is the problem. Yes, you can use PHP 5.5. The plugin should work with anything over 5.3; 5.6 is just recommended by WordPress and by us. As an aside, GoDaddy shared hosting may not be the right fit for a complex LearnDash site.

    Thread Starter zenview2000

    (@zenview2000)

    Hi Uncanny Owl:
    Thanks! Good to know. I’m nearing the end of my hosting plan with GoDaddy so now is the time for me to make some decisions. Can you say more about why they may not be the best fit for a complex LearnDash site? In the short term, my needs are simple, but if I will be growing/expanding, I’d rather do the migration now. What tradeoffs/considerations should I be thinking about?

    Plugin Author Uncanny Owl

    (@uncannyowl)

    We tend to see LearnDash sites have memory allocation errors and experience slow performance on shared hosting (that isn’t optimized for WordPress). For us, trying to work around the constraints of shared hosting isn’t worth the effort.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘fatal parse error’ is closed to new replies.