You need to include it in the main file package that you upload.
I am pretty sure that this is not allowed. All files must be readable and work on a standard shared hosting. Both is not the case with this framework.
“implemented as a C extension”
What does that mean? Are there are binary files? Or does it require a special loader on the server?
If i’m not wrong, many WordPress addon authors requires item purchase codes to activate there plugins ?
Not only WordPress developers but also CodeCanyon PHP developers. That is totally legit according to the TOS. It does not matter what the knowledge base or the staff is saying, the only thing that counts are the TOS.
It is not even funny anymore. Everyone tells you something different. Even the reviewers told me that it is allowed to verfify the purchase code within the application setup. Why shouldn’t it?
Fact is that there is no such term in the TOS, and i honestly do not care what your knowledge base says, easy as that.
The item, and all advertised sub-modules and features, needs to be functional right out of the box without user intervention.
That is a wishful thinking and not possible. Many applications require the user to do some configuration, e.g. the mysql data, site specific values and more. Your thinking might work for WordPress plugins but surely not for a complex standalone software.
Items aren’t permitted to ask the user for a purchase key or license code to unlock the item or part of it. License keys are still allowed to create buyer specific support systems and forums.Hopefully this info helps.
Can you show me where this is located in the TOS? Are you really going to tell me that I am not allowed to use the envato API to verify the purchase code?
It’s ridiculous how the Envato team does not even know the TOS themselves and keep spreading around false information.
Authors ARE permitted to check the purchase code if they want to.