No, authors are not allowed to do that unless they have an agreement with each other (for example, Author A made a WP theme and Author B made an agreement with Author A to sell a Joomla theme of the same design).
If both themes are sold in the same category and look almost the same, but sold by different authors, I think there’s a high chance that it could be a rip-off which, in this case, it’s better to contact Envato support to let them investigate it.
As FlatKing pointed out, change those things. Also, the font for header navigation menu.
However, after fixing those things (and some other problems), you could still be rejected due to ‘originality’. From what I see, the current theme design, layout and almost every element is already found in some other themes, so what makes you think that buyers will want to buy yours and not others?
That’s something which only you can answer and solve if you want it to be accepted and generate good sales.
Thanks and good luck.
HellasDesign saidPost formats are integral components of WordPress. You just need to enable them in your theme’s functions.php file : http://codex.wordpress.org/Function_Reference/add_theme_support
Because I am new to Wordpress… Do I have to create a plugin for the Post Formats (e.g. video, image, quote, status etc)? I am using a Framework for my new theme and I don’t know if I have to create a plugin for these Post Formats or not. Thanks
Well, I think it depends on whether you are willing to spend the extra time to make a good documentation and ‘fill’ the files with placeholders. I released my HTML template before completing the WordPress version (which was released about 2 months later).
Did someone rip off my HTML template before I released my WordPress version? Yes. Did someone share my WordPress theme illegally after I released it? Yes. Basically, no matter what you do, your items will definitely get ‘ripped off’, but I believe those who got them through ‘other means’ do not intend to use them on their actual website anyway.
With that said, providing both HTML and WordPress versions allows buyers to choose what suits them the most. Up till now, there are still people who buy my HTML template occasionally although there is a WordPress version available because it might be more suitable for them if they don’t update their website frequently (in terms of adding blog posts etc.), or that they just want to port it to fit their own CMS.
I don’t think it’s possible because you will need the ‘complete’ package if you want your submission to have even 1% chance of getting approved.
If you’re thinking of doing this just to check whether your design / concept is acceptable, perhaps you can submit the design to PSD category, or some relevant categories which can be done with lesser preparation / work. Usually if it can be accepted in one category, it will be accepted in another but if I have not mistaken, an item can only have a maximum of 3 ‘variations’ (i.e. PSD, HTML and WordPress, or HTML, WordPress and Joomla etc.).
Hope that helps.
gnosis21 saidAlthough this might sound good for buyer, but don’t you think the prices are too cheap if support is obligatory for 3 years? If this were to be implemented, I can see many authors leaving / not producing new items for the marketplace because 3 years is too long in the Internet world.
I think basic theme submission requirement should be obligatory support and theme updates for theme buyers at least for 3 years. Because with current situation almost all WordPress themes after year or so turn into garbage and sites running them are dysfunctional because theme authors don’t make updates for newer WordPress versions. 3 years should be obligatory minimum that theme will be compatible with new WordPress versions, otherwise what’s the point in buying WP theme?
WordPress 3.0 was released in 2010 (about 3 years from now). Look at how many major releases were there in the past 3 years. It’s quite difficult to get a theme working in so many major releases when there are new / deprecated functions in each release (most themes here are not as ‘basic’ as free themes, hence they are more prone to problems due to the extra scripts / functions used for various effects / features). Even WordPress encourages developers to support only the 2 latest major WordPress versions.
When authors update their items, we don’t get extra exposure (i.e. we’re updating it but only the buyers know, and maybe those who used the not-so-efficient search in TF). So the time is ‘wasted’ in working with old items which do not generate much sales rather than working on new items with better design / features. This is also why there is information about the compatibility of the theme so that the buyers can decide whether it can run on what they are using.
In simpler words, obligatory support with the current pricing structure is impossible. Perhaps the prices should be increased by at least 3 folds if it were to be implemented, or as an extra ‘opt-in’ purchase (like how you pay for extended warranty for computers).
Congrats! You’ve built up quite a good portfolio within such a short time, whereas I’m still ‘stuck’ at only one design (but still working on adding new features to it now)
I believe this can be achieved with any WordPress theme (which also includes mine). You just need to assign multiple categories to each work (i.e. both Video and Artist A, or Animation and Artist B etc.). However, you will make the artist a child category of the ‘creative work’. If you have an artist with multiple works (eg. Photo and Video), perhaps you can find a taxonomy plugin for that since a category can only have one parent category.
Otherwise, I think making the artists as a tag works too, without having to rely on any plugins. Of course, this is based on what I can get from your description of what you want to achieve.
... This is why I expected there to be a ton of topics opened here on the forums about working together. You all have businesses in an open source community. The new submission requirements are a perfect opportunity to truly take advantage of this fact.
What I mean by this is that people from the TF community should be creating GitHub projects to handle these things so that users aren’t running into these problems. As theme authors, you have an ideal chance to work together and build something that’s actually useful for your users in both the short and long term.If all TF theme authors are putting their own shortcodes into their own plugins, then everyone is kind of missing the point that the phase 2 submission requirements are attempting to address. ...
... Whether the plugin comes from the authors collaboration or officially from Envato, it should be working great in this case for both users and authors. (Not quite sure that this is too ideal or practical in the real world though.)
Unfortunately that the phase 2 of the submission requirements didn’t state anything about this. I could see only “the functionality/shortcodes must be in the plugin” stuff. If the situation is still like this until the effective time comes (November, 2013), I’m afraid that the authors, including me, couldn’t avoid creating self plugins containing shortcodes to pass the review process (and yes, the issue like the sample scenario in my second question will persist).
I didn’t really follow through all the pages in this topic (and the original one which was locked) because there are too many pages to read through. So, based on what I can deduce here, I seem to be ‘stuck’ in the same situation as UXbarn because I’m not sure whether I should be developing a plugin for my theme, or someone has already done one for shortcodes / custom post types?
If there’s no ‘common’ plugin for all TF authors, I’m afraid that each author will have his/her own plugin for all his/her items. In this case, although the same plugin can work well across all items by the same author, it defeats the purpose of the new requirement as it’s not really much different from bundling those things in our themes.
I totally support the new theme requirements but as of now, there doesn’t seem to be any ‘common’ plugin available, or any sign of it coming soon. So the main question is, should I be creating mine (which will still output the content in case a user switches but without the proper styling, as UXbarn’s hypothetical scenario which is likely to happen), or there is something more ‘popular’ among TF authors for shortcodes / custom post types?
Well, probably Envato is worried that authors might ‘abuse’ it by doing frequent minor updates (which will add to the reviewer’s workload). Also, it is difficult to determine whether an update is ‘major’ (it’s very subjective).
What I would suggest is, perhaps, themes should be shown in this new section if the last update / release date was at least X months ago (maybe 2 / 3 months?). In this case, authors are also encouraged to support their theme for a longer duration since they will get ‘rewarded’ for that. Also, authors would rather add more features into each update rather than having minor updates every few weeks.
I personally have been updating my theme periodically for almost a year since it was released (still doing some updates now) and it’s definitely much more ‘refined’ than it was at the time of release, but I don’t think many people check my updated theme after getting ‘drowned’ in hundreds of new themes released throughout the months.