Justin Tadlock 9:50 pm on November 11, 2014

How do we solve the theme options problem?

Users love options, right? That’s the reason we add them as theme authors. While I think there’s a lot to be said about themes with no options that make sound design decisions, I won’t get too much into that right now. Rather, this post is about solving the major issue we’ve had for years as theme reviewers and theme authors trying to get their themes on the repository.

Up until a week ago, we allowed theme authors to create theme options in one of three ways — Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., or with custom options pages using the Theme Mods API. We’ve since narrowed that down to only allowing use of the Theme Customizer (strongly recommended) and Settings API. This was a pretty great move, but it doesn’t really solve 99% of the issues with theme options. Most everyone has already been using those things.

Realistically, the problem has come down to education. There are resources out there available for using these things. However, those tutorials are often written by programmers who aren’t great teachers or writers who are not so good at programming.

One of the things I’ve always hoped the TRT would become is more of an educational team. I firmly believe that if we didn’t have to spend so much time dealing with theme options, we could spend more time on educating in other areas of the dev/design.

I’m writing this post to open a dialogue for everyone on how best to approach this problem.

Issues

The issues I’m laying out here are based on my own personal observations and some things that I’ve heard from other reviewers. As an admin, I’m tasked with doing final reviews on themes before they go live. These issues are often missed by the first reviewers. This is not to lay blame on them. Frankly, it’s a tough job reviewing theme options, especially when no two theme options pages are even coded remotely the same.

Sanitizing, validating, escaping

By far, this is the number one set of problems we run into. What I’m seeing:

Themes don’t do any of these things.
Themes do one thing but not the other (e.g., sanitizing input but not escaping output).
Themes use the wrong functions (e.g., esc_attr() to escape a URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org).

Options saved by default

This has become less of a problem recently, but I still see it on occasion. Themes should be using sane defaults rather than saving default options to the database.

Frameworks, libraries, etc.

There are a number of theme options libraries available for theme authors. These are some awesome tools. However, what’s happening is that theme authors are using these things as a crutch and not learning how the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WordPress APIs actually work.

This creates a problem because it can be hard to explain how to correct an issue if a theme author doesn’t have the basic foundation that they need to work with theme options. This effectively eliminates a great moment to educate theme authors because we’re not on the same page.

Fixing the issues

I’m writing this post because I believe this to be the biggest hangup with themes today. It’s the hardest part of the review process. It’s also one of the most critical because theme options means potential security issues.

I’d honestly love it if all themes would just use the customizer. That’d solve a ton of problems. However, it would be too limiting to theme authors who are doing some awesome stuff. I wouldn’t want to punish good devs by requiring the use of the customizer just so we can fix everyone else’s problems.

My initial proposal is that we build educational tools/tutorials for handling theme options. These need to be written more clearly than developer resources because many theme authors don’t come from a development background.

Another thing we should be doing is strongly pushing theme authors to utilize the theme customizer.

What are your thoughts? What do you think will benefit both theme reviewers and authors? How can we better educate people on these common issues?

KalenJohnson 10:01 pm on November 11, 2014

So the issue you’ve found is that the references / tutorials out there are too technical for more of a designer / front end HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. / CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. developer?

I think a few “Build your first WordPress theme for the theme repository” tutorials would be good, perhaps focusing solely on the Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., then perhaps an “advanced” one that covers some of the basics of the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. But yes I can definitely see how some more not-so-developer focused references could be beneficial.
- Justin Tadlock 5:56 pm on November 12, 2014
  
  Yep, that’s what I’m thinking. Some friendlier docs that are not dry technical writing would be helpful.
Ryan Hellyer 10:01 pm on November 11, 2014

I’m not sure the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. helps much here, as you can easily do stuff wrong in that too.
- Emil Uzelac 10:20 pm on November 11, 2014
  
  It’s not really weather or not we can do wrong or right in CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., it’s about focusing on the future and make it easier for authors to integrate. Education is the key here and moving forward with Customizer just makes sense to me.
  
  Recommending Customizer will unify Theme Options and that will create less issues for both authors and reviewers.
  
  Just take Underscores for an example, ever since this theme was created we have increased the code quality in directory and elsewhere.
  
  Some good examples of Customizer can follow the same path, heck we can even have them on https://github.com/wptrt too 😉
  
  And as you all know this already exist: https://github.com/Automattic/_s/blob/master/inc/customizer.php so it’s just matter of having more docs and extending the basics.
