Just so you know, another user posted something similar recently concerning this issue and I responded
with details about some possible solutions here
. There is no perfect solution though and even the suggestions I made can be labor intensive and prone to breaking over time as each social network changes how their APIs work.
Frankly, it's entirely possible that in a few years, some networks may not allow their buttons on non-https pages. If you work very hard to keep your count growing on http pages, a future update may permanently break that and reset those pages back to 0 when the counts are even large.
With that said, the idea of 'force scheme after date' is not feasible. For Joomla content, it *may* be possible, but even then, things like the creation date, publish date and other dates can be changed at will, whether intentional or not. However, JFBConnect can add social buttons to any page from any component, and not all of them have datestamps for when the page was first publicly accessible and there's no way we could make something that worked across every extension as there's no forced scheme for a component to use to set dates. Unfortunately, it's just not possible.
I hope the above helps explain things more. It's not a situation we like either, but about 3 years ago, we made the switch to https-only and lost our counts as well. It's not fun, but at least we know we'll keep the count we have now.. until we change our SEF format or move to Joomla 4 with a new routing system or some other URL change crops up.
{JFBCComments} plugin http to https
