What about the Famous WordPress Frameworks like GANTRY and WARP , Will it be acceptable? with the new requirements?
I hope to clarify
Just a concern : I have not been following this thread. I hope/expect at the end of all this discussion, once all the terms are finalized, Envato would notify all the authors of the new terms with an official mail.
I am fairly comfortable with most of the guidelines and the point of view of many authors (who are in disagreement) here. Although, as you have consulted the top authors, I hope you have also consulted the top buyers (of each profile) as well, as they are the ones which truly govern the direction of this market place.
I notice that in the Theme Check plugin when running tests, it displays that it is REQUIRED for add_theme_page() to be used in place of add_menu_page().
I’m not understanding why add_menu_page() is REQUIRED instead of RECOMMENDED? Since add_menu_page() adds a top level menu item, whereas add_theme_page() only adds a submenu under the Appearance top level menu. Why does the Theme Check plugin have this as REQUIRED instead of RECOMMENDED, when WordPress Codex has that method available for wp developers to use? And the various themes sold on ThemeForest have top level menu items to group and organize their option page menus for usability to the end user.
If my admin options I’m making for a theme have many option pages, I want to group my theme pages together under my own top level menu item. It will be very impractical to use add_theme_page(), which would make all my option pages submenus under the Appearance menu. I want to group my option pages together so the end user doesn’t get confused when using my theme and navigating the backend which is a usability issue! That is why i would use add_menu_page().
Anyone else seeing this error thrown in the Theme Check plugin? And think that it should be RECOMMENDED instead of REQUIRED?
I emailed Enavto Support regarding this issue with the Theme Check plugin, and will post if I receive an answer.thanks!
If wordpress does not let developers use top level menu then where is the scalability of wordpress we all talking about? why all of my pages should go under appearance?Do you know why theme check gives this error? because its configured for wordpress.com where you cant do much. they have this and that rules for their own…
I wrote the author about that Theme Check plugin, and he basically said that ThemeForest rules don’t apply to his plugin, and at themes being submitted to wordpress.org. http://wordpress.org/support/topic/regarding-why-add_menu_page-is-required-instead-of-recommenced
So why do we have to use the Theme Check plugin, that enforces different errors and rules for the way to submit themes on wordpress.org. When we are submitting themes to ThemeForest?
ThemeForest should make their own Theme Check plugin for checking themes submitted on ThemeForest. Instead of being forced to use the Theme Check plugin that was built to submit themes on Wordpress.org.
This makes no sense for his Theme Check plugin to say that add_menu_page() be replaced with add_theme_page(). Even on the wordpress codex examples for creating options pages, it uses add_menu_page() :http://codex.wordpress.org/Creating_Options_Pages
What do you all of you think of that Theme Check plugin?
No one is against a stricter code moderation. It’s kindly great to improve our skill level.
The problem concerns just to plugins that will come with themes and have no relation to another themes. What is a sense to convert an options framework or shortcodes into a plugin? Bad code will never works properly regardless of whether a plugin is or embedded code and it will not reflects on the compatibility with other plugins. It’s a damn pain for customers/authors only. In any case, a buyer does not find any paid/free solution to get the functionality like in our demo if our “Custom Portfolio Plugin” (just for example) is crooked and I’m not even talking about the styles of specific design. “Lego” themes are not for TF in my opinion.
Envato has to clarify the goal of “WordPress Features 8-11” because “to play nice with other 3rd party plugins” isn’t a valid reason being already addressed by all other rules.
If the plan is to follow wp.org then why custom post types were not event mentioned ? Instead, we just have a list of allowed/forbidden shortcodes without a clear rationale (at least to me) which tells nothing about the purpose of this whole move.
“Themes should be just themes not complete websites / too much features bloat” ? If so, elaborate first, make rules after: what would qualify as an appropriate feature for a TF theme ? Because, again, if we wanna follow wp.org, then answer would something like blog / post / basic page styling and maybe some custom widgets ?
So what’s the story ? do you think TF products have too much features or you don’t care about it as long as those features are moved into a plugin ?
we’ll be recommending, but not enforcing
i think its pretty clear.
I think the best solution for both authors and customers is creating a new “Wordpress Skins” category. I know some of the customers have php,html etc. knowledge and they want to play with the codes for their clients needs. Maybe they just want a theme which has a good design and well coded for customization. So they can look for this kind of themes in this category and they can pay lower prices for this simple Wordpress skins.
But Most of the customers looking for an easy to use complete web solutions. They don’t want to upload tons of plugin. They don’t want to play with the codes or change their theme every month. They just want a website like the demo… So I think Themeforest is the best marketplace for them for just this reason…
I have to tell that I’m strict agains this rulle “No inline styles are allowed any where.”.
I don’t get it why? Top saled themes like avada or enfold and ofcourse much more themes have inline styles. So for example I want to let user choose custom color of some text. There is no way ho to do it diferently.
So my question is. Is this rulle absolute stric, so I really will be not able to use any inline style for my theme?
Thank you very much for your help.