What are the advantages and disadvantages of Option Tree over the Customization API?

I’m relatively new to WordPress theme development, and I had to create a theme with options available. I did a Google search to see what are the possibilities, and I read articles about such, and read about frameworks, and I came across Option Tree, which was recommended as a framework to develop with.

What my question is, when I’m developing themes to sell, what are the advantages and disadvantages of Option Tree over the Customization API built into WordPress?

Related posts

Leave a Reply

2 comments

  1. disadvantage using option tree:

    1. Your theme depend on other work as a core
    2. You need to always keep an eye for the plugin update ( which is really not good if you’re going to use it in premium theme )
    3. If you’re going to integrate it in your theme, then when there is update from the plugin you will need to do lot of things to update it in your theme.

    advantage :

    1. Save you the time to create your own theme options

    If you have lots of time I suggest you to create your own theme options which will be better if you’re gonna use it in a premium theme to sell, you’ll have more control over the theme options.

    And if you’re not going to write your own script, I suggest you to use Options Framework Theme which is specially build to include in theme rather than using plugin. The author is keep updating the script itself so its safe to use it, I also use it in my premium theme.

  2. Why one should consider other … options

    Frameworks like “Option Tree” (there’re also several others) shouldn’t be used anymore. The “Theme Customization API” is what you should use now, as it also adds the possibility of live editing a Theme in the Theme Customizer and binding the Theme options to the “Theme Modification API”.

    The “Settings API”, which is the underlying API for Frameworks like “Option Tree”, nowadays is meant to be used with plugins and WP core instead.