350 posts Gambit
  • 6 Years of Membership
  • Affiliate Level 3
  • Author Level 7
  • Collector Level 4
+6 more
bfintal
says

Aside from CPT and shortcodes, I would also like to know what else SHOULD be made into plugins. For example, in my themes, I have a MailChimp widget. Then in comment and contact forms I have reCaptcha integration. My themes also have their own translation and multilingual capabilities.

Should ALL of those functionalities be converted into plugins?

181 posts
  • Exclusive Author
  • 3 Years of Membership
  • Author Level 5
  • Collector Level 2
+2 more
HellasDesign
says

Because I am new to Wordpress… Do I have to create a plugin for the Post Formats (e.g. video, image, quote, status etc)? I am using a Framework for my new theme and I don’t know if I have to create a plugin for these Post Formats or not.

Thanks :)

734 posts
  • 4 Years of Membership
  • Author Level 6
  • Beta Tester
  • Affiliate Level 1
+2 more
billyf
says

Because I am new to Wordpress… Do I have to create a plugin for the Post Formats (e.g. video, image, quote, status etc)? I am using a Framework for my new theme and I don’t know if I have to create a plugin for these Post Formats or not. Thanks :)
Post formats are integral components of WordPress. You just need to enable them in your theme’s functions.php file : http://codex.wordpress.org/Function_Reference/add_theme_support
181 posts
  • Exclusive Author
  • 3 Years of Membership
  • Author Level 5
  • Collector Level 2
+2 more
HellasDesign
says

Post formats are integral components of WordPress. You just need to enable them in your theme’s functions.php file : http://codex.wordpress.org/Function_Reference/add_theme_support

Thank you very much billyf :)

56 posts
  • Author Level 5
  • Collector Level 2
  • 5 Years of Membership
  • Exclusive Author
+1 more
ThemeManiac
says

Hi all. Are there any new Requirements for WP theme main files structure? I want to upgrade the theme but I get the respond: Same issue, you have not included the main WP file. I uploaded Main files + separate WP theme. tnx br

56 posts
  • Author Level 5
  • Collector Level 2
  • 5 Years of Membership
  • Exclusive Author
+1 more
ThemeManiac
says

Forget it. It’s OK:)

350 posts Gambit
  • 6 Years of Membership
  • Affiliate Level 3
  • Author Level 7
  • Collector Level 4
+6 more
bfintal
says

@Envato Staff and co-authors.

I’m currently trying to separate stuff in my theme framework into plugins in order to conform to the phase 2 requirements. Since my next theme will clearly not make it in before November. I’m still pondering on what stuff SHOULD and SHOULD NOT be separated into plugins.

So far, my thoughts are that if the user switches to another theme, all their content should still be intact.. even though they won’t be styled at all.

Basically, everything that generates content will be moved to plugins (no styling included):
  • CPTs with their custom fields and templates
  • custom taxonomies
  • shortcodes
  • widgets
All else will remain in the theme:
  • captcha on forms
  • pagebuilder (although this should be transferrable to the normal editor)
  • tgm plugin activator
  • theme customizer
  • theme options
  • sidebar generator
  • everything else…

One thing that I’m not sure though. Since page custom fields generate content, then technically they should be moved into a plugin. But so far I’m leaning towards simply retaining those in the theme. What do you guys think?

@Envato staff, we really need specifics on this. We are currently in the dark

417 posts
  • Author Level 4
  • Beta Tester
  • Collector Level 2
  • Trendsetter
+3 more
CodeScribe
says

@Envato Staff and co-authors.

I’m currently trying to separate stuff in my theme framework into plugins in order to conform to the phase 2 requirements. Since my next theme will clearly not make it in before November. I’m still pondering on what stuff SHOULD and SHOULD NOT be separated into plugins.

So far, my thoughts are that if the user switches to another theme, all their content should still be intact.. even though they won’t be styled at all.

Basically, everything that generates content will be moved to plugins (no styling included):
  • CPTs with their custom fields and templates
  • custom taxonomies
  • shortcodes
  • widgets
All else will remain in the theme:
  • captcha on forms
  • pagebuilder (although this should be transferrable to the normal editor)
  • tgm plugin activator
  • theme customizer
  • theme options
  • sidebar generator
  • everything else…

One thing that I’m not sure though. Since page custom fields generate content, then technically they should be moved into a plugin. But so far I’m leaning towards simply retaining those in the theme. What do you guys think?

@Envato staff, we really need specifics on this. We are currently in the dark

Acutally, styling for all plugins should resides inside plugins only ? Am i right ? Please correct me:)

199 posts ThemePrince
  • Weekly Top Seller
  • Elite Author
  • Exclusive Author
  • 6 Years of Membership
+3 more
ThemePrince
says

I think we should think of it like a normal plugin. There must be a general styling included in the plugin, so if you use it in any other theme, it should look good.

AND in your theme’s stylesheet you can add some extra stylings to make plugin’s layout more compatible with your current theme’s design.

350 posts Gambit
  • 6 Years of Membership
  • Affiliate Level 3
  • Author Level 7
  • Collector Level 4
+6 more
bfintal
says

I think we should think of it like a normal plugin. There must be a general styling included in the plugin, so if you use it in any other theme, it should look good. AND in your theme’s stylesheet you can add some extra stylings to make plugin’s layout more compatible with your current theme’s design.

Oh that’s what I meant, a super general styling. But nothing fancy at all

by
by
by
by
by
by