I just zip everything up upon release then do the same creating new zips with every version change must learn git
When using this desktop software, you don’t need to be a master of git. I find that it is enough for me to know two buttons from this software, “commit” and “sync”. It is enough for me to track the changes of the codes on my repos.
Yes, I pay for private repos.
As GravityDept mentioned, you can use bitbucket, it supports free private repositories.The reason I use GitHub even though I have to pay for it is because I find that it has a better interface.
That’s true, Github web interface is better than BitBucket. But having many private repositories makes me use BitBucket for free unlimited private repositories, but I still use Github for free repositories.
But, for my daily work, I use “Github For Windows” software to manage both my Github repos and Bitbucket repos.
But themes with advanced integration are POSSIBLE to be released as different theme.
I think that the problem with this though is that buyers are missing out.
Let’s say I release a new theme, it sells well, buyers ask “eCommerce?” and I say “Yep, we’re releasing an eCommerce version separate to this one”
So buyers then have to buy 2 themes if they liked the original enough to buy it and hoped that eCommerce was on the roadmap for the original theme.Overall this seems a very grey area, platform to platform makes sense, no problem, but upgrade / downgrades within the same platform and the same theme seems like a risk to a flooded marketplace.
Hi Tommus, your example is a little bit different with my post above. Sorry if my post was not very clear. Jremick case applies to different eCommerce platforms. But for your case:
Standard Theme = A theme, Standard Theme + WooCommerce = B theme
I will also say NO for this. Because A theme will be a “lite” theme for sure…
I totally understand this, but it’s not like WordPress has it’s own shortcodes built in so if users change the theme, the shortcodes will simply work! And I was looking over http://wordpress.org/plugins/shortcodes-ultimate/ this plugin. It’s fine, I’ll integrate it into the theme’s stylings so it fits in really well and bundle it as an optional plugin for the end-user, but what if they plan to use a different plugin than this one? It will not fit in the theme for sure, and should they change the theme, it won’t be the same anyways. It’s really making me nervous at this time and I’m not sure on how to proceed considering the fact that I’ve spent quite a few days putting some great shortcodes in the theme. Sure if the user changes the theme, they will probably not work the same anymore, yet I call this the end-user’s decision and I could let him know about this before purchasing the theme. Do you get my point here? What do you guys think?
This is also OK for me. Some TF themes use this plugin also. I do not want to call the theme name, search it.
In the end, there are many solutions that you can use. We only give some suggestions here. Choose the one that you are comfortable with.
Ah I see, that’s a start. I would have problems understanding what exactly is “Extended functionality and theming” or “Unique designs”… I don’t know, that sounds unmotivated and very generalised. To me, it probably could be summarized as “well, it needs to work with the eCommerce and just look integrated”.
I see that this case is specific for WordPress eCommerce platform. It doesn’t mean that bbpress version, buddypress version, etc can be released as separate themes. It is different case.
You know what, we can easily say that all well-coded WP Themes should be “compatible” with WooCommerce without any code changes.
But, some authors then customize the styles to match with their theme, it falls to basic integration.
Then, some authors extends it by custom shortcodes, custom widgets, custom features, etc, that specific to a eCommerce platform. it falls to to advanced integration.
In my opinion, themes with only basic integration should NOT be released as different theme. But themes with advanced integration are POSSIBLE to be released as different theme. The reason are simple, UPDATE & SUPPORT. It is not easy to maintain a SUPER theme that has advanced integration to some eCommerce solution at the same time. So, releasing as different theme can be a good reason for this.
Don’t worry, it doesn’t mean everyone will release similar themes for every eCommerce solution with advanced integration. It means that you have to be a master to understand everything and you have to be ready with customer supports for different platforms. Many authors seem to choose WooCommerce because it is the most popular, user friendly, and developer-friendly at this time.
In the end, TF reviewer will be the final judge when you submit it. And I hope jremick can come with detail clarification to make it clear for everyone here to minimize grey area.
jremick saidIt would be interesting to know where the line would be drawn here. It sounds pretty blurry and I’m sure it will cause confusion if there’s not a list of features that need to be included in order to define an item as eligible for sale.
a “lite” theme vs “standard” theme would not be allowed. However, an eCommerce version of a “standard” theme, built more specifically for eCommerce functionality, etc. would be allowed to be sold separately from the “standard” theme.
I think the latest contest describe it enough, you can see “advanced integration” criteria for WordPress eCommerce platform.
- Inclusion of customized shortcodes, widgets, sidebars, and/or templates utilizing the eCommerce platform functionality.
- Extended functionality and theming for eCommerce relevant features.
- Integration and theming of additional eCommerce platform specific plugins/extensions.
- Unique designs that serve a real market/industry
This is my own interpretation, btw…
this is awesome news. because having that new rule is a great thing but if we can just do as we want depending of our interpretation then is fantastic
one thing we can do just now is throwing a rave party at envato headquarters, working hours only. I will bring the beer but we need to stock it somewhere. Did some of you have the key to Collis office? If not, we will break the door.I drink Guinness, if someone have other preferences please let me know.
Sad fact but it is true. It does happen several times here. I send a real example via message to you. Check your email.
Basically, I can say that there is no change on the rules here. It is only on our interpretation, and different author has different interpretation here.
And, this is only because some of us think that doing anything to get more sales is allowed here. And when Envato said, “don’t do that”, then some of us said, “oh, Envato changes the rules”... I can say that it is not “his” first time…
I think, it is better if Envato can make a dedicated page to show the rule, “easy to read” DOs and DON’Ts for authors. So, it can be good author guidelines before doing anything that possibly cross the line.
I might not get it. How about themes that use Revolution Slider ? They all contain a zip file with this plugin so the buyer can install it and get the functionality from the demo, isn’t it ?(without the need to separately purchase the plugin) Is this against the rules even if the author bought the slider with extended license and got written permission from the plugin author that is ok to do this ?
That is perfectly okay because it is default rule in ThemeForest, Extended License + Author Permission.
The issue on this thread is different, the Premium GPL Plugins are from outside Envato Marketplace (from two different companies) and there are no written permission from plugins authors. You can read the detail here, http://coenjacobs.me/en/dont-buy-bundled-premium-plugins/