Viewing 15 replies - 1 through 15 (of 56 total)
  • lollypopstar

    (@lollypopstar)

    Yes I’m having the same problem too. The url is correctly set for the Facebook post – but the Twitter one seems to be using an old (cached?) version of the site address…

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Could you go to Settings > General in your dashboard, and check your Site and WordPress address?

    If they both show the correct domain, could you click on “Save Changes” at the bottom of the page, and see if that helps next time you publish a post?

    Thread Starter swaroopch

    (@swaroopch)

    The first thing I did when I observed the issue was to check the site and wordpress address – they are both correct, I will let you know what happens the next time after ‘save changes’.

    lollypopstar

    (@lollypopstar)

    I checked the settings on my WordPress site, and resaved them, to no avail.
    I even tried “disconnecting” from WordPress.com within Jetpack & reconnecting to see if that would recognise the new settings, again to no avail.
    Also tested deleting the link to my Twitter account in the Sharing section and using an alternate account – still it shares with links to old address.

    Any suggestions what to try next?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @lollypopstar Could you let me know your site URL?

    lollypopstar

    (@lollypopstar)

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thank you! I had a look at your site settings, and everything seems to be set up properly. However, I noticed that your site is not connected to Twitter anymore.

    Could you try to reconnect, and let us know if the problem happens again?

    lollypopstar

    (@lollypopstar)

    Hi Jeremy, I just tested it with another Twitter account and it works now, thank you.

    Any guidance as to what I did wrong? I think in future when I set up a WordPress site I won’t connect it to Jetpack until its on a live URL. Hopefully that will stop any of these caching issues

    Thanks again.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    I think in future when I set up a WordPress site I won’t connect it to Jetpack until its on a live URL.

    That seems like a good solution, yes. Hitting “Save changes” in Settings > General should also solve any problems you may have in the future, since it updates your site settings as well as your Jetpack settings.

    If you still experience issues, you can also contact us via our contact form here:
    https://en.support.wordpress.com/contact/?jetpack=needs-service

    majones

    (@majones)

    Hi,

    I’m getting the same problem on one of my wordpress installs – it’s calling the original dreamhoster.com url that the install was set up on but that hasn’t been an active url for a good couple months. Publicizer was only activated yesterday on our install.

    Site settings have the correct domain (sla-europe.org) in place in both fields and I’ve tried removing and replacing them and saving it again but it still picks up the now inactive dreamhoster url.

    Thanks.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @majones I have made a change to your Jetpack site settings. Could you try publishing a new post? It should use the proper URL now.

    majones

    (@majones)

    @jeremy – Hooray, it worked! Out of curiosity, what exactly needed to be changed?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    @majones Your Jetpack site settings still used your old dreamhoster URL. It seems they were not updated when you changed your site address in Settings > General in your dashboard. I just changed it manually for you ??

    Is this something we’ll be able to do for ourselves at some stage? Like most others here, I’m assuming, I first did my WordPress site on a separate development URL, and then copied everything to a production server and gave it a production URL. Today I posted my first post, and LinkedIn + FaceBook used the development URL, however, Twitter used the bit.ly shortened URL which did go to the write server.

    I’ve logged into wordpress.com but can’t find any Jetpack settings. Site settings here all look right, and I’ve even just tried to nuke and re-attach the three social accounts, but they don’t want to play nice.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Such problems can happen when copying the whole database of your test site (including the Jetpack options) over to a new URL.

    Disconnecting / reconnecting to WordPress.com should update your site settings. If it doesn’t, please let me know your site URL, and I’ll be happy to have a look!

Viewing 15 replies - 1 through 15 (of 56 total)
  • The topic ‘JetPack Publicize uses wrong URL for Twitter’ is closed to new replies.