- Justin Tadlock 10:36 pm on November 11, 2014
  
  You can definitely do things wrong there. I will say that I’ve seen more “correct” implementations of the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. than the Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. I’m sure that will change as more people use it.
  
  There are a few ways it helps though:
  
  1) Theme Check automatically checks that a sanitize callback is at least used with the customizer options. This is a big help right off the bat for theme authors who forgot or didn’t know about it. Of course, it may not be the correct callback function, but it’s a start.
  
  2) It helps theme reviewers because we’re all on the same page rather than dealing with massively different types of theme settings pages. We all have that same starting point, which I think is a good thing.
  
  3) It automatically handles a lot of form elements right off the bat that.
  
  I’d even go as far as recommending using the theme customizer + theme mods (default). That makes things even more uniform.
Devin Price 11:25 pm on November 11, 2014

I agree that this is the most difficult part of theme reviews and I second the strong recommendation for using the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. for front-end styles and options.

It’s lovely doing theme reviews that were based off of _s. So many potential pitfalls are avoided by using a strong base. We could do something like that for the customizer, perhaps in an example _s child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/.. We could have an example option for each input type (input, textarea, select, radio, upload, etc.) with proper default sanitization and solid documentation for how to validate, sanitize and output these mods as well.
- Maria Antonietta Perna 12:07 pm on November 12, 2014
  
  As a budding WordPress theme developer (so far I’ve been customizing themes and helping out on the forums) I give my full thumbs up to Justin Tadlock’s observations and to Devin’s practical suggestion on how to tackle this aspect of theme development.
  
  I so hope this example _s child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/. with the proper use of the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. + documentation will be made available to all those who like me are moving their steps into WP theme development and are willing to do it in the best way possible.
  
  Thanks to all of you 🙂
- Ian Stewart 4:11 pm on November 12, 2014
  
  Probably better off as a fork of _s since we don’t want to encourage anyone child-theming _s. We could also maybe ship _s with a more robust sample customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. if the team could see themselves using it. Worth a pull request at least.
  - Devin Price 4:55 pm on November 12, 2014
    
    I was thinking a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/. because it could basically just be one file (“customizer.php”), which people could just drag into any theme they chose. I wouldn’t really want to bloat up the lean/mean _s theme- but if some commented out boilerplate code leads to some better practices it might be worth doing.
usability.idealist 12:20 pm on November 12, 2014

IMHO, some kind of actual default option framework built straight into the WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., would help a lot.

The CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. way is a nice sketch, but the current implementation is pretty much broken. As soon as you got more than a handfull of settings, some kind of default fallback with type detection (switch case) would come in MUCH MORE handy.

A ghandful = 6- 10 settings. More than a handfull = 30 – 50 settings. Or like in CC2, approx 110+ settings. Also, the missing default settings are quite a PITA (yes, the Customizer got default settings; sadly, after INITIAL theme activation, they DO NOT WORK – at least not for any kind of colors and images; both in WP 4.0 and 4.1-nightly).

