@Kops I think both derived inspiration from the same source. And I think it’s okay to feel inspired when you bring your own interpretation to the table. We’re designers, but that doesn’t mean we can’t be inspired by others designs and products. I for one love the simplicity in Apple’s products.
Rosa is not an original design, if you know what I mean. Take a look at Dribbble profile of Mike | Creative Mints and if you will search for a project on 21 March 2014, you’ll see what I mean
How do you know it’s not a massive job and a tiny job, because you can’t code it yourself?
In order to get something done, you’ll need to first get someone to do an evaluation for you … Going on that mindset is completely wrong and I can see where your project is going and why it will be avoided by most professional developers.
Please take my response as constructive criticism and not as a personal attack, I’m just trying to help you out get a better grasp of things.
Too bad I’m missing the first meetup, since I’ll still be in Germany! I would have loved it, though!
1) Escape as late as possible. You’ll never know how data can be manipulated. You might think you thought of all the cases, but someone else still finds a loophole.That’s why there are guidelines into place. Which were set by other developers, which are working on the core of WordPress: http://vip.wordpress.com/documentation/best-practices/security/validating-sanitizing-escaping/
It’s best to adhere to some best practices of WordPress, since you’re working with WordPress.
2) I’m sorry to say, but it’s quite ridiculous to load every script even if it’s not needed, just to expect the customer “maybe he needs it”. Load the scripts only when the shortcode is used, this will definitely won’t be a problem with the review theme. Use some conditional logic
Hopefully I didn’t come out as harsh, as I was just trying to help you improve and understand better the current pain points that you are having, and that basically you were doing it wrong. Get familiar with WordPress, it’s mantra, it’s standards, and your code will improve and review problems will be gone.
Usually it is good to contact the theme developer from where you purchased from through his support channels, in order to get proper assistance. But, did you try to use the : “Settings > Permalinks” from your WordPress Dashboard and just click on the button with Save on it? It usually fixes errors like the one you currently have.
A more realistic figure for this amount would be around 28k-30k, if you are starting at 50% and you are not an elite author. But getting that amount is really hard.
DigaCoder, instead of focusing on the money and get rich quick scheme, I’d advise you to first create a meaningful product, which solves the issue of a customer, and then think about money.
You won’t have to pay ThemeForest anything with what you sell on your own website.
You are paying a buyer fee just when you purchase the Magento theme itself ( a one time transaction ), from ThemeForest, which is included in the price you see here.
So after you purchased it, your business will not have any connection with TF. Your business is your business
Hopefully things are clearer now.
It always helps to show a link of your theme and the soft rejection message. Usually, when it’s a soft reject, it’s really close to a release. Just a couple of small tid-bits which need to be sorted out. I’m sure that the community can help you on this
Anps, I also had this problem and I think I know the root cause.
When you created a demo XML import file and you exported let’s say the configuration of the Contact Form 7 plugin, you also exported your e-mail address there by accident. So now, whenever one of your customers is using your theme, he maybe forgot to change his e-mail from the one that currently is (yours) and you get those e-mails. I know, I did that mistake and I received plenty of funny e-mails like: “Can I get an appointment for bride make-up and hair styling?”
Ok, sorry about that Thanks for the response!
Also, on topic: When you’re using it as a plugin, I think you’re just simply following the WordPress philosophy: Functionality in plugins, Design/Appearance in Themes.
So your theme should work and not break as a simple stand-alone theme without any plugins first. Then, you can further extend the capabilities of the theme, by providing compatibility with various available plugins (like WooCommerce, Unyson, etc.) So whenever one of my customer doesn’t want to use this capability, then they are free to do so, their theme is still functional. It’s more of a “Features as plugins” model…
That’s at least what I do in my themes.