Tim Moore
Forum Replies Created
-
If you have access, you could check you PHP error logs and see if there are any messages being thrown there that might help us locate the issue.
You could also post a list of your active plugins and I can test them, as well, to see if I can find an incompatibility.
Did you publish that code via the “Visual” tab in the editor?
What other plugins do you have active? Could you try deactivating them to see if there’s anything conflicting?
It might also be worthwhile trying a default theme (Twenty Ten or Eleven).
What is the content of the page when you are in the edit screen?
You should see something similar to:
[contact-form] [contact-field label="Name" type="name" required="true" /] [contact-field label="Email" type="email" required="true" /] [contact-field label="Website" type="url" /] [contact-field label="Comment" type="textarea" required="true" /] [/contact-form]Support is happening over here: http://wordpress.org/support/topic/plugin-jetpack-by-wordpresscom-wont-connect-to-wordpress?replies=16
Please keep to one thread so that support doesn’t get diluted. Thanks!
Hi Tim S,
Jetpack could be connecting from several different IP addresses in our data centers; it’d be hard to narrow down a specific one that could be blocked. We have dashboard.wordpress.com, jetpack.wordpress.com, and stats.wordpress.com, I believe, that all respond to requests from Jetpack, but they could be from any of our data centers or IP addresses.
In the testing I asked resistanceisfruitful to run above, our test suite indicated that PHP is configured in such a way that it could only spawn one process at a time. When Jetpack is initially connecting, it needs to have two processes spawned (one outgoing process, one incoming). This seems to be breaking the Jetpack connection process.
It also looks like HTTPS requests are being rejected entirely, which is not necessarily a problem. Jetpack tries to use either HTTP or HTTPS and both seem to be having issues currently.
Please let me know if I can help further.
Could you try changing your name servers to point directly to your inMotion hosting? Right now, the name servers are pointing to CloudFlare and a colleague and I believe it might be causing part of the problem.
@resistanceisfruitful: it looks like the issue is that your host limits the PHP processes. You should get in touch with them and ask them if their PHP_FCGI_CHILDREN is set to one and, if it is, ask them to set it to two or higher.
Do you have a caching plugin, like WP Super Cache or W3 Total Cache, installed?
If so, it is likely that you are seeing the site as a logged out user in Safari and on your iPad, which means you’d see a cached version. Until the cache is cleared (sometimes as long as 12 hours later), you’d continue seeing a static page and not any new content.
@resistanceisfruitful: if you could install this plugin and post the results, that would be perfect.
http://plugins.svn.wordpress.org/jetpack/branches/jetpack-compatibility-test.zip
@kekepana: is Jetpack active on your blog now? Everything looks to be in order; the sharing icons are a bit out of place, but not breaking things in my browser.
If things still look out of place, could you switch to Twenty Ten or Twenty Eleven and see if that changes anything?
@kekepana: could you provide the URL to your site where the issue is occurring?
Forum: Plugins
In reply to: Jetpack Stats not workingW3 Total Cache sometimes has incompatibilities with Jetpack, though not always.
As I mentioned previously, your host is responding very slowly, which will cause timeouts when requests are sent to our servers at WordPress.com to get your stats data. You’ll need to talk to your host to resolve response time issues.
Have you deleted the xmlrpc.php file from your server? Or has CloudFlare blocked that file in some fashion?
Forum: Fixing WordPress
In reply to: Jetpack stats how not to count my visit to siteThat setting will not count any visitors who are logged into your WordPress site only.
Forum: Plugins
In reply to: [Plugin: jetpack] site_inaccessible@russell: if Anticipate is blocking access to xmlrpc, be aware that even after Jetpack is connected, there will be times when Jetpack needs access to xmlrpc to do its work (accessing Stats, during upgrades, for email subscriptions, etc.).