Skip to:
Content

BuddyPress.org

Opened 16 years ago

Closed 16 years ago

#6 closed defect (bug) (fixed)

newest trunk download keeps MU site from loading.

Reported by: lostdeviant's profile lostdeviant Owned by:
Milestone: Priority: critical
Severity: Version:
Component: Keywords: site won't load, core
Cc:

Description

Fatal error: Allowed memory size of 12582912 bytes exhausted (tried to allocate 30720 bytes) in /home/myhostingaccount/public_html/name ofwebsite/wp-content/plugins/share-this/share-this.php on line 644

as soon as I uploaded the newest buddypress files to their proper places and tried to reload the site I got an error for a similar plugin. I DELETED that plugin from my site via FTP and got the same error for this plugin.

I then uploaded the same buddypress files to another mu install and got the same issue.

I went one by one deleting BP plugins and still got the error. My mu site only loaded once I had removed the core file.

I then went back to the first install of buddy press and removed the core file first and my site loaded right back up. I wouldn't expect the plugins to work so I then deleted them anticipating the fix.

Change History (4)

#2 @drmiketemp
16 years ago

  • Resolution set to invalid
  • Status changed from new to closed

You need to bump up the allowed memory within php. This is covered in point 2 under the PHP section of the Readme file included with the wpmu download.

#3 @lostdeviant
16 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

r9 didn't give that error. I have the memory_limit set to 64 in the php.ini and I know my account is at 64 because I had requested it raised in the past.

Whatever was changed in the core file is requiring much more memory which means a dedicated server will be required just for a few blogs to work. That is not cool.

#4 @apeatling
16 years ago

  • Resolution set to fixed
  • Status changed from reopened to closed

I've removed this line. Please follow the instructions in the MU readme to handle this.

Note: See TracTickets for help on using tickets.