Tim Moore
Forum Replies Created
-
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack DisappearedHi – you’ll need to log in via FTP and locate the folder
wp-content/plugins/jetpack. Delete thejetpackfolder. Then go back into your WordPress Dashboard and install Jetpack. Everything should install and activate just fine.This is not currently possible. We are working on a method to allow local development and will post a notice on http://jetpack.me/news when it is available. Thanks!
Using Publicize in Jetpack, it is not possible to change that text. You’d have to use a different plugin and set up your own Facebook App with your own App ID and Key.
When you are asked to enter a username and password by Jetpack, you should be using a WordPress.com account, not your local WordPress account. Two different accounts.
You can get a WordPress.com account here:
https://signup.wordpress.com/signup/?user=1Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Akismet and Jetpack mergedThis is intended. The code is actually in the Akismet plugin; it checks to see if Jetpack is active, then either puts its menu under Jetpack’s or under the Plugins menu.
Hi Ozh,
I do appreciate the feedback and the review. WP core doesn’t currently support removing a custom post type via a filter, so we haven’t added anything to the Jetpack plugin to do this at this time. (See this for more info).
In the meantime, I put together a mini-plugin for you that should give you your requested functionality:
https://dl.dropbox.com/u/92961364/jetpack-cpt-remover.zip
Let me know if that helps.
Thanks,
Tim
For folks receiving the -32301 error code, that usually means that your site is set to private in some way. Either your web host will not allow connections from our servers at WordPress.com or you’ve set up your site to be accessible to only certain folks, which means Jetpack will not have access.
Are either of you using a Minify plugin, like W3 Total Cache?
ob_start(); comment_form(); ob_get_clean();The issue is that your
comment_form()is being put into an output buffer. Ifob_get_clean()is on a line by itself and not beingecho‘d, then that is why your comments are not showing up.I’d recommend removing
ob_start()andob_get_clean().Not currently. We are in the middle of a large release. I will take a look at this ASAP.
Twitter has been changing its API and locking it down. It is quite likely that if you are on shared hosting, your host’s server has been blocked by Twitter because, between all of the sites on the server, Twitter has seen too much traffic from that one server.
This isn’t something that Jetpack or any WordPress plugin can control or prevent, unfortunately.
The change in Jetpack 1.8.3 and on should be sending email “from” the site URL of the WordPress site.
The address it tries is “wordpress@EXAMPLE.COM”.
It is possible that Yahoo is blocking anything that is not a real email address. You could try setting up “wordpress@EXAMPLE.COM” as a real email address on your client’s Yahoo email system (if possible) to see if this helps.
This seems to work fine for me in the Chrome browser. What browser are you using?
There is not currently a method to do this.