Thank you everyone! I see I am not the only who thinks this is a little bit odd.
@pixeful: I am quite sure it is not a mistake, since we got 2 soft rejections and in the first one they actually created some screenshots which elements are too similar in both themes and should be fixed. Then we fixed all of them and provided detailed explanation what we changed and why. The second response was then just ‘the items are still too similar’.
@Anps: yes, it is a soft reject, 2 times now already. The problem is that we already made all the changes to make it even more diverse. It doesn’t make any sense to introduce some completely new elements or ruin the existing ones, just for the sake of uniqueness?
@surjithctly: backend/frontend code is entirely new, as we updated from Bootstrap 2 to 3, created new widgets or improved the existing ones, changed the filenames, dir structures, introduced Grunt build process etc.
@icesoft: yeah, I think the same :/
I don’t know yet how we will solve this…
Hello there guys!
We have quite a situation here and we want to hear your opinion about it.
For the last three months we were creating a new WordPress theme for restaurants (http://restaurant.demo.proteusthemes.com/). Two weeks ago we uploaded it and we got two soft rejections with the reason that theme is too similar to this one (Carpress – http://www.proteusthemes.com/themes/?theme=carpress-wp ) and that was it. We were not even close to get any useful direction on what should we change or do.
I must say we used Carpress theme as a foundation but in restaurant theme we changed almost entire .css file, changed style, size and position of almost all elements and added lots of new features (advanced plugin implementation, page builder, more options in live WP cutomizer etc.). No need to say that the code is entirely new, using new/better/different approaches.
It was quite an unpleasant surprise for us mostly because TF reviewers every day accept more than dozen single-page portfolios or Avada-like themes which all look the same. We saw a lot of authors just changing the colors and position of elements and having another “unique” theme accepted, but we wouldn’t dare to do so as the customers are lost then in the ocean of the same themes with different content.
We don’t want to criticise the reviewers as much as we want to get second opinion from other authors and staff members. Do you think this is fair, what do you think we should do in this case?
In the worst case scenario we could sell Restaurant theme on our own sales channels or make it free for the matter of promotion. But first we want to know what could we do to get our hard work approved on the ThemeForest?
Thank you all for help, Kind Regards, ProteusThemes
Just added the option that the first argument can be provided as the purchase code. If missing, the script will prompt for the input.
$ everify.sh e4e91153-XXXX-4483-XXXX-882ee0686787 # first argument is the purchase code
I tried that as well, but it still returns the result in one line. I prefer JSON anyway.
Yes, I tried to google for more ‘native’ approach, but as you said – linux and mac comes with python preinstalled, so it is the easiest option to use it
Looks good! (is that a real purchase code?)
Hey add a user agent like “everify by ProteusThemes” to that curl request. Devs said somewhere that they would like all API requests to have a user agent so apps can be tracked / they don’t get blocked.Edit: works well cheers!
I’ve added user agent header just as you suggested …
Yes, that is a real purchase code, but I will blur it now
To simplify the process of the verifying purchase codes I decided to write a simple shell script. I am a heavy terminal user and this is by far the simplest and fastest way to do.
I though that it might be useful for some of you as well. You can see instructions / download it here: https://github.com/primozcigler/everify.sh
Zendesk is really amazing piece of software, I cannot argue with that. I switched to it and we are satisfied with it.
But the problem is that it is not what we, Envato authors, need. At least not all of it.
We would need something that works pretty much the same as Zendesk, but it is very straightforward to setup and use. Most of the features there are a huge bloat and it really takes time to setup everything. Plus there is no integration with Envato. They have the APIs, but as far as I checked it will not allow to simply implement the purchases code checking.
So based on the terrible experience with the Ticksy and not-so-terrible-but-i-can-do-it-better experience from Zendesk I am developing a realtime nodejs app that takes best from the both spheres and that I believe will be the ultimate tool (not just for support) for Envato authors, at beginning especially for the ThemeForest as I am scratching my own itch
Some features that are already implemented or in-progress:
- trully realtime experience, no more browser refreshing, something like Zendesk is – or even closer to Trello boards (which I am huge fajn of)
- editing in Markdown, both for clients and agents
- option to verify the ticket AND optionally kind of ‘punishment’ for the clients who don’t verify, like the unverified tickets will be shown with 3 days delay to answer (to softly force the verification)
- all tickets are public, with optional (limited in characters) field for sensitive data like wp of ftp access
- very very powerful search
- all categories automatically synced with your items via Envato API
- automatically created tickets from the comments on the themeforest (author will just click to create a ticket and paste back on original comment on themeforest the link to asnwer)
- profiles with signatures
- internal comments for correspondence among support agents that are visible only to agents
- knowledge base
- auto-suggested answers when wiring ticket from the knowledge base
- macros for agents
This is planned for v1.0.0. But there is more than just support system in plan. What I also have in plan to add to the system is:
- automated system for split the earnings based on % per each item when working in teams
- keyboard shortcuts
- dropbox integration (like Trello)
- inside-ticket invoices – when the client will ask for customization, the agent will be able to create the invoice on-the-fly with link sent to client to pay it (Stripe | PayPal | ...)
- voting system for the features in products – the clients can suggest the features for the items (moderated by admin) and with the voteups the other clients can vote for the next features implemented – very powerful for the authors to see what is most desired in the items
- social engagement – suggest client to tweet/like about your brand when the ticket is successfully closed
- automatic replies to email out of the predefined working hours
- optionally paid support for example after 6 months after the purchase of the item (we cannot provide forever free support for $40 a piece)
- option to import/export in standard formats the whole DB of ticket and KB articles – if you find a better solution elsewhere or something happens to me or the project, I don’t want you to lock in our software
I would love to hear your thoughts about this.
I am not sure yet if that will be opensource project or SaaS. Maybe both. At least I think that for 1 user it will be free, for more it will be paid. Or something like Ghost, free if you want to host it yourself, paid for SaaS.
I have the first VERY alpha release online already, everybody interested in for being alpha/beta testers, let me know somehow!
Alpha version works already, but very few things are implemented already, and there is no design applied to it and no UX done for better usability
But if there will be huge demand for the app and that would somehow pay for itself, I could speed up development.
(As you can see from when this post is pusblished) for now I am spending some Saturdays developing this system, but if you guys are prepared to somehow ‘fund’ me or provide some kind of assurance that would be prepared to pay (and how much) for this kind of ultimate solution, I can devote more time to it.