Skip to:
Content
Pages
Categories
Search
Top
Bottom

Odd blank sections in WP admin after installing BP

  • @aran

    Participant

    14 years, 8 months ago

    1. Which version of WP/MU are you running?

    WordPress 2.9.2

    2. Did you install WP/MU as a directory or subdomain install?

    Directory

    3. If a directory install, is it in root or in a subdirectory?

    Subdirectory

    4. Did you upgraded from a previous version of WP/MU? If so, from which version?

    No – fresh install

    5. Was WP/MU functioning properly before installing/upgrading BuddyPress (BP)? e.g. permalinks, creating a new post, commenting.

    Yes

    6. Which version of BP are you running?

    1.2.3

    7. Did you upgraded from a previous version of BP? If so, from which version?

    No – fresh install

    8. Do you have any plugins other than BuddyPress installed and activated?

    No

    9. Are you using the standard BuddyPress themes or customized themes?

    The standard default theme, unmodified

    10. Have you modified the core files in any way?

    No

    11. Do you have any custom functions in bp-custom.php?

    No

    12. If running bbPress, which version? Or did your BuddyPress install come with a copy of bbPress built-in?

    Not running bbPress

    13. Please provide a list of any errors in your server’s log files.

    Haven’t managed to access them

    14. Which company provides your hosting?

    Rackspace

    ***

    The problem:

    After a vanilla install of WordPress 2.9.2, and an automatic install of BP 1.2.3, when I navigate to some sections of the WP admin section (including Add New plugins, and General settings) the Buddypress Admin navbar gets whited out, and the pages don’t finish loading – so, for example, on the General settings page there is no way to submit changes, and on the Add New plugins the collection of plug-in tags doesn’t get loaded.

    It doesn’t seem to be affecting the operation of the site in any other way, so I can live with it by fixing changes I want in General settings in the database instead – but it’s a bit worrying.

    Any ideas as to what might be causing it would be gratefully received…:-)

    I’ve uninstalled and re-installed a couple of times, and have got exactly the same thing every time so far.

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

  • @songv

    Participant

    14 years, 8 months ago

    I am experiencing the exact same issue! I’ve tried everything and cannot get it to work at all.

    @songv

    Participant

    14 years, 8 months ago

    Hey Aran, I could not get this to work at all with just regular WP, but after deleting and installing WordPress MU in its place, I was able to get BuddyPress to work with no problems. Very strange…because I was able to install BuddyPress with just a regular install of WordPress 3 days ago on another site.

    @jivany

    Participant

    14 years, 8 months ago

    If you look at the source of the page, does it look like it’s complete? That is, does the source for the setting page end with:

    </body>
    
</html>

    If not, it sort of sounds like the httpd process is getting killed while it’s generating the page. It would be really good if you could look in the server logs.

    @aran

    Participant

    14 years, 8 months ago

    That’s really interesting, songv – so it’s looking like a single WP clash with something in BP – but not being experienced by everyone?

    jivany, great call – your suspicions are exactly right, the source code is clearly not complete.

    I should have access to the server logs, but it’s not something I’m familiar with – do I just want to grab whatever I can, or look for some particular details?

    @jivany

    Participant

    14 years, 8 months ago

    Look in the error logs for anything that suggests why the page load failed to complete. Typically, you would load the page to reproduce the problem and then look in the logs for the most recent entries and see what they say. If you’re not sure, post them here and someone can probably offer some pointers.

    @aran

    Participant

    14 years, 8 months ago

    Haven’t been able to reply to this thread for some time, not sure why!

    ***

    I navigated to some of the pages that weren’t loading yesterday, and checked the log files – the php error file (which is the only one I could see) had these little gems:

    [21-Apr-2010 07:29:55] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1458
    [21-Apr-2010 07:29:55] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1458
    [21-Apr-2010 07:29:56] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1495
    [21-Apr-2010 07:30:06] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 18019 bytes) in /hafan/wp-includes/wp-db.php on line 478
    [21-Apr-2010 07:30:26] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 64 bytes) in /hafan/wp-includes/plugin.php on line 137
    [21-Apr-2010 07:30:41] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1458
    [21-Apr-2010 07:30:41] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1458
    [21-Apr-2010 07:30:42] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /hafan/wp-includes/class-simplepie.php on line 1495
    [21-Apr-2010 07:34:22] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 18019 bytes) in /hafan/wp-includes/wp-db.php on line 478
    [21-Apr-2010 07:34:27] PHP Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 64 bytes) in /hafan/wp-includes/plugin.php on line 137

    So the regular one seems to be the class-simplepie.php one – does that make any kind of sense?

    @jeffsayre

    Participant

    14 years, 8 months ago

    It looks like you need to increase the allocated memory limit for PHP. Depending on the way your hosting company has set up the servers, you might be able to do this yourself. If you’re on a shared hosting package, they might not allow you to increase the memory limit.

    I suggest contacting technical support at Rackspace and tell them about the error message. Then ask them what is set in the server’s php.ini file for the value of the memory_limit directive. If Rackspace allows for this value to be overridden by Apache, then you can easily tell php to use more memory by adding this to the very top of your .htaccess file.

    ### Set PHP Memory Directive ###
    php_value memory_limit 60M

    As a final check, make sure that your site is running PHP5. Although WordPress does run under PHP 4, it also runs under PHP 5 and that is always better.

    If this is all foreign to you, then perhaps Rackspace will do it for you.

    @aran

    Participant

    14 years, 8 months ago

    That’s gold, Jeff – thank you very much indeed. I upped it to 64M in the .htaccess file, and we’re working like a dream.

    Thank you very much to everyone who took the time to post in this thread, and helped gently shepherd me in the right direction for a fix – your help has been very much appreciated…:-)

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Odd blank sections in WP admin after installing BP’ is closed to new replies.

Topic Info

Skip to toolbar