jphase

Version 2.1.1 has a redirect loop when active that has something to do with the intro text after update. I’m unable to access my dashboard after updating to Version 2.1.1, and the only way I can is to move the plugin directory. Once moved back into place and reactivated, the redirect loop occurs again.

I can’t say what logic is causing the redirect loop definitively, but commenting out the wp_redirect() call on line 31 of admin/class-config.php will resolve the issue temporarily.

If you need help with the example filter mike62 linked to, I’m the person who wrote it. I’m happy to help.

Thanks dakta – there are many out there that have been trying to google this specific need without an explicit answer. Your solution was quite helpful.

rosyb:

either open up wp-config.php and put this in there:

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

or open up .htaccess in your web root and put this in there:

php_value memory_limit 64M

For me it was including another php file in functions.php that broke this. The contents of the file didn’t matter, even including a blank file breaks this. Anyone know why or maybe a better way to include a file from functions.php?

So after some debugging and googling, I realized that this was theme-specific. In my case, I was using an include in my functions.php file to include a php file to setup some settings in Settings > General. Removing this include (or switching to twenty eleven) fixed the problem.

The weird thing is, I could delete the contents of my settings.php file I was including that caused the problem and it still broke the network admin screen. It’s literally my include line that broke it??

include "settings.php";

Any idea how I can do this without breaking the network screen? Perhaps a cleaner way to include a file in functions.php?

Scratch that, after setting up my different domains (WPMU) I get the 500 error again. Booo!

Just to chime in…

On a fresh install of 3.4.2 doing a subdomain multisite install (manually) – I’m getting the exact same problem, same get_current_screen() error message in apache logs, and same 500 error when accessing the network admin screen.

@incrediblesolv_list – I rolled back to 3.2.1 and tried again, same exact problem

So far the only way I was able to resolve this was to roll back to 3.0 (old school), do the network install, then update to 3.4.2

Definitely a huge bug in the network install process. If you already have a network installed and configured, this doesn’t seem to be an issue with the latest version. Definitely a big bug and I don’t have the time to troubleshoot, so here’s my cheap trick workaround.