Posts by EugeneO

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

why do you need to know everytime you have a sale, that would drive me nuts…
Being notified when you make a sale isn’t a problem. The problem is when you stop hearing the notification sound because your items have stop selling.
405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

“One-page” would not make sense as a category as it describes the layout of the item rather than the intended use (which is what the existing categories do). It would make more sense to add it to the item info beside the existing layout description (responsive, fluid, fixed). However, if this was added it should be possible to mark an item as having both a one-page and multi-page layout as they are not mutually exclusive.

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

Custom post types should be packaged as plugins instead of as a part of the theme. The new submission requirements deal with this issue specifically.

http://support.envato.com/index.php?/Knowledgebase/Article/View/472
405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says
This:
(function($) {
“use strict”;

//Author Code
})(jQuery);

...is the same as this:

jQuery( document ).ready( function( $ ) {
"use strict";

//Author Code
)};

It sounds like you are using the long form of the document ready function and then trying to wrap it in the shorthand form of the document ready function. You need to use one or the other.

The code provided by OriginalEXE and Tommus are the same and are exactly what you need. They meet the theme requirements.

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

From my understanding you can use the Site Origin page builder plugin with your themes sold on ThemeForest as the license only stipulates that you can’t bundle it (hardcode it) into the theme.

If you make your theme compatible with the plugin with custom CSS styles and either inform buyers that it is compatible or even use the TGM activation plugin to recommend buyers install it you should be fine. This paragraph from their website seems to support this:

That said, I’d suggest just encouraging your users to install Page Builder from the WordPress plugin repo. This will ensure they stay up to date with the latest version of Page Builder. It’s an actively developed plugin with almost weekly updates and bug fixes
405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

Looking at the item’s description the author is justifying it as a separate item because, despite the designs being identical, the old item (with WooCommerce support) is for commercial sites and the new version (without WooCommerce support) is for corporate sites and the two items will have different development paths going forward.

I don’t know how legitimate of a claim that is as to me there should be very little difference between a theme without WooCommerce support and a theme with WooCommerce support but the plugin not activated.

I’m pretty sure I read a rule somewhere that said two items in the same category (HTML, WordPress, Joomla, etc) could not share the same design and if they did they should be sold as one item.

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

^ This. Why try to reinvent the wheel?

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

If you are transparent and honest with your clients about your business practices then this isn’t a problem as your clients should already know you are creating their sites using templates.

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says

It looks good but for it to pass the new requirements a lot of the framework features as it stands would have to be separated out into individual plugins (mainly shortcodes, custom post types and possibly the sidebar generator). Until that happens we won’t be able to use it for themes sold here.

405 posts
  • Has referred 100+ members
  • Has sold $250,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+5 more
EugeneO
says


Moving towards a plugin centric is a good idea however for it to work I think we will also need some standardized plugins for the common theme features. Otherwise, we are going to end up with 1000 different shortcode plugins, 1000 different portfolio plugins, etc which is going to make things just as complicated. I know this was something that was suggested a while back but I don’t know how far the idea progressed.
That’s not good. Maybe one uses bootstrap for all their themes, maybe another uses skeleton, limiting the authors to certain plugins is like limiting clients from modifying the themes they buy
If the common shortcodes and features aren’t standardized to a select few plugins then your just substituting one version of a problem for another.
by
by
by
by
by
by