@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 centsBest 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…
Have you tried implementing them individually?
For instance my latest theme does each one individually like this:wp_enqueue_style( 'googlefonts-sanpro', "$protocol://fonts.googleapis.com/css?family=Source+Sans+Pro" ); wp_enqueue_style( 'googlefonts-sanpro2', "$protocol://fonts.googleapis.com/css?family=Source+Sans+Pro:400" ); wp_enqueue_style( 'googlefonts-sanpro3', "$protocol://fonts.googleapis.com/css?family=Source+Sans+Pro:400italic" ); wp_enqueue_style( 'googlefonts-sanpro4', "$protocol://fonts.googleapis.com/css?family=Source+Sans+Pro:600" ); wp_enqueue_style( 'googlefonts-sanpro5', "$protocol://fonts.googleapis.com/css?family=Source+Sans+Pro:700" );We found if you did not do it this way, sometimes for some unknown reason they did not work.
That’s interesting, never seen anyone do it like that.
We’re also launching a new feature for elite authors Tuesday AEST next week. Elite authors will be receiving an email with more details on the day.
so it was not a surprise but a secret that only elite authors knows abouthope you tell us also or we may start to think is something bad for us
Haven’t got any email yet
@OriginalEXE: Yes, I did and using various methods.
bianca: Its happening with Oswald font-family, but its not really a buggy rendering issue. Its simply not working.
Have you ever run into problems while using multiple weights of the same font?
For some reason, my friend cannot view heading tags with custom web fonts when they have different font-weights applied. Happening on Chrome on Windows, but only for some pcs, not all.
There is already a plugin that converts CPTs for future use.
Since the plugin only lets you view the data without using them, can’t the user just export the CPT as xml or back up their data before changing themes? They can switch back to the old theme whenever they want.
If every author has a plugin for himself, how is this modularizing themes? User will be able to see their previous data, but won’t be able to use them in the new theme. This does not really solve anything.
If we are really going forward with moving shortcodes and cpts to a plugin, I believe its best that Envato supply a boilerplate plugin.
A boilerplate plugin by Envato will push authors to use the same codes for their supporting plugins which will in return, make lives of reviewers easier.
ThemesDepot saidAt the moment, I believe that metaboxes will need to be in plugins for the phase 2 requirements. Do you see this as a problem?
Something that is not clear to me is : metaboxes must be in plugins?
Options Framework come with metabox support, so integrating the theme options, but placing metaboxes in a plugin is not an option
I think moving the shortcodes & metaboxes to a plugin is unnecessary.
Looks very good, one thing I would change is the setting colors as RGBA not HEX