ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Upgrade to 1.6, missing button for creating Custom Weblog Fields, Member Group, etc.

June 22, 2007 11:42am

Subscribe [4]
  • #1 / Jun 22, 2007 11:42am

    hothousegraphix

    851 posts

    I’ve just noticed with my upgrade to 1.6 that I’m missing the button that creates Field Groups, Custom Fields, Member Groups, etc.

    The hot-spot does still exist and if selected I’m sent to the proper place…just no image.

    I’ve attached a screen-shot to hopefully clarify what I’m experiencing.

    Would anybody have a clue as to how to address?

    Thanks

  • #2 / Jun 22, 2007 12:17pm

    hothousegraphix

    851 posts

    In looking at this further it seems the text is present (white on white) but the button BG is not.

    Was this an image in the new default theme, or simply color defined in the CSS?

  • #3 / Jun 22, 2007 12:37pm

    Sue Crocker

    26054 posts

    Here’s the path to my image:

    /themes/cp_themes/default/images/bg_button_a.gif

    Assuming you are using default as your CP theme. Make sure of that.

  • #4 / Jun 22, 2007 12:54pm

    hothousegraphix

    851 posts

    Good Morning Sue,

    Funny, I was just looking at the rendered CP styles, and…the images paths are still reading /cp_themes/31Three/images/tab_inactive.gif rather then default.

    Let me back up a bit. I’ve read a number of threads that indicate config.php (after updating) should now be fairly small, only 25-40 lines long. Mine is quite a bit longer.

    According to the Update Instructions we’re told not to overwrite the config file. I assumed this meant, do not overwrite config.php from my previous install - so this file is the same as it was from my prior version. Was this correct? Could this be what is causing my situation?

    If not, all the new files for the new CP theme are installed and located in themes/cp_themes/default.

    Upon further inspection of my CP the button div I seem to have no BG for has a class of “crumblinksR” which indicates that it should be a background-color of #96C251 (green).

    Is this the old CSS for the 31three theme. I’m getting updated drop-downs and placements so have assumed that it is the new default theme CSS…maybe it is not?

  • #5 / Jun 22, 2007 12:59pm

    Sue Crocker

    26054 posts

    You need to change your default CP template from 31Three to Default. 😊 That should fix things for you.

    I had some weird looking things in my CP until changing to Default. See if that helps.

    The new default theme is based on the 31three theme, but it’s not exactly the same.

  • #6 / Jun 22, 2007 1:07pm

    hothousegraphix

    851 posts

    I am set to default, in fact, I have no other themes installed.

  • #7 / Jun 22, 2007 3:36pm

    hothousegraphix

    851 posts

    Additionally…if I update a template, sometimes the corresponding button in question (under Admin Tab) shows up with the green BG color and red button text.

    It’s appearance seems not to be consistent. I’ve not been able to pick up a pattern - like, for instance, updating a template every other time.

    Any ideas?

  • #8 / Jun 22, 2007 4:29pm

    Derek Jones

    7561 posts

    hothouse can you switch to Classic and then back to Default?  First get a fresh download and replace the cp_themes folder just to be on the safe side.

  • #9 / Jun 22, 2007 4:58pm

    hothousegraphix

    851 posts

    Hey Derek…thanks for jumping in.

    I never installed all the themes with the upgrade. So, as suggested I’ll download again and update my cp_themes folder.

    Sort of on the same note, I asked Sue, but she didn’t really answer my question. When I updated to the new version I followed what I thought the Update Instructions meant when saying “Do NOT” overwrite the path and config files. I assumed this meant, do not overwrite config.php from my previous install - so this file is the same as it was from my prior version. Was this correct?

    I only ask this because I’ve seen in several posts where users are mentioning that their config files are only between 20 and about 50 lines on length. Mine is at about 160 lines.
    Could this be contributing to my situation?

    I’ll update and post me results.

    Again, thanks for helping out.

  • #10 / Jun 22, 2007 5:07pm

    hothousegraphix

    851 posts

    Derek,

    I wanna thank you very much…that process seemed to correct this situation!

    Thanks much.

    Have a wonderful weekend.

  • #11 / Jun 22, 2007 5:10pm

    Derek Jones

    7561 posts

    The theme changes are mentioned in the version notes for 1.6 which is linked at the bottom of the upgrade instructions.

    The new config files are smaller, and that takes place during the update.  Are you saying that you have updated your site to 1.6, ran the update script, successfully, and that your config file is still 100+ lines long?  What is the ‘app_version’ value?  And do you happen to be on Windows?

  • #12 / Jun 22, 2007 5:11pm

    Derek Jones

    7561 posts

    NP, but let’s make sure your update process went smoothly and that the config file is correct before we break out the champagne! 😉

  • #13 / Jun 22, 2007 5:18pm

    hothousegraphix

    851 posts

    Are you saying that you have updated your site to 1.6, ran the update script, successfully, and that your config file is still 100+ lines long?  Yes

    What is the ‘app_version’ value?  I assume you’re referring to the build version -Build:  20070621

    And do you happen to be on Windows?  Also, Yes (XP service pack 2)

  • #14 / Jun 22, 2007 5:33pm

    Derek Jones

    7561 posts

    No, I’m referring to the ‘app_version’ value in the $conf array.

    And for the record, ::sigh::  We have a protection in the update script to not allow one to run it unless the config.php file is writable, and on Windows, PHP rarely seems to get it right.  The only ones that are required now are:

    $conf['app_version'] = "160";
    $conf['license_number'] = "your license number";
    $conf['debug'] = "1";
    $conf['install_lock'] = "1";
    $conf['db_hostname'] = "db_hostname";
    $conf['db_username'] = "db_username";
    $conf['db_password'] = "db_password";
    $conf['db_name'] = "db_name";
    $conf['db_type'] = "mysql";
    $conf['db_prefix'] = "exp";
    $conf['db_conntype'] = "0";
    $conf['system_folder'] = "system";
    $conf['cp_url'] = "http://example.com/system/index.php";
    $conf['doc_url'] = "http://expressionengine.com/docs/";
    $conf['is_system_on'] = "y";
    $conf['allow_extensions'] = "y";
    $conf['multiple_sites_enabled'] = "n";

    Obviously, with your settings instead of these examples.  And please backup your file before modifying it, just in case!

  • #15 / Jun 22, 2007 5:35pm

    Sue Crocker

    26054 posts

    hothousegraphics:

    And do you happen to be on Windows?  Also, Yes (XP service pack 2)

    Derek is referring to whether your site is running on a Windows box, or on a Unix/Linux box, not what you are personally running.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases