@scottpaterson – Hi, Scott,
thanks for posting here, again.
I’ve provided exact code that their developers could use to fix this issue
– could you be so kind to provide an exact link to this? From what I’ve seen in the past, you haven’t done this but implied it “should be easy” to do so, even though we’ve explained, numerous times, that until Google decides to patch OpenSSL with PHP 8.x, there’s not much we can do about it.
I thought that would be obvious to a developer.
– we’re not all developers and this is NOT a developer-focused product.
Currently they will not respond to my support requests, even thought I have purchased their lifetime license on their site.
– that’s, again, a false claim. There’s no point in replying with the same answer, over and over, and you claiming you’re not happy about it. We’ve done this, repeatedly. You seem unable to accept the fact that it’s outside of our control.
YES we do offer support for our product. YES we will support your lifetime purchase. NO, we will not be forced into doing something we don’t believe is either right for our product nor actually possible (the current scenario).
Badgering us about getting PHP 8.x in KB support faster, just because you think it’s all about: “speed, security, it’s the future of PHP” isn’t going to happen any faster by leaving a 1* review.
It’s your right to express your opinion here and I truly appreciate you taking the time to do so. I reckon you must be busy with all the plugins you’re submitting “exact code that their developers could use to fix this issue” …
I’m sorry to have to say this again – but the PHP 8.x support will be added when OpenSSL will be patched to work with PHP 8. Until then, I’m afraid there’s nothing we can do about it.
Take care and stay safe!
Warm regards,
/Cristian.