3007 posts
  • 5 Years of Membership
  • Affiliate Level 5
  • Author Level 9
  • Bundle Boss
+8 more
duotive
says

No offense, but with these changes you will only make the customers here have a worse experience than before, because your standards are not clear and do not cover every aspect and every author will end up choosing their own way of doing stuff. This changes are just bad. The only one i have to say i agree with is the shortcode one. The other moves to plugins are just useless.

At the moment i have spend some time reading this whole thread and i am clear of one thing: you have no idea what you want us to do.

I think that you want to make the functionality part of the theme portable to other themes. Basically what woocommerce does. BUT what author wants to spend time on a plugin for lets say their slideshows, and than allow the buyer to take that plugin and use it unlimited times with other themes. What is that? You are confusing wp.org with premium themes.

302 posts The Joomla Guy
  • Author Level 12
  • Power Elite Author
  • Winner
  • Featured Item
+12 more
hogash
says

Hy guys,

@Envato team : Instead of moving all functionality to a plugin, can’t we still keep the CPT ( for example ) in the theme and just add an extra plugin in the theme package that will contain just the functionality of the CPT ?

How i see the things :

1. The user installs the theme 2. The user can benefit from all the theme features ( portfolio, shortcodes , etc) 3. The user want to switch to a different theme and disables the first theme ( at this stage, he will lose all the theme features – CPT , shortcodes, etc ) 4. The user ( if he still want to use the first theme’s features ) installs the plugin provided in the theme package and he will get the CPT and shortcodes functionality

By doing this, the clients and developers are happy ( in my opinion :) )

my 2 cents :)

Best regards, Stefan

815 posts
  • Affiliate Level 1
  • Author Level 5
  • Collector Level 1
  • Freebie
+3 more
rvision_
says

What about dependencies between the theme and the plugin.
- If I have some functions that are used both in the cpts and regular posts, where should I put them?
 if (!class_exists('myclass')) require_once('myclass')

?

633 posts Dream big
  • Trendsetter
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
+6 more
pixel-industry
says

How i see the things :

1. The user installs the theme 2. The user can benefit from all the theme features ( portfolio, shortcodes , etc) 3. The user want to switch to a different theme and disables the first theme ( at this stage, he will lose all the theme features – CPT , shortcodes, etc ) 4. The user ( if he still want to use the first theme’s features ) installs the plugin provided in the theme package and he will get the CPT and shortcodes functionality

By doing this, the clients and developers are happy ( in my opinion :) )

my 2 cents :)

Best regards, Stefan
This was my idea too. I am curious would this be allowed?
954 posts
  • Affiliate Level 1
  • Author Level 3
  • Beta Tester
  • Most Wanted Winner
+3 more
aleluja
says

^ But why? Ok, for editing old themes it’s much easier, but if you’re making a new one I can’t see one reason to have code duplicated when the effect is same. Plus, who the hell would keep the files he downloaded 3-4 years ago (when he installed the theme). That item would probably be deleted and there would be a hurricane of “OMG WHERES THE ITEM I NEED THE PLUGIN”.

302 posts The Joomla Guy
  • Author Level 12
  • Power Elite Author
  • Winner
  • Featured Item
+12 more
hogash
says

Hi guys,

What’s hapening here ?? Our theme Kallyas for wordpress that was released earlier this year was just soft disabled. The email we have received states that the theme is not compatible with the new requirements ??

We have also opened a ticket ( #WLT-286-98234 ) if someone can investigate and give us a proper reason for the disable.

Best regards, Stefan

16 posts
  • 5 Years of Membership
  • Brazil
  • Collector Level 1
  • Exclusive Author
theux
says

+1


wp.org != premium themes.

16 posts
  • 5 Years of Membership
  • Brazil
  • Collector Level 1
  • Exclusive Author
theux
says

Hy guys,

@Envato team : Instead of moving all functionality to a plugin, can’t we still keep the CPT ( for example ) in the theme and just add an extra plugin in the theme package that will contain just the functionality of the CPT ?

How i see the things :

1. The user installs the theme 2. The user can benefit from all the theme features ( portfolio, shortcodes , etc) 3. The user want to switch to a different theme and disables the first theme ( at this stage, he will lose all the theme features – CPT , shortcodes, etc ) 4. The user ( if he still want to use the first theme’s features ) installs the plugin provided in the theme package and he will get the CPT and shortcodes functionality

By doing this, the clients and developers are happy ( in my opinion :) )

my 2 cents :)

Best regards, Stefan

That’s not simple. Plugins developed to a specific theme will carry the theme’s style. It will not be a plug and play thing for other themes. For example: future plugins from Kallyas will not be useful for people that have Avada theme. Completely different styles. In the end, Envato will ‘force’ the user to code and tweak plugins.

Like @duotive said, i think Envato is confusing wp.org with premium themes.

I quite agree with Submission Requirements Phase One, but phase two is blurry.

1642 posts
  • Elite Author
  • Featured Author
  • 6 Years of Membership
  • Author Level 10
+8 more
fuelthemes
says


Hy guys,

@Envato team : Instead of moving all functionality to a plugin, can’t we still keep the CPT ( for example ) in the theme and just add an extra plugin in the theme package that will contain just the functionality of the CPT ?

How i see the things :

1. The user installs the theme 2. The user can benefit from all the theme features ( portfolio, shortcodes , etc) 3. The user want to switch to a different theme and disables the first theme ( at this stage, he will lose all the theme features – CPT , shortcodes, etc ) 4. The user ( if he still want to use the first theme’s features ) installs the plugin provided in the theme package and he will get the CPT and shortcodes functionality

By doing this, the clients and developers are happy ( in my opinion :) )

my 2 cents :)

Best regards, Stefan

That’s not simple. Plugins developed to a specific theme will carry the theme’s style. It will not be a plug and play thing for other themes. For example: future plugins from Kallyas will not be useful for people that have Avada theme. Completely different styles. In the end, Envato will ‘force’ the user to code and tweak plugins.

Like @duotive said, i think Envato is confusing wp.org with premium themes.

I quite agree with Submission Requirements Phase One, but phase two is blurry.

I totally agree, Phase 1 changes are great, but phase 2, not so much…

516 posts
  • Super Copyright Ninja
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
+8 more
Jaynesh
says

Hi guys,

What’s hapening here ?? Our theme Kallyas for wordpress that was released earlier this year was just soft disabled. The email we have received states that the theme is not compatible with the new requirements ??

We have also opened a ticket ( #WLT-286-98234 ) if someone can investigate and give us a proper reason for the disable.

Best regards, Stefan

That’s quite scary considering that these requirements haven’t gone into effect yet AND existing items were meant to have a longer grace period.

by
by
by
by
by
by