-
AuthorPosts
-
December 18, 2013 at 4:06 am #201369
Ever since I installed Enfold and deactivated all the plugins and reactivated them I’ve been getting the following error message when attempting to connect Jetpack to WordPress.com.
Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. Please check to make sure http://mountainstreamgroup.com/wordpress/xmlrpc.php is working properly. It should show ‘XML‑RPC server accepts POST requests only.’ on a line by itself when viewed in a browser and should not have any blank links or extra output anywhere.
Jetpack states “The problem is that there’s whitespace above the message. This extra space is annoyingly important. It suggests that some plugin, theme, or wp-config.php file in your WordPress has extra “whitespace” (new lines, spaces, tabs, …) before the first “<?php” in the file.”
I started going through all of the .php files as they stated and I found the Enfold error404.php file has the following.
1
2<p class=’entry-content’><?php _e(‘Nothing Found’, ‘avia_framework’); ?><br/>
3
4<?php _e(‘Sorry, the post you are looking for is not available. Maybe you want to perform a search?’, ‘avia_framework’); ?>Are these spaces on line 1 and 3 the possible cause?
December 18, 2013 at 4:37 am #201378Hey MtnStreamGroup!
Could be! Try changing the opening of the file to:
<?php /** * Content area of the 404 error page * */ ?> <p class='entry-content'><strong><?php _e('Nothing Found', 'avia_framework'); ?></strong><br/>
Just make sure there is no white space before of course :)
Regards,
Devin- This reply was modified 11 years ago by Devin.
December 18, 2013 at 5:16 am #201393Thanks, but that didn’t solve the problem. I’ve just searched for the “‘XML‑RPC server accepts POST requests only.” in the xmlrpc for WP 3.8 and can’t find it.
- This reply was modified 11 years ago by MtnStreamGroup.
December 18, 2013 at 7:39 am #201407Sounds like it may be an issue with the WordPress install in that case. I’ve not run across that issue so I’m not sure what else you could really try but hopefully Jetpack support has some additional information on it.
December 19, 2013 at 7:13 pm #202182I’ve done more digging into the issue.
1.) I tried running a plugin called XML-RPC De-whitespacer then tried to connect to WordPress.com. First I got a no load gray screen. When I reloaded the page, I got the following error.
site_inaccessible Error Details: The Jetpack server was unable to communicate with your site http://mountainstreamgroup.com/wordpress [IXR -32300: transport error: http_request_failed transfer closed with 1 bytes remaining to read]
I deactivated this plugin and the error message returned to xml_rpc-32700.
2.) I deactivated all of the plugins.
3.) I checked our XMLRPC.php and got this screenshot. https://dl.dropboxusercontent.com/u/18117912/xmlrpc2.jpg This screenshot shows at least 4 lines of whitespace.
4.) You mentioned a possible WordPress install issue. I followed the WordPress instructions on manually installing WP3.8, including having all plugins deactivated during installation.
5.) After the clean install of WordPress 3.8, I checked the XMLRPC.php again. The same screenshot as in item 3 above.
I thought there was a issue with the Enfold Child theme which points Enfold 2.5, but I changed to Twenty Twelve, and other themes and go the same issue.
When I changed to the Nimble theme and I checked the XMLRPC.php again. When I did that I got this screenshot https://dl.dropboxusercontent.com/u/18117912/xmlrpc-nimble.jpg. More whitespace.
Then I went through all of the same process for Twenty Eleven, Twenty Twelve, Twenty Thirteen and Twenty Fourteen then back to Enfold Child. All of them had the same whitespace.
Then I activated XML-RPC De-whitespacer plugin with the Enfold Child theme activated and all other plugins including Jetpack deactivated. I got this screenshot. https://dl.dropboxusercontent.com/u/18117912/XML-RPC%20De-whitespacer.jpg
With XML-RPC De-whitespacer plugin activated, I activated jetpack and no other plugins. Then I tried to connect to WordPress.com. I got the following error message.
site_inaccessible Error Details: The Jetpack server was unable to communicate with your site http://mountainstreamgroup.com/wordpress [IXR -32300: transport error: http_request_failed transfer closed with 1 bytes remaining to read]
Based on my testing that seems to be a WordPress 3,8 issue.
- This reply was modified 11 years ago by MtnStreamGroup.
December 20, 2013 at 11:01 am #202521Hi!
A google search return some results (i.e. http://wordpress.org/support/topic/site-inaccessible-error-after-upgrading-to-wp-38 ) and I’m pretty sure it’s a wp3.8 issue.
Best regards,
PeterAugust 26, 2014 at 4:29 am #309094I stumbled upon this thread after hearing back from Automattic and the support team at JetPack:
While your site is publicly accessible, we cannot access your site’s XML-RPC file:
This file is used by Jetpack and other plugins and apps to connect to your site, and must return the following message:
XML-RPC server accepts POST requests only.I’m running WP 3.9.2 — so this is unrelated to WP 3.8 —
I’m running WordPress on several other sites and don’t have a problem with this. Wondering if anyone else has encountered this?
I do have a second WP infall on this domain but in a totally different directory.
Here’s the link to my site: http://worldri.de/9KS6l
- This reply was modified 10 years, 3 months ago by MacMyDays.
August 26, 2014 at 5:28 pm #309434Hi!
We’ve not had any other reports about this but you could try switching to one of the twenty something themes and see if that helps.
Edit: for clarity, switching themes is meant as a test to see if there is a theme specific conflict and not a permanent solution :)
Cheers!
Devin- This reply was modified 10 years, 3 months ago by Devin.
August 26, 2014 at 8:37 pm #309510Great idea, Devin.
I did just that and JetPack fired up with no problem:
You’re fueled up and ready to go.
Jetpack is now active. Browse through each Jetpack feature below. Visit the settings page to activate/deactivate features.When I switched back to Enfold Child theme, I didn’t get any other error. So just switching to Twenty Fourteen and back to Enfold seemed to solve that issue.
strange
-
AuthorPosts
- The topic ‘XML-RPC file’ is closed to new replies.