cityeyes

Ok, I spoke too soon. Getting internal server errors like mad even with the default theme and no plugins activated aside from Akismet.

I’m literally the only person on the site right now and it’s still regularly spiking to 512 megs.

Glad to see I’m not alone. It really is a pain.

I should have taken notes on which version the problems started with.

Edit: OK, I fixed *some* of my problems by switching to a more up-to-date theme. It’s not screwing up as much, but it still seems to be spiking.

@matt Kelly, Oh cool, thanks. I’ll keep my eye out for the changes.

I’m wondering the same thing as Igloozion. I submitted a “process”, but given the fact I’m going to be the only person submitting to my app (through the WP Facebook plugin), I can’t really give the people in charge of approval a good walkthrough of what exactly to do without creating a dummy account, which I don’t really feel like doing.

I just explained myself and gave a walkthrough of what I’d do to use that action. Guess I’ll see if I get rejected or not.

Success! Everything seems to have worked properly!

No problem at all, by the way. You guys are on the ball. I appreciate it.

Yup, that problem’s solved. Now, unfortunately, I’m getting the same problem as is found here (the OAuth error).

Exact error is (with app name redacted, just in case):

Failed posting to your Facebook Timeline. Error: {“message”:”Unknown path components: /(my namespace):publish”,”type”:”OAuthException”}

I should probably note that I do have social posting enabled, I just can’t seem to get it to work 100%.

Awesome, will do. Thanks!

For reference, those particular lines read:

$status_messages = array_merge($existing_status_messages, $status_messages);

in the Fb social publisher and:

header(“Location: $location”, true, $status);

in Pluggable.

Gonna post this in a different thread because it seems to be a different problem.