[Trip Kirkpatrick]

In 2 successive clean local installs of CBOX, I’ve had the same thing happen twice: after installing and activating the CBOX theme, I’m able to access the client side of the local site, but not the admin side, which is a blank white screen. Each time, I’ve had to manipulate the database directly and set the theme to something else in order to restore access to the admin side. As best as I can tell, I followed the instructions at https://commonsinabox.org/documentation/installation. I tried chmoding my entire WordPress directory to 777, but no change, so it doesn’t seem to be a permissions issue, but it’s possible it’s a different kind of permissions issue. Something I noticed, but possibly a red herring, is that there’s no Infinity base theme listed among the themes.

The original installs were using 1.0.3, but upgrading to 1.0.4 doesn’t seem to have made a difference.

Running Mac (Lion) and MAMP Pro.

[Boone Gorges]

Trip – Please enable WP_DEBUG and try again. You should receive a “Fatal error” message when you try to access the admin. Report back with the content of that error.

To enable debug mode, open wp-config.php. Find the line that says

define( 'WP_DEBUG', false );

Change it to

define( 'WP_DEBUG', true );

[Trip Kirkpatrick]

Roger wilco. (But not until tomorrow.)

[Trip Kirkpatrick]

Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-includes/functions.php on line 2959

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-includes/functions.php on line 2959

Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 12288 bytes) in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-admin/includes/update.php on line 107

**********

Interesting that even when I flop it back to Twenty Twelve in the database I get

Notice: Trying to get property of non-object in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-content/plugins/commons-in-a-box/admin/admin-loader.php on line 133

on my dashboard.

 

[Trip Kirkpatrick]

Note:

I am also seeing a BuddyPress menu in the WP Dashboard. When I access it, I get the notice:

“Don’t worry! We’ve moved the BuddyPress options into more convenient and easier to find locations. You’re seeing this page because you are running a legacy BuddyPress plugin which has not been updated.

Components, Pages, Settings, and Forums, have been moved to Settings > BuddyPress. Profile Fields has been moved into the Users menu.”

[Boone Gorges]

The Fatal Error you’ve pasted above says that you’ve run out of memory. What’s probably happening is that you were running pretty close to being out of memory already, and the Commons In A Box theme has fairly hefty Dashboard settings, so it pushed you over the edge. You can try dropping the following into your wp-config.php file, to see if it helps:

define( 'WP_MEMORY_LIMIT', '64M' );

It appears that your current memory limit is 42M, which is pretty low for an installation of BP + WP + a bunch of other plugins. Bumping the limit as I’ve suggested here should work, as long as your host doesn’t have restrictions against this kind of manual adjustment.

You can safely ignore the other notices.

The BuddyPress menu you see is not a bug. In a recent version of BP, the top-level options were moved to Settings > Dashboard, but we add the top-level menu dynamically when a legacy plugin needs it.

[Trip Kirkpatrick]

Rokey dokey — that got me able to have a Dashboard and a public end. Turned out it was MAMP Pro’s php.ini setting the threshold at 32M.

However, I’m still seeing
Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-includes/functions.php on line 2959

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-includes/functions.php on line 2959

Notice: get_current_theme is deprecated since version 3.4! Use wp_get_theme() instead. in /Users/trip/Documents/Academic Commons/buddypress-test/wordpress/wp-includes/functions.php on line 2839

Is there any connection, or is that a separate problem, or is there nothing to see here, move along?

[Boone Gorges]

> nothing to see here, move along?

This. You can now disable WP_DEBUG.

[Author]

Posts