Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

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

  • lawlyet
    Participant

    @lawlyet

    Hey, you managed to put up a very beautiful website! Congratulations!

    Have you tried Siteground? They do have PHP7. I’m running their shared hosting plan, and after some issues with their terms about number of processes, executions and time, I faced the beast and started to get my hands dirty, removing all plugins, templates, messing with the configuration, putting a default wp template (twenty seventeen), creating my own child theme and messing with functions.php first and then modifying css and php files myself. I have never been a wordpress developer… Not even a php programmer… Just started messing with it on my own, for necessity (and, after a little time, for fun)… Now, I have a website with almost zero plugins (only the essentials), running on php7, http2 and moving in the speed of light, with the lowest server consumption ever…

    My advice: dont be afraid of getting your hands dirty.. the code is there, also the documentations, sites, forums, blogs and all kinds of resources 😀


    lawlyet
    Participant

    @lawlyet

    This error is showing up to many websites. A google search for “PHP Warning: Creating default object from empty value in /wp-content/plugins/buddypress/bp-groups/classes/class-bp-groups-member.php on line 1170” returns almost 5500 results…

    And if you search for “PHP Warning: Creating default object from empty value in class-bp-groups-member.php on line” (removing line number and the path of the file from the results, you get some something like 337000 results.

    My site is also showing this message, and I already removed all plugins and themes, running the latest version of WP, BP and BBPress with Twenty Seventeen template.

    I guess it may be a problem with php, or maybe with chrome and chromium… Maybe it is time to start working on this issue.

    I already added the following in my functions.php:

    /* Remove errors if any */
    error_reporting(E_ERROR | E_PARSE);
    /* End remove Errors */

    it’s not the ideal. there is also the better option to add some lines in your wp-config.php, to do a proper debug and get it in a log file, instead of showing it in the site.

Viewing 2 replies - 1 through 2 (of 2 total)
Skip to toolbar