Skip to:
Content
Pages
Categories
Search
Top
Bottom

Admin Area Turned to Persistent Blank Page


  • Tranny
    Participant

    @tranny

    9 years, 10 months ago

    After activating BuddyPress, my admin area turned to a blank screen. Launching FTP client and renaming the buddypress subdirectory solved it immediately, but no matter what I tried (deleting the files, reinstalling, cleaning up the transient records from the database, etc), re-activating BP immediately results in everything behind wp-admin turning to a blank screen.

    Search through support forums here lead to no solution. There are recommendations to increase the available memory, but I’m on a very powerful dedicated server with more than 50% memory available. I had this confirmed after consulting with my webhost.

    What’s a guy to do to make BP work?

    PS – I run a very busy website with 10 Million uniques a month, 20% bounce rate, 12 pages accessed per visit, 480k registered members and a new comment made approximately every 2 to 3 minutes. The server is powerful enough to handle this load of traffic and have a lot of extra power for spikes. I’m sure the problem is not with insufficient server resources. Help?

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

  • shanebp
    Moderator

    @shanebp

    9 years, 10 months ago

    Anything in your error logs?


    Tranny
    Participant

    @tranny

    9 years, 10 months ago

    I’ll take a look at error logs. What should I look for?

    Also, I looked up server’s phpinfo. My current memory_limit is 128M.


    shanebp
    Moderator

    @shanebp

    9 years, 10 months ago

    Look for php errors re WP.
    Try doubling or quadrupling your memory limit


    Tranny
    Participant

    @tranny

    9 years, 10 months ago

    I bumped memory limit from 128MB to 512MB – as I expected, it did not resolve the issue. Activating the plugin results in the blank screen and the whole admin area returns nothing but blank screens from that point on. Renaming the buddypress subfolder resolves the problem as it deactivates the plugin.

    I honestly did not think memory limit had anything to do with the problem, but I wanted to try it nevertheless to have it confirmed.

    As for error logs – I learned from my webhost that we don’t have them enabled due to high traffic to the site. Daily logs were 2Gb in size.

    Are developers gonna consider looking into this issue? There must be a deeper underlying issue. Bumping up memory limit is not a solution. If memory limit was a potential issue, it would have already demonstrated itself as such as I watched my site grow, and tried a number of plugins over time.


    shanebp
    Moderator

    @shanebp

    9 years, 10 months ago

    Without an error message, there isn’t much anyone can do to help you.
    If your error log was 2GB per day, then you have a lot of other problems.

    Try turning on wp_debug.


    Tranny
    Participant

    @tranny

    9 years, 10 months ago

    I got this in the debug.log file:

    [27-Jan-2015 01:16:12] PHP Fatal error: Call to undefined function bp_is_user_inactive() in /home/xxxxx/xxxxx.com/wp-content/plugins/buddypress/bp-core/bp-core-caps.php on line 264

    What does that mean?


    Tranny
    Participant

    @tranny

    9 years, 9 months ago

    Update released today. I go to update the plugin, hoping it would end the blank page, but the first thing I see after update is… blank page.

    This is obviously a persistent issue, reported by many users. It’s unfortunate nobody cares to address it.


    Mathieu Viet
    Moderator

    @imath

    9 years, 9 months ago

    Hi @tranny

    I’m sorry to read about the problem you’re having when activating BuddyPress. From what you’ve described it looks like a plugin or a theme is checking for a capacity very early in the process, well at least before the BuddyPress members component has been fully loaded.

    BuddyPress hooks ‘plugins_loaded’ at a 10 priority and define its components a little while after. So your target is a plugin, a theme, or a specific code direclty loaded in global scope that is doing a current_user_can() before the action ‘plugins_loaded’ has been fired.

    If you look at this page, you’ll see there are 3 actions fired before ‘plugins_loaded’ : https://codex.wordpress.org/Plugin_API/Action_Reference#Actions_Run_During_an_Admin_Page_Request

    Searching the cause of the problem won’t be easy, if i were you i’d do a back up of your entire site and would do some tests on a local server making sure the local server environment contains a x-debug client so that it would display the different functions called before the error appears.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Admin Area Turned to Persistent Blank Page’ is closed to new replies.

Topic Info

Topic Tags

Skip to toolbar