I’m currently writing something like that for Custom Community 2 (https://github.com/Themekraft/Custom-Community), which basically consists of an associative array, with several parts, including the whole theme_mods corner, and their related sanitation callbacks. It’s going to be hooked into the theme activation / switch callbacks, fetch all the listed options and theme mods, compare them, and add the default value if none are given.

cu, w0lf.
- Frank Klein 4:27 pm on November 12, 2014
  
  The `get_theme_mod()` function accepts a default value as second parameter, so I don’t see what kind of issue you are talking about.
  - usability.idealist 5:15 pm on November 12, 2014
    
    NOT talking about get_theme_mod, but about the settings in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. Those have a default value, but are not used – as described before. An RL example would be: https://github.com/Themekraft/Custom-Community/blob/v2.0.10/includes/admin/customizer-options.class.php#L534
    
    cu, w0lf.
- Justin Tadlock 5:42 pm on November 12, 2014
  
  I never have any problems with the defaults working in the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. If you’ve found a bug in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WP, you should open a TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket. That’s outside our jurisdiction.
tareiking 2:33 pm on November 12, 2014

It would be nice to have an official version repo extending Paul Underwood’s work on custom controls for the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. : https://github.com/paulund/wordpress-theme-customizer-custom-controls to illustrate that developers may not even need theme option frameworks.

Copy and pasting accepted examples of controls would likely help developer adoption of the customizer and bump the code standards of themes.
- Justin Tadlock 5:43 pm on November 12, 2014
  
  I actually think that’s a great idea. We should have many examples, even a repository, for customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. controls.
Jason Lemahieu (MadtownLems) 3:31 pm on November 12, 2014

I’m curious what overlap, if any, you see between this issue and something like: https://core.trac.wordpress.org/ticket/18285

I think that something like Devin’s https://wordpress.org/plugins/options-framework/ or https://github.com/farinspace/wpalchemy existing as part of coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. would address not just this, but many other issues.

Why are we having thousands of developers duplicate the effort (and each one doing it over and over again) of generating the htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. form controls, validation, sanitizing, etc of options in the first place?
- Frank Klein 4:22 pm on November 12, 2014
  
  The CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. comes with a ton of controls out of the box. If you think that there is a component that is needed, you can always create a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. ticket for it. Also the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. provided by the Customizer is great, and there’s no need for an additional framework.
  
  The big problem with frameworks is that most developers never even bother to read and understand the code in them. That’s also the major reason why I repeatedly see developers using option framework APIs the wrong way.
  
  Now using a framework and not understanding it is about as bad as using a Core API and not understanding it. In both cases the developer has no idea what’s going on and how to securely integrate options into his theme.
  
  But in the case of the framework, the added risk of the framework itself having security issues is much higher than if you just use the APIs provided by Core.
  - usability.idealist 6:47 pm on November 12, 2014
    
    The major biggie with the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. currently is the documentation. It’s all over the place and lots of important parts are not documented at all. Been cringing lately a lot ..
    
    So, to stop complaining: Hope to get some spare this weekend to seriously tackle those issues. Eg. I’d like to do a full analyzation of a “hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. firing during a typical customizer request”, document all used methods, and prepare better examples. Maybe dig into the sanitation part, write up or at least prepare a few tutorials, and maybe get also a possible solution for a general customization function (theme-specific), ie. good practices-style, similar to Paulund’s articles. Of corpse, thats not all manageable during a weekend – more like a plan for future (ab)use of my spare time 😉
    
    Ok, basically the same as Justin proposed in his intial post, but with focus on the Customizer (bit off-topic, but still) 😉
    
    cu, w0lf.
    - Justin Tadlock 7:18 pm on November 12, 2014
      
      I’d love to see what you come up with. The more resources for using the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., the better!
- Justin Tadlock 5:54 pm on November 12, 2014
  
  As a theme developer, Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. stuff doesn’t really matter to me much. I dropped it like a bad habit when the theme customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. came along. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. WP has an extremely robust system with the Customizer API coupled with the Theme Mods API. The primary reason for its existence is so that theme authors would have a much easier time building theme settings. It’s a complete framework in and of itself.
  
  As a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developer, I’m excited about potential changes such as that ticket for the Settings API. Anything that core can do to improve this area is always great. Even though they can improve that, I don’t think there’s much overlap. Like Frank said, it’s not so much the tools that’s the problem. It’s the incorrect usage of the tools is where we’re seeing issues.
  - Zane Matthew 7:05 pm on November 12, 2014
    
    Are you suggesting that the Theme CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. should fully replace the settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.? and possibly the settings API should become deprecated?
    
    IMO, I think both are important and do have their distinctions.
    - Justin Tadlock 7:16 pm on November 12, 2014
      
      Not at all. The Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. is a useful tool, particularly for pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party developers. There’d be no need for it to be deprecated. That’s not even a consideration. Not to mention, it can also be used in conjunction with the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. (it’s one of three ways to save settings).
      
      I actually think requiring the use of the customizer would spur some innovation, and we’d all be better for it on the whole. However, as I wrote in the post, the last thing I want to do is create more guidelines for limiting good developers. One of the reasons I originally got involved with TRT was to help stop those sorts of guidelines.
kevinhaig 3:51 pm on November 14, 2014

I’ve been following this thread, and decided to dig into the theme customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. I am developing a theme with a significant number of options, and it is just not reasonable to expect users to re-enter the options if they decide to go to a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/..

So far I really like the customizer, but I see this as a major stumbling blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for themes with a lot of options. Is this being looked at?

Another question, why can we use “option” to save the theme option as a separate item in the options database when it is required to have all theme options in an array?
- Justin Tadlock 7:47 pm on November 15, 2014
  
  I’ve been following this thread, and decided to dig into the theme customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. I am developing a theme with a significant number of options, and it is just not reasonable to expect users to re-enter the options if they decide to go to a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/..
  
  It makes a lot of sense for many, many themes. I have many users who use the same parent theme but switch child themes depending on the season, holiday, etc. Their settings (e.g., colors, menus, etc.) need to be tied to the active theme so that they don’t have to change things up whenever they switch back to their normal child theme.
  
  There’s also tons of other really neat stuff you can do on a per-theme basis with Theme Mods (what you’re talking about). It’s awesome once you learn the ins-and-outs of it.
  
  Of course, if you need to go another route, simply don’t use the Customizer + Theme Mods. Use the Customizer + Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. method of saving settings. That’s one of three different default methods. Actually, there’s a fourth method where you can pass a custom type of option and run all the callbacks yourself.
  
  You could even use a combo of methods if it made sense.
  
  So far I really like the customizer, but I see this as a major stumbling blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for themes with a lot of options. Is this being looked at?
  
  There’s nothing to look at. It’s just a lack of education on the subject. That’s what this post is about. You’ve provided a good example of one of the problems, which is that theme authors don’t have the knowledge they need to effectively make use of the customizer. That’s one of the issues I hope for us to figure out.
  
  The various option methods and their pros and cons should definitely be on the list. I’d love to get more feedback from you on things you see as stumbling blocks. It’ll help guide me on figuring out what all we need to touch on.
  
  Another question, why can we use “option” to save the theme option as a separate item in the options database when it is required to have all theme options in an array?
  
  The reason for this is because, in the past, we had theme authors who would have 30, 40, 50, and even 100 inividual options. It’s generally frowned upon to save all those options, cluttering up the wp_options table in the database, especially when a single array works just as well.
  
  There may be some, but I’m not aware of any, advantages to using multiple options over a single array of options. If there’s a case to be made for the options in your theme, we’ll certainly look it over and take it into account. Feel free to CC me on the ticket.
  
  Personally, I’m not against more than one option. Most TRT members probably aren’t either. Our main goal is to avoid many options with no direct benefit over using an array, which is the default way that WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handles things with the Settings API and Theme Mods API.
  - kevinhaig 6:17 am on November 16, 2014
    
    Thanks for the response Justin. I will definitely supply feedback. I have around 200 options on the theme and I’d love to make customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. work. I think if I can make that many options work better using the customizer, then it’s a pretty good example of the system. I know the amount of options sounds ridiculously high, but it gives the user great flexibility.
    
    The theme I submitted about 10 days ago is called Panache. I spent the last couple of days switching to customizer to have a look at it, and I think it is pretty incredible, I am quite excited about it.
    
    I have encountered a few issues but they may be from my lack of understanding of some of the controls. I will list them anyway.
    
    The image controller should allow selection of images from the media library, and not just loading images from the computer.
    
    With the amount of options I have, I load the settings and controls through an array, kept outside the customize register function. I tried using type:option and then an array for storage, but it will not accept that, which led me to the theme_mods type. I am not sure how to use the settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to save the options within customizer, the existing documentation only refers to option and theme_mod types.
    
    It would also be nice to set up a sanitize_callback function that could pass multiple variables such as sanitization type, value, and default.
    - kevinhaig 10:15 pm on November 16, 2014
      
      Just an update…I did manage to get the settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. to work.
Ulrich 7:02 pm on November 18, 2014

@greenshady – I am not sure if you are aware the Theme Docs. https://developer.wordpress.org/themes/

It would be great if we could work with them to improve these pages and not create our own pages which compete with them.
https://developer.wordpress.org/themes/advanced-topics/theme-options/
https://developer.wordpress.org/themes/advanced-topics/theme-customizer/
- Samuel Sidler 7:05 pm on November 18, 2014
  
  The front page of that is only visible to certain users, but those other pages are definitely visible. We have a handbook chat weekly at 21:00 UTC on Tuesdays. Anyone that’s interested in helping improve the theme developer handbook so we can ship it, we’d love for you to join!
- Justin Tadlock 8:13 pm on November 18, 2014
  
  I really think that the developer handbook should be something different than what I have in mind. Maybe I’m wrong, but I believe the goal with it is to be more of a reference. That is certainly great, but references aren’t always the best learning tools. They’re good in addition to the main learning resource.
  
  The big problem I see is that both the Make Themes site and the Theme Dev Handbook are poorly designed for the more free-form type of resource that I’d like to provide, which is really more my style.
  - Tammie 6:17 pm on November 19, 2014
    
    We are changing the format of the handbook though @greenshady and I see we can now have the opportunity to add in free-form resources. Even maybe beyond a collection of resource links.

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

How do we solve the theme options problem?

Issues

Sanitizing, validating, escaping

Options saved by default

Frameworks, libraries, etc.

Fixing the issues

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Issues

Sanitizing, validating, escaping

Options saved by default

Frameworks, libraries, etc.

Fixing the issues

Share this: