New “Compatible With” Feature Added For ThemeForest

ThemeForest has a new feature we hope you will like. We’ve added a new field to the upload page that will now allow you to select certain compatible services in relation to your upload type.

Read more…

So, compatible doesn’t mean it provides custom design for the plugin/services? Just, compatible? Or if it is built based on that platform?

kailoon said
So, compatible doesn’t mean it provides custom design for the plugin/services? Just, compatible? Or if it is built based on that platform?

It’s kind of a mixture of both here’s some more information. Within our current situation if an author submits a theme for a band or artist it would normally go under something like WordPress > Entertainment > ... But lets say the theme author decides to integrate social aspects using BuddyPress. Right now the BuddyPress option would take precedence and the file would go under WordPress > BuddyPress. This type of categorization lacks the extra descriptive information gained with our descriptive child categories. Additionally, it limits the theme to only being classified as a “BuddyPress” theme.

Where as under the new method, an author could submit that same theme into the proper category of WordPress > Entertainment > XXX and then attribute it with BuddyPress. But he/she could also integrate other services like WooCommerce for sales. So now you could have a WordPress theme that’s categorized based on description, and then using the Compatible With attribute, it could be sort of tagged with both BuddyPress and WooCommerce.

Another nice thing about this new method is the way in which our items are displayed. If a WordPress theme with both BuddyPress and WooCommerce functionality was submitted before, the author would have to choose one of the three categories to place their theme in. Now it could technically be displayed in all three.

So to answer your question, compatible with should be used when a theme has been built and designed to not only work with the compatible addons selected. But these platforms should also be well integrated and styled to match the rest of the theme. Nothing is changing here. Pretty much if you’re submitting a theme that has one of these compatible with attributes selected, its going to fall under the same reviewing guidelines as it would had it been submitted straight into Wordpress > BuddyPress.

Just saying something like “tested BuddyPress with this theme and it works” is not sufficient.

I like this idea, thanks for adding this. I just don’t get why Bootstrap is there but maybe I don’t know something

Nice addition. Could you add more options for CMS like jomsocial, ecwid, redshop and other common components?

thanks.

MarkBrodhuber said
It’s kind of a mixture of both here’s some more information. Within our current situation if an author submits a theme for a band or artist it would normally go under something like WordPress > Entertainment > ... But lets say the theme author decides to integrate social aspects using BuddyPress. Right now the BuddyPress option would take precedence and the file would go under WordPress > BuddyPress. This type of categorization lacks the extra descriptive information gained with our descriptive child categories. Additionally, it limits the theme to only being classified as a “BuddyPress” theme.

Where as under the new method, an author could submit that same theme into the proper category of WordPress > Entertainment > XXX and then attribute it with BuddyPress. But he/she could also integrate other services like WooCommerce for sales. So now you could have a WordPress theme that’s categorized based on description, and then using the Compatible With attribute, it could be sort of tagged with both BuddyPress and WooCommerce.

Another nice thing about this new method is the way in which our items are displayed. If a WordPress theme with both BuddyPress and WooCommerce functionality was submitted before, the author would have to choose one of the three categories to place their theme in. Now it could technically be displayed in all three.

Thank you. This is exactly what I suggested last year when you moved my themes into the new “BuddyPress” category. It’s a “category” that makes no sense. The exact example I gave was, what happens when you support 2 major plugins. I’m glad we made it to a proper solution.

You need to also look at browser versions. Firefox 2? Really? Current version is 12 yet max we can submit is 4?

-Scott

Quick suggestion for expanding the list, bbPress.

arrowthemes said
Nice addition. Could you add more options for CMS like jomsocial, ecwid, redshop and other common components? thanks.

These are all on their way in due time

So for those of us currently categorized in the now defunct BuddyPress area, how do we get our theme moved to a real category? Just selecting the BP options in the “Compatible With” section they’ll appear in the BP section. I was hoping to get moved back to the category I previously had my themes listed under based on it’s design/style.

The reason I always hated being in a BP category was buyers often asked, “Does this work without BP?”, which makes me think I’m surely missing sales to people who don’t realize it’s still a WP theme. I know I wouldn’t check the BP theme section if I just wanted a regular WP theme.

Now that we’ve fixed this who do I email to get moved back to a category?