Sorry. Look I understand what you're saying from a support point of view. I also think SMF should do something to kerb that message from showing when it's not needed, but can't see it happening.
I was merely pointing out that the database version message that accompanies a error message is a red herring and can safely be ignored. The error that it accompanies is the one that needs dealing with. If you see what I mean.
No one is saying you shouldn't try to fix it.
TP support I agree is a bit sparse, that's really down to the fact we don't have a active developer at the moment. and team members are a bit thin nowadays. My own knowledge is limited, which I will openly admit, but I wanted to keep the project alive so it didn't disappear altogether. Hence one of the reasons I took the project on. We (mainly down to illori's help) have managed two new versions since, TP 1.1 TP 1.2 A beta of TP 1.2R (Responsive). Plus a working beta of TP for SMF 2.1 beta 3.
We'll see what the next few months has to offer, and decide where to go on this. But yes support needs a good shake up, more staff and a good Dev.
