wkoffel
Forum Replies Created
-
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Disable auto-tweet/FacebookThanks, definitely helps. So first off, that checkbox default works fine, the confusion on that was my fault.
Regarding the Jetpack connection, I use Duplicator (http://wordpress.org/plugins/duplicator/) to pull down the production site periodically so I have the latest content to develop against locally. What must be happening is that the database settings and connection tokens to Jetpack are being duplicated a bit too well. 🙂
So problem solved, I have two options. Change the checkbox default in development, or even easier, just disconnect jetpack whenever I’m in development mode and reconnect only to test specific jetpack features.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Disable auto-tweet/FacebookThanks Jeremy. I tried that filter for ‘publicize_checkbox_default’ and it doesn’t seem to have any effect for me. I still see in the New Post admin interface that it’s going to be publicized the all my connections. WP 3.7.1, latest Jetpack.
Any thoughts?
Jetpack automatically turns on development mode when you have a domain of ‘localhost’, which I happen to when developing, so that’s working fine. But the issue for me is that Publicize is using the same oauth to social media sites in both environments. If I disconnect them all in development, then they are also disconnected in production. Are those going through my WP connection in some way I don’t understand?
I’d just like to be able to disconnect them all in dev, while leaving them in production. Or even better, have a way to globally disable publicize in my dev environment. If I could get the ‘publicize_checkbox_default’ working, I suppose I could just add an environment check into that filter, that’d probably do the trick.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Disable auto-tweet/FacebookI’ll second this request. I’m surprised there’s no way to disable the publicize features in development without also breaking all the oauth on a live copy of the site.
More than once I’ve been developing on a copy of my site and posted a localhost URL by accident to Twitter, Facebook, LinkedIn. It creates an embarrassing mess. Any thoughts on a way to make that cleaner?