Quote:
Originally Posted by Vaira
You have missed the point. You have included the importer which reads abe1's tables into your paid version with the intention to make more profit. You know that abe1 has canceled support and that many of us are using his hack already.
To get paid for own work is out of question. Compared to your free version it is almost no effort to write a script that reads tables. Almost no effort to have most profit. Profit made because of the fact that we are using abe1's tables already.
If I am wrong than just provide the importer at your free version as well.
Anything else is pointless arguing to me.
If you would provide the importer at the free version as well, your profit will decrease. I know that and you know that and hence it is available at your paid version only 
|
Why don't you learn SQL a bit? You only need basic knowledge to run a query that'll import thanks from Abe's hack to DBTech's.
The only problem, for a newbie, might be importing stuff from 2 different tables (yeah DBTech's table doesn't match Cyb's table).
Cyb's "
_post_thanks" table has columns:
id
userid
username
date
postid
DBTech's "
_dbtech_thanks_entry" table has columns:
entryid <-- you copy Cyb's
id here
varname <-- you write "thanks" here
userid <-- you copy Cyb's
userid here
contenttype <-- you write "post" here
contentid <-- you copy Cyb's
postid here
dateline <-- you copy Cyb's
date here
receiveduserid <-- the only problematic column - you need to copy
userid from the '
_post' table, from the
postids matching the
contentid that you've just copied.
And no, I'm not gonna write the query here - if you don't wanna buy the DBTech's Pro version, then you should write the query yourself. With my explanation it should be easy enough, anyways.