You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2021. It is now read-only.
I didn't have an issue incorporating Detector into my theme by literally dropping said directory into the theme directory then requiring it from functions. In terms of functionality it was a breeze.
What I discovered belatedly when having to connect to Wordpress to enable Jetpack was the following alert:
Error Details: The Jetpack server could not communicate with your site's XML-RPC URL. Please check to make sure http://www.example.com/ 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.
What happens when visiting /xmlrpc.php is just an endless loop. Commenting out Detector from functions.php let xmlrpc.php resolve correctly.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I didn't have an issue incorporating Detector into my theme by literally dropping said directory into the theme directory then requiring it from functions. In terms of functionality it was a breeze.
What I discovered belatedly when having to connect to Wordpress to enable Jetpack was the following alert:
Error Details: The Jetpack server could not communicate with your site's XML-RPC URL. Please check to make sure http://www.example.com/ 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.
What happens when visiting /xmlrpc.php is just an endless loop. Commenting out Detector from functions.php let xmlrpc.php resolve correctly.
The text was updated successfully, but these errors were encountered: