ThemeShaper Forums » Thematic


Theme-options.php only showing in admin dashboard

(9 posts)
  • Started 11 years ago by LizaValero
  • Latest reply from LizaValero
  • This topic is not resolved
  1. I have a wpmu (still running 2.9.2) and follow Ian's instructions for adding a theme-options.php file to a thematic power blog child theme. Everything went great, except that now the only dashboard the theme options shows up in is my admin one. All my site owners/user admin's dashboards do not have it.
    Help please!

    Posted 11 years ago #
  2. Hmm, the plot thickens. I've just started playing with mu ( networks via WP 3.0).

    I have a theme_options.php as well as some additional theme options added directly through functions.php into a separate submenu. (ugly, i know, don't ask...)

    Anyhow, my child-theme options added via theme_options.php show up for users, but not the options added via functions.php.

    So, we seem to have the same, but different problems. I'll start comparing the mechanism used to add these options to find what is missing from the function calls in functions.php, i bet therein lies the answer for both of us.

    As a clue, and a question, the default thematic option menu does not show in the child-theme for users either, do you have this same issue?

    Posted 11 years ago #
  3. eww, ok, my issue is a little too complex/convoluted, lets just try to see why my theme_options works for my users and yours doesn't.

    I did the same as you an used Ian's sample as a base without much modification.

    Do you have this same set of function calls at the start of the file?

    add_action( 'admin_init', 'theme_options_init' );
    add_action( 'admin_menu', 'theme_options_add_page' );
     * Init plugin options to white list options
    function theme_options_init(){
    	register_setting( 'shabadoo_options', 'shabadoo_theme_options', 'theme_options_validate' );
     * Load the menu page
    function theme_options_add_page() {
    	add_theme_page( __( 'Shabadoo Options' ), __( 'Shabadoo Options' ), 'edit_theme_options', 'theme_options', 'theme_options_do_page' );

    Did you include it in functions.php the same way?

    //register theme options
    require_once ( get_stylesheet_directory() . '/includes/theme-options.php'  );
    Posted 11 years ago #
  4. Thanks for the answers and its good to know I am not alone, even though we have opposite problems.
    I have the exact same function calls at the top of theme-options.php.

    In the functions.php though, mine is slightly different.

    '//register theme options
    require_once ( get_stylesheet_directory() . '/theme-options.php' );'

    Where you have

    '//register theme options
    require_once ( get_stylesheet_directory() . '/includes/theme-options.php' );'

    But I guess you just have it in a different place than I do

    I went over every step again, and I still got the same result,
    my admin account, the new theme options page is there, all other user/admin accounts, it is not.

    I just check the default Thematic options page and it does not show up for my users either. I had never noticed it before because they do not have any use for that page, but sure enough, it is not there either

    Posted 11 years ago #
  5. Now that I think about it, and I could be wrong, but I'm fairly certain that the sample options was coded specific to wp 3.0. I seem to remember trying to use it on a 2.9 site and it didn't play nice.

    also, are you running MU via wildcard? i.e.

    I'm having several issues where a thematic child-theme just doesn't seem to know where to look for things due to MU's directory structure. I don't have these issues with non-child themes. Things like (get_stylesheet_directory) don't seem to always produce the desired result.

    Have you tried adding even a portion of the theme options directly into functions.php just to see if anything shows?

    Posted 11 years ago #
  6. I haven't, but I will. I didn't see anything about 3.0 but I will go look again. I need to go ahead to do the update but I am afraid of the havoc. I
    I have had a few issues here and ther with the child themes, but I thought they were mostly styling in IE, I haven't thought about it much further, but you may be right.
    I check out your website tied to your avatar and by coincidence it seems that you may have some knowledge I might need. My wpmu is for a real estate company and we are doing our own in house IDX. But the guy who put together the RETS part for me is going back to school and so I have to decide what next. I saw you have a co in NC, what MLSs do you work with now?

    Posted 11 years ago #
  7. Oh and I forgot to answer about the domain structure. My wpmu does use the wildcard.

    Posted 11 years ago #
  8. Liza, you're welcome to call me anytime to chat about RETS. Its a deep ocean in its own right. I only have one client in NC, up in Highlands, a small market, but the moving parts are the same as I assume your using a Marketlinx IDX/RETS.

    As for our theme_options issue, there's a way to quickly help determine if we're on the right path.

    Cristian Antohe, over at Cozmolabs, does some great thematic child-theme work. I know that most of his free themes, Commune and Early Morning, in specific, have child-theme option menus that he coded directly into the child-theme's functions.php. You can just cut and paste his theme-options code from one of his functions.php into your functions-php and see if it shows up. He does a great job of documenting his code, so it should be relatively apparent what parts to cut out. As long as you cut out the right code you won't break your site, (hell, if it does break just remove what you did :P), the options just won't work as your theme wasn't designed for them, but it will help us get to the bottom of this.

    Posted 11 years ago #
  9. OK, I am familiar with some of the cosmo labs child-themes. I will do as you suggested and let you know what happens
    Thanks os much for the help

    Posted 11 years ago #

RSS feed for this topic

Topic Closed

This topic has been closed to new replies.