-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-Envato Authors Version #11
Comments
Hi @jayism I think you can use Supportte right out of the box as a support theme - without using the Aqua Verifier plugin. I have not seen anyone do this, but it's possible. A while ago I asked some authors if CM has any API that enables them to verify purchases - but they told me there aren't any, so I'm not sure how CM authors support their items - perhaps manually adding them to the forum? Oh, and any help is highly appreciated! :) |
There are License Plugins available on CodeCanyon - they may/probably use this, and add them manually to the forums. Thanks. |
Could you point me to the URL for license plugin? Thanks |
BTW, what skill sets are you currently in need of. We are a new Collab Group founded at Forrst.me/Dribbble/SocMedia - and most of our Head Dev's are at Uni 'til Xmas break (we are international) and a registered Organization in Australia (easiest to work with other countries, easy set-up & tax benefits etc). Anyhow - We are working on our 1st 1 official launches atm on 1/2 staff, but always make time to give back - especially as we are getting known, and we are all about collaboration as our Org. name suggests ;-) |
Hi, I think a Suportte theme for ALL digital products and (CC) Licensed products would be a great Idea. Maybe SUPPORTTE (Clean) v1.0 to start, and in future maybe some coders can help add different options to the admin - CreativeMarket etc as they continue to grow.
I think it will do a whole ot better for BBPress Support Themes, as there are currently ZERO Community based themes in development.
@Code_Collective would love to help out.
The text was updated successfully, but these errors were encountered: