sfmobius

Not sure what I’m missing but I am having the same problem. Plugin is up and running, Facebook app is up and approved. Added ID and key and getting 0 imports.

Is there a configuration url or Valid OAuth redirect URIs ?

Please advise

ountered in order over the span of about 3 months.

1) Live Writer returned the “500 error” anytime I tried to upload a post with pictures or attachments. I incorrectly assumed it was my xmlrpc file.
2) Dashboard widgets would sometimes load and other times only 1 or 2 would load.
3) Manually creating posts in WP would generate “500 error” but the post still went thru.
4) Unable to upload any media files thru WP.

My ISP proposed a variety of answers so I thought I’d share all of them. This is, of course, assuming your write permissions are set correctly for your WP directory.

1) Disable and test plug-ins. This is particularly important if you use plugins that restrict views or categories based on users logged in or not. Sometimes, they create their own .htaccess files which causes problems if you upgrade, downgrade, or remove the plugin. You should have one .htaccess file in your root blog directory. Any others in other sub directories should be suspect. Check the plugin vendors instructions for a fix.

2) The file upload size for your server is set too low and the 500 error is returned as a result. Your host can change this if you don’t know how. It takes all of 5 minutes. I didn’t realize my host has a default setting of 10megs.

3) If your hosting provider is running multiple versions of PHP, you’ll definitely need this fix for WP v2.7 and above. Your .htaccess file has to call for the newer version of PHP.

Note – If you are using default permalinks, you may not have a .htaccess file at all. WP only creates it when you change the default handling of how it processes files/links. You’ll have to manually create one in this instance. https://codex.www.ads-software.com/Using_Permalinks

Use “AddType x-mapp-php5 .php” without the quotes and note the spacing between the 5 and the dot is correct, do not remove it. Also, add this to your .htaccess file AT THE VERY BEGINNING, even before the “#Begin WordPress” comment.

Apparently, PHP v5.0 has significant improvements in rendering w/o extra server load so ISP’s may throttle your backend use to encourage you to upgrade. NOTE – If your host is only using one version of PHP, DON’T DO THIS, IT WILL CAUSE MORE PROBLEMS.

*I’ve posted this on a few different threads, apologies if you get this more than once*

I thought I’d share some of my issues and the possible fixes I discovered in talking with my domain host. I’ve listed the problems I encountered in order over the span of about 3 months.

1) Live Writer returned the “500 error” anytime I tried to upload a post with pictures or attachments. I incorrectly assumed it was my xmlrpc file.
2) Dashboard widgets would sometimes load and other times only 1 or 2 would load.
3) Manually creating posts in WP would generate “500 error” but the post still went thru.
4) Unable to upload any media files thru WP.

My ISP proposed a variety of answers so I thought I’d share all of them. This is, of course, assuming your write permissions are set correctly for your WP directory.

1) Disable and test plug-ins. This is particularly important if you use plugins that restrict views or categories based on users logged in or not. Sometimes, they create their own .htaccess files which causes problems if you upgrade, downgrade, or remove the plugin. You should have one .htaccess file in your root blog directory. Any others in other sub directories should be suspect. Check the plugin vendors instructions for a fix.

2) The file upload size for your server is set too low and the 500 error is returned as a result. Your host can change this if you don’t know how. It takes all of 5 minutes. I didn’t realize my host has a default setting of 10megs.

3) If your hosting provider is running multiple versions of PHP, you’ll definitely need this fix for WP v2.7 and above. Your .htaccess file has to call for the newer version of PHP.

Note – If you are using default permalinks, you may not have a .htaccess file at all. WP only creates it when you change the default handling of how it processes files/links. You’ll have to manually create one in this instance. https://codex.www.ads-software.com/Using_Permalinks

Use “AddType x-mapp-php5 .php” without the quotes and note the spacing between the 5 and the dot is correct, do not remove it. Also, add this to your .htaccess file AT THE VERY BEGINNING, even before the “#Begin WordPress” comment.

Apparently, PHP v5.0 has significant improvements in rendering w/o extra server load so ISP’s may throttle your backend use to encourage you to upgrade. NOTE – If your host is only using one version of PHP, DON’T DO THIS, IT WILL CAUSE MORE PROBLEMS.

*I’ve posted this on a few different threads, apologies if you get this more than once*

I’m using a fresh install of v2.7 and a new database. Every time I uploaded an image I got the “auth required” box. After an exhaustive effort on the items above, none of them worked.

However, I changed the upload directory and the problem disappeared. I only upload images/videos to my blog and I am the only person allowed to upload. Not sure if that works for everyone but putting it out there for anyone else, like me, who just wants it to frakin’ work!

@mickmel

I had already created a new user and reassigned my posts to it. However, this worked like a charm.

I found an answer here. If WP is not in your root directory and you add additional domains or subdomains, WP will cause the subdomains to either get caught in an infinite loop or resolve to your root directory.

I nifty workaround is here. https://markjaquith.wordpress.com/2007/09/25/wordpress-23-canonical-urls/ Scroll to the bottom and click the “online plugin” at the bottom of the article. Save install as a plugin and shazam, your subdomains and domains pointing at your blog directory will function again.

I use 1and1.com and I’m running on a linux serve but having the same problem. They are telling me wordpress is redirecting my subdomain back to the root.

My wordpress and blog url are both at https://www.mobius.name/blog. I point a subdomain blog.mobius.name to the /blog/ directory but after the recent upgrade it resolves to the root. 1and1 says there is a scripting error from wordpress causing the redirect.

Is there a workaround for this? I tried changing the blog url to blog.mobius.name but then if someone loads the full path it adds an extra ‘blog’ directory at the end for a url like this, https://www.mobius.name/blog/blog/