Conversation
supportHi, We’re using Jetpack to push blog posts to Facebook, LinkedIn and Instagram. We have a php snippet installed that had previously allowed us to manually push posts when we publish, as sometimes we don’t want posts to automatically be shared to socials (for example if it’s not relevant). It was working previously, but now posts seem to be being shared automatically on socials when we publish again. Here is the snippet we have on the site: // Disable auto-selection of social media networks add_filter( ‘publicize_checkbox_default’, ‘__return_false’ ); Any assistance would be much appreciated. Sarah The page I need help with: [ log in to see the link]
Hi there, @sirrah , I’m sorry to hear about the trouble, but thanks for reaching out. Before diving into the bespoke PHP code, I checked your Jetpack connection, and I can see some blocks happening at the server’s end that are preventing Jetpack from connecting as expected. Let’s see if we can fix your initial problem by re-establishing a working connection 🙂 There seems to be a block returning the 503 error, that typically indicates a mismatch in the settings at the host’s end. I recommend contacting your host and report this error, in detail: Transport error - HTTP status code was not 200 (503) It’s also worth checking the following: ensure our IP range is fully in the allow list for your servers: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/ check for any security/caching plugins you may have enabled, and try temporarily disabling them to see if it fixes the problem. search for any firewall on your server-side that might be blocking the communication with the Jetpack Hope that’s all clear! Let me know how you get on, and we’ll take it from there if necessary. Thanks!
Hi, I’ve checked these items and can’t see any issues from our end. The posts are still sending via Jetpack so I don’t think there is any issue with communication. They just seem to be sending automatically when they shouldn’t be. Thanks, Sarah
Hi @sirrah , Thanks for reaching out — I’ve been looking into your site and I have a couple of things to flag. First and most important — check for code snippet issues I understand you’re using a code snippets plugin to customize Jetpack Social’s auto-sharing behavior using the publicize_checkbox_default filter. Please double-check the syntax carefully. A common issue we see is smart/curly quotes getting into the code, especially when copying snippets from websites, docs, or emails: add_filter( 'publicize_checkbox_default', '__return_false' ); I’d recommend checking any active code snippets and, if in doubt, deleting and manually retyping the code rather than pasting from a formatted source. As a side note — I also noticed your site has duplicate social connections (two Facebook and two LinkedIn connections pointing to the same Bureaucracy Beat profiles, set up by two different admin users). One set is marked as shared/global, which means it allows auto-shares for all users on the site. Cleaning up the duplicates under Jetpack → Social for each individual admin user would help clean up your social connection setup. Let us know how things go!
Hi, Thanks so much for getting back to me. I checked the snippet and it looks correct. I think it might be the second factor you mentioned – duplicate social connections. I think I’ve turned off those duplicates now – is that something you can see has been resolved from your end? If not, are you able to point me in the right direction as to how to clean up the duplicates? Thanks again for all your help. Sarah
Hi, I’m just following up on this as I’ve tried again to post without it automatically pushing and it’s still not working (i.e. is automatically posting when it shouldn’t). But now, I’m also receiving emails from Jetpack saying that the post failed to send to Facebook when it did! Is there any other avenue for support for the plugin? It was working with no issues, and for no apparent reason it is not working as it should.
Hi @sirrah , I looked again at your site’s social connections and found that the duplicate connections were still active. I’ve sent a follow-up directly to the email address associated with your Jetpack connection with a full summary of what was done to address the duplicate connections and to continue our conversation there. I’m also going to close this forum thread for now, as we’ll be tracking your issue via that direct support ticket #11250076 going forward. If you ever need to reach us directly again, you can do so anytime at https://jetpack.com/contact-support/ . Best,
Hi there, @sirrah , I’m sorry to hear about the trouble, but thanks for reaching out. Before diving into the bespoke PHP code, I checked your Jetpack connection, and I can see some blocks happening at the server’s end that are preventing Jetpack from connecting as expected. Let’s see if we can fix your initial problem by re-establishing a working connection 🙂 There seems to be a block returning the 503 error, that typically indicates a mismatch in the settings at the host’s end. I recommend contacting your host and report this error, in detail: Transport error - HTTP status code was not 200 (503) It’s also worth checking the following: ensure our IP range is fully in the allow list for your servers: https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/ check for any security/caching plugins you may have enabled, and try temporarily disabling them to see if it fixes the problem. search for any firewall on your server-side that might be blocking the communication with the Jetpack Hope that’s all clear! Let me know how you get on, and we’ll take it from there if necessary. Thanks!
Hi, I’ve checked these items and can’t see any issues from our end. The posts are still sending via Jetpack so I don’t think there is any issue with communication. They just seem to be sending automatically when they shouldn’t be. Thanks, Sarah
Hi @sirrah , Thanks for reaching out — I’ve been looking into your site and I have a couple of things to flag. First and most important — check for code snippet issues I understand you’re using a code snippets plugin to customize Jetpack Social’s auto-sharing behavior using the publicize_checkbox_default filter. Please double-check the syntax carefully. A common issue we see is smart/curly quotes getting into the code, especially when copying snippets from websites, docs, or emails: add_filter( 'publicize_checkbox_default', '__return_false' ); I’d recommend checking any active code snippets and, if in doubt, deleting and manually retyping the code rather than pasting from a formatted source. As a side note — I also noticed your site has duplicate social connections (two Facebook and two LinkedIn connections pointing to the same Bureaucracy Beat profiles, set up by two different admin users). One set is marked as shared/global, which means it allows auto-shares for all users on the site. Cleaning up the duplicates under Jetpack → Social for each individual admin user would help clean up your social connection setup. Let us know how things go!
Hi, Thanks so much for getting back to me. I checked the snippet and it looks correct. I think it might be the second factor you mentioned – duplicate social connections. I think I’ve turned off those duplicates now – is that something you can see has been resolved from your end? If not, are you able to point me in the right direction as to how to clean up the duplicates? Thanks again for all your help. Sarah
Hi, I’m just following up on this as I’ve tried again to post without it automatically pushing and it’s still not working (i.e. is automatically posting when it shouldn’t). But now, I’m also receiving emails from Jetpack saying that the post failed to send to Facebook when it did! Is there any other avenue for support for the plugin? It was working with no issues, and for no apparent reason it is not working as it should.
Hi @sirrah , I looked again at your site’s social connections and found that the duplicate connections were still active. I’ve sent a follow-up directly to the email address associated with your Jetpack connection with a full summary of what was done to address the duplicate connections and to continue our conversation there. I’m also going to close this forum thread for now, as we’ll be tracking your issue via that direct support ticket #11250076 going forward. If you ever need to reach us directly again, you can do so anytime at https://jetpack.com/contact-support/ . Best,