mrandyjoe

@otto42 Thank you so much!! I thought there might be something like that for really old themes but I had no idea where to ask for help. I didn’t know about the Slack either but I’ll use that from now on for issues like this. Thanks again!

@t-p I am the author of that theme! That is what this entire conversation has been about. I have pushed an update to MY theme, that I have authored, and it is not changing the listing on the Theme Directory Page.

@t-p It is updated in my style.css though. Here’s a link to it in the wordpress subversion repository where you can see it says 1.2.0: https://themes.svn.ww.wp.xz.cn/aplos/1.2.0/style.css

I’m wondering if even though my commits were taken, because it’s been so long since I’ve updated it, the theme directory has archived it or something and it needs to be “re-activated” before new changes will show up. Does such a system like that even exist though?

I suppose I could clarify things and give an example of what I’m doing. It’s possible I’m not implementing the Customize API in the best way and someone has alternatives (my theme is Aplos btw).

Everything here is contained in functions.php.

First I create my customizer function and add a setting for link colors (I don’t need to create a new section as I’ll just be putting it in the default Colors section that comes in the Appearance menu):

function aplos_customize_register($wp_customize) {
 $wp_customize->add_setting( 'link_color',
         array(
            'default' => '#8F1E0C',
            'type' => 'theme_mod',
         )
      );

Then, in that same function, I add my control for the setting:

$wp_customize->add_control( new WP_Customize_Color_Control(
         $wp_customize,
         'aplos_link_color',
         array(
            'label' => __( 'Link Color', 'aplos' ),
            'section' => 'colors',
            'settings' => 'link_color',
            'priority' => 15,
         )
      ) );

I then create a new function that actually customizes the CSS and prints the desired values in the header based off of what is set by the Customizer:

function aplos_customize_css() {
  ?>
     <style type="text/css">
     a, a:visited { color:<?php echo get_theme_mod('link_color'); ?>; }
     </style>
  <?php
}

I then hook both of those functions into the theme:

add_action('customize_register', 'aplos_customize_register');
add_action( 'wp_head', 'aplos_customize_css');

And that is pretty much all I am doing. So this will print a separate stylesheet in the head of the theme based on what is set in the Appearance menu.

However, as outlined in my original post, I noticed that the first time a user installed my theme, none of the default values were being used. Even in the preview on the official WordPress theme page, none of those values were being set and it looked horrible. So I went ahead and hardcoded in the default values into the main theme stylesheet. Technically this means that styles are printed twice, but it uses what is set by the Customizer because that stylesheet is printed last.

I don’t want this behavior. I’m going to have font subset choices soon and don’t want people loading two separate font files for performance reasons (if the @font-face rule is printed twice). So does anyone know how I can use the Customizer and not have to hard-code my default styles into the main theme stylesheet?

Yes, I just checked the database and those table values are exactly what you said (and as they should be). I did change those in my general settings before moving around files.

I’m pretty sure this has to be an issue with the fact that it’s on a Windows server. My research keeps turning up something about IIS but I really don’t understand it.