• GoDaddy Community
  • Websites + Marketing | Website Builders
  • Websites + Marketing | Website Builders

    cancel
    Showing results for 
    Show  only  | Search instead for 
    Did you mean: 

    Has GoDaddy made ANY changes to their Shared cPanel PHP Hosting in the last few months?

    Dear GoDaddy and Community,

     

    We have a vBulletin 4 site that we had migrated a while ago to GoDaddy hosting.  Everything was going smoothly until recently when we noticed the following PHP appearing at the top of the Forum:

     

    ---

    Warning: Illegal string offset 'name' in [path]/includes/functions.php on line 6570

    ---

     

    We googled the error, and every result that comes up mentions that this error appearing suddenly is caused by changes made by the Hosting company, some even mentioning changes in the PHP version by the Hosting company as the cause.

     

    So that begs the question, has GoDaddy made ANY changes to their Shared cPanel PHP Hosting in the last few months?

     

    To be clear, we have not made any changes on our end to the site this year when the error suddenly started appearing.

     

    Please advise and thank you for your time.

    2 REPLIES 2
    Moderator
    Moderator

    Re: Has GoDaddy made ANY changes to their Shared cPanel PHP Hosting in the last few months?

    Hi @GDCustomer, thanks for posting.

    I'm not aware of any change that would cause an issue like this, but you can change your PHP version in cPanel to a different version to see if that resolves the issue. See:

    https://www.godaddy.com/help/view-or-change-your-php-version-16090

    ^Gary

    Gary - GoDaddy | Community Moderator
    24/7 Support | Check System Status
    Retired
    Not applicable

    Re: Has GoDaddy made ANY changes to their Shared cPanel PHP Hosting in the last few months?

    Hey there,

     

    That warning appearing is generally the result of the PHP version being updated on the server. If that error appeared out of the middle of nowhere. You can always change your PHP versions in your cPanel, or you can edit the config.php of your vBulletin and add

     

    error_reporting(0);

     

    This will disable error reporting on the public side of things. You can still find your php errors within the error_log however.

     

    The problem rests with vBulletin and code becoming out of date or error reporting settings being changed. It shouldn't impact your forum, and can be easily suppressed.

     

    You can certainly google more on the matter!

     

    Roger