• Resolved Gal Baras

    (@galbaras)


    The update links for the plugin still use the slug “woocommerce-com-facebook”.

    Clicking on this link brings up a WooCommerce.com changelog, which isn’t formatted properly.

    Updating the plugin results in failure with the message “An error occurred while updating Facebook for WooCommerce: Update package not available.”

Viewing 11 replies - 1 through 11 (of 11 total)
  • Morning @galbaras!

    Thanks for letting us know about this issue. Could you let me know what version you were upgrading from, and if you were updating to the latest v1.11.0?

    I ask because, I was using v1.10.2 and can see an update available, and the changelog looks okay from this end, with the correct slug: https://cloud.skyver.ge/xQuWDQLg

    I’d be grateful if you could send over a screenshot of what you’re seeing, and if you could try installing the latest version by first removing the older one and uploading the newer version directly: https://downloads.www.ads-software.com/plugin/facebook-for-woocommerce.1.11.0.zip

    Do you still see the same error even with the manual install?

    Cheers,

    Simon.

    Thread Starter Gal Baras

    (@galbaras)

    I was on 1.10.2.

    The plugin wasn’t configured on both of the sites where it was installed, so I just deleted it and reinstalled, and things seem fine now. Hopefully, they’ll remain that way when there’s an update.

    Thanks @galbaras!

    We have seen an issue similar to what you’ve mentioned previously, though there was a fix added to resolve this. I wasn’t able to see the issue again my local testing, and as far as I’m aware, the developers haven’t seen it since either.

    If you do encounter it again, please do reach out to let us know so we can take a closer look! Though, it’s great news it’s back up and running again now then.

    Is there anything else I can help out with today?

    Cheers,

    Simon.

    This has been forever and I cant update either. That is the new issue.

    Thread Starter Gal Baras

    (@galbaras)

    Delete the plugin (use FTP if you want to keep your data) and reinstall it.

    Hi @landed and @galbaras!

    A further update on this after I checked in with our developers. I was previously mistaken on what version the fix was included in. I do apologize for the misinformation!

    The change was made in v1.11.0 and should hopefully prevent this from occurring in the future. The problem is that it wouldn’t take effect until after v1.11.0+ is installed.

    So you may still see the error while installing v1.11.0 at the moment, but the next automatic update after this should be fine. For now, if you could follow Gal’s steps, that should get you back up and running.

    Of course, if you then notice the issue again with the future updates, please do let me know!

    Cheers,

    Simon.

    Thread Starter Gal Baras

    (@galbaras)

    @skyverge (Simon) it will be good to redirect the old plugin slug to the new slug on wp.org, even temporarily. This is a simple way to help everybody update seamlessly.

    Hey @galbaras,

    I checked in with the developers quickly and as far as they’re aware, it isn’t possible to add a redirect to the www.ads-software.com downloads.

    The automatic update issue doesn’t seem to happen for everyone either, as we’ve not been able to replicate the issue on any of our test sites, and have had only a handful of reports compared to active users.

    With the latest release including the code change, we hope this will be a final fix for everyone. Thanks so much for your patience so far.

    Cheers,

    Simon.

    Thread Starter Gal Baras

    (@galbaras)

    Hey Simon,

    Your developers won’t be able to modify wp.org, but they can use plugin author channels (Slack?) to request that of the people who run the site.

    It should make some (many?) lives easier.

    Cheers,
    Gal

    I went to do a direct removal and install over the top today and somehow the plugin was up to date? So I am happy now and hope this plugin can get better.

    FYI the notes attached to changelog are not readable the html code is not parsed correctly. Hope this long standing issue will also get fixed.

    THANKS for making and keeping this plugin going.

    Hi @landed,

    Great to hear! Yes, the changelog issue not being formatted correctly is all part of the same issue. So now that you’re on the latest version, it should be fixed and shouldn’t occur with future updates.

    If you do still see it though, please let me know so I can loop our developers in to take a closer look!

    Cheers,

    Simon.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Incorrect update link’ is closed to new replies.