irifkin

Look in the error log

Not much in the PHP error log. No messages when going to the /wp-admin pages. When going to the front page at / I see the following error:

PHP Notice: Undefined index: filter in wp-includes/default-widgets.php on line 382

(a seg fault implies you have a bolloxed install, BTW)

Perhaps that’s related? Any suggestions?

Thanks again.

Tried twenty eleven theme. Same result (/wp-admin pages are blank).

Yes, JSON is enabled. Version 1.2.1 of JSON.

Any other thoughts?

Thanks again!

PHP version 5.2.5.

Hi,

Yes, PHP error, but specific to this version of WordPress. Rolling back to 3.1.3 it works fine. In Apache error log I see the following:

[Mon Aug 01 20:57:17 2011] [notice] child pid 12595 exit signal Segmentation fault (11)

I disabled all plugins and even temporarily deleted them completely and still see the same.

htaccess is still in place.

Any ideas?

Thanks

I wasn’t thinking it’s a multisite issue and didn’t realize there was a special Multisite forum.

Thanks.

FYI, we use the Multisite functionality (by sub-directory). It seems that I can’t see the front-end of the other blogs after I upgrade either. The wp-admin pages for the sub-blogs show the same behavior as noted above.

Thanks.

Hi again,

I just double checked. I do not see the error about pluggable when using the Twenty Eleven theme, but it still doesn’t work. Going to /index.php now redirects back to / like it should, so maybe that part was theme related.

On the homepage it looks fine except for a message in a sidebar that says:

Notice: Undefined index: filter in wp-includes/default-widgets.php on line 382

I can click around the non-admin part of the site and see posts and pages.

If I go to /wp-admin it’s blank.

I can go to /wp-login.php which loads fine and I can authenticate successfully. It redirects me to /wp-admin which is still blank. Going to /wp-admin/index.php prompts me to download the index.php file which is blank.

Going back to / it looks OK and I see my admin menu at the top, but the links (all to specific .php files in /wp-admin) all prompt me to download a blank file instead of loading the page.

I hope this helps better explain the issue.

Thanks again.

Typo in my previous post. Yes, a fresh copy of 3.2.1 is what I tried.

Sorry for confusion! Any ideas?

Ian

Hi,

Thank you for your reply.

I reverted back to 3.1.3, switched to the default theme and tried again. Same behavior.

I tried removing all plugins again. Same behavior.

I tried a fresh download of WordPress 3.1.3 downloaded from www.ads-software.com except for wp-config and wp-content (themes, and blogs.dir). Same behavior.

I tried running the upgrade from wp-admin and that also shows the same behavior.

Thoughts?

Thanks again.

@marikamitsos Sure thing. I’ve posted the patch file: https://pastebin.com/HMJ37yfh

For those comfortable with UNIX, you can run the following at the command line:

patch ds_wp3_moderate_new_blogs.php < moderate.patch

where “ds_wp3_moderate_new_blogs.php” is the path to the plugin and “moderate.patch” is the path to the patch file I’m sharing with you.

If you’re not comfortable with this, you can manually make the changes. The lines beginning with “–” are the lines before the patch is applied and the lines beginning with “++” are the lines after the patch is applied.

Hope this helps!

It looks like this plugin is no longer maintained, but I was able to get it working. The two things that need to be fixed are:

1) The paths to the files. ms-edit.php doesn’t exist. It should bee /wp-admin/network/edit.php

2) It needs the _wpnonce in the URL.

I’d be happy to share a patch file with you or anyone else interested. I’m not sure if there’s anywhere I can post it on here?

Regards,
Ian

Hi,

I run WordPress Mu (2.9.1), but I thought I’d reply because I see something similar in my logs. My apache logs have requests coming from localhost (127.0.0.1) that are returning 302 redirects. An interesting point is that the GET says HTTP/1.0 (not 1.1).

Sometimes it “gets” so bad the server can’t take the load. It’s like it DoS’s itself!

So there are two questions:
1) Why do HTTP/1.0 GETs return redirects?
What’s interesting here is that doing a GET / HTTP/1.0 via telnet does return 200 if I specify the host, but returns 302 error if I don’t. I think this is because (for me at least) my domain name is listed as a virtual host in my apache config.
2) Why is the server hosting wordpress doing GETs of itself?
This I’m not sure about. Maybe it’s a plugin (e.g. akismet)? Any ideas?

My apologies if my issue is specific to Mu, but I thought I’d reply as it appears netwood99 has a similar issue.

Thanks,
Ian

It works when I change the config to use PSpellShell, so I guess my dictionary file is present. Is there something else I need to do to get it to work with (the default) GoogleSpell?

FWIW spellcheck does work if I edit the spellchecker config and change it from GoogleSpell to PSpellShell. But why doesn’t GoogleSpell work, especially if it’s the default?