New answers tagged get-option
Yes, get_site_option() is for data about the whole network. The irritation comes from a mixed vocabulary: what was a site once is a network nowadays, and what was a blog once is now a site in a network. wp_get_sites() for example is from version 3.7, it fetches sites in a network, not all networks in an installation. So a site in wp_get_sites() is not the ...
Could there be something happening in Customizer then? I'm seeing the same thing as the OP here. I can confirm that with about 30 options my Customizer load time dropped from around 3s, to around .5s when switching to get_option over get_theme_mod Calling the methods directly I see a 2ms difference. ...
get_theme_mod is just a wrapper around get_option. In theory because it is another layer of abstraction it will work slower but in practice the difference should not be big enough to be noticed by a human. Actual speed differences can be caused if you have some slow code hooked on the theme_mod hooks.
You can use PHP's stripslashes() command: <?php echo stripslashes( get_option( 'myOption' ) );
Top 50 recent answers are included