• Resolved jalira

    (@jalira)


    Hello,

    I have just switched from http to https (https://bastelrado.de/). All https sites and posts are redirected via 301. Im using Shariff 4.3.0.

    Problem: Unfortunately after the conversion none of my share/like counters are visible in the frontend anymore. Also in the backend all counters are zero ?? (settings -> shariff-> ranking). This applies to all social medi buttons and not only one.

    Question: What can I do to get my “old” counters back (from http-sites) and show them on my new https-sites? Any hints or feedback is very much appreciated.

    Thanks a lot in advance,
    JaLiRa

Viewing 5 replies - 1 through 5 (of 5 total)
  • This is unfortunately the disadvantage in the changeover from http to https. Facebook considers the URL with https as a new URL, which is not related to the old http URL. At the moment, no solution is known about how to change this.

    Plugin Author Jan-Peter

    (@starguide)

    What detoris wrote is correct. There is nothing you can do about that, because Facebook and others think that these are two different URLs. So all shares in the future will be counted under the new URL with https. Facebook sometimes merges the two URLs after a while, but till today I only have seen that happening with larger sites in the ranges of a couple thousand shares per post. For small sites – unfortunately – the old share counts will probably be lost. That was one of there reason why we implemented the “hide share count when zero” option, so older posts are not all showing a zero.

    Cheers,
    JP

    Thread Starter jalira

    (@jalira)

    Oh, that’s a pitty :-(. But anyway: Thanks a lot for you answers.

    Hey guys,

    I have exactly the same problem.

    –> Couldn’t you add a feature that looks up the counts for both URLs, http and https?

    Ciao,
    Johannes

    Plugin Author Jan-Peter

    (@starguide)

    Hi Johannes,

    the problem is that we do not know, if an URL is being counted separately for http / https or not (it can be different even on the same domain) and therefore might show way to high results. Doubling all request for each URL would also probably push a lot of people into the request limits.

    Since this problem solves itself after a while, when all your current posts are on https, creating a workaround isn’t quite high on the priority list – nevertheless I have it on my list of thing to take care of, if I’ll have more spare time again.

    Cheers
    JP

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[http -> https ] all old counters are lost’ is closed to new replies.