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.

Control Panel CSS format not being recognized

May 09, 2011 4:35pm

Subscribe [3]
  • #1 / May 09, 2011 4:35pm

    tedhutchins

    9 posts

    Hello,

    I have just installed ExpressionEngine 2.1.3 on a clients site.

    Everything went well, except when I log in there is no formatting to the control panel. If moved the CP_theme out of the themes folder and placed it in the systems folder as suggested by the user guide, I get the following error message.

    “An Error Was Encountered, Unable to load the requested file: _shared/menu/item_parent.php”
    When I try to login.

    I also get:

    “An Error Was Encountered, Unable to load the requested file: account/login.php”

    Any suggestions? Thank you.

  • #2 / May 10, 2011 4:35am

    John Henry Donovan

    12339 posts

    tedhutchins,

    Welcome to the forums 😊

    I believe moving the folder method was for EE1.x only. Can you move it back please.

    Can you then add the following to your config.php file please

    $config['theme_folder_path'] = '/home/domain/public_html/themes/';
    $config['theme_folder_url'] = 'http://www.domain.com/themes/';

    Make sure its your full server path

  • #3 / May 10, 2011 11:32am

    tedhutchins

    9 posts

    Thanks John,

    But, I am still not getting any CSS formatting in the login page, or the control panel.

    I moved the cp_themes back to the themes folder and I added:

    $config[‘theme_folder_path’] = ‘/magma/users/u62/ocl/public_html/themes/’;
    $config[‘theme_folder_url’] = ‘http://www.ocl.ca/themes/’;

    To the top of expressionengine/system/config/config.php

    Also, I noticed in the General Config (control panel) that the path and URL were already being recognized before I made the changes to the config.php.

    Thanks

  • #4 / May 11, 2011 2:10pm

    Kevin Smith

    4784 posts

    Also, I noticed in the General Config (control panel) that the path and URL were already being recognized before I made the changes to the config.php.

    Thanks

    Hi tedhutchins,

    That’s because those values are also stored in the database. However, any values you have in config.php always take precedence, so that’s why we typically suggest it for troubleshooting. Folks migrating sites between a dev server and a live server also tend to prefer using config.php since it’s independent of the DB which is much harder to sync between environments.

    With regards to your issue, is this behavior consistent across several different browsers? Firefox, Safari, Chrome, Internet Explorer, etc…

    Double-check your theme_folder_path config variable for me if you would. Nine times out of ten, that’s the culprit when CP styles aren’t loading.

    Kevin

  • #5 / May 11, 2011 3:14pm

    tedhutchins

    9 posts

    Hi Kevin

    The theme_folder_path config checked out OK.

    I’ve tried Firefox, Safari and Chrome on a Mac and a PC and I am getting the same results as before for all 3.

    I tried Opera on a Mac and PC and it worked, the formatting appears to be OK.

    I tried Explorer on a PC and it worked, the formatting appears to be OK.

    If it’s possible I would prefer to do my development in Firefox. Is there a fix?

    Thanks, Ted

  • #6 / May 12, 2011 2:00pm

    Kevin Smith

    4784 posts

    Well this definitely isn’t expected behavior, so we’ll get you fixed up, no worries there.

    Have you tried clearing all caches at CP Home > Tools > Data > Clear Cached Data?

    Let’s also make sure we’re entering the correct server path. Add this to a new file called path.php, place it in your /themes directory, and pull it up in your browser:

    <?php
    $path = getcwd();
    echo $path.'/';
    ?>

    Now take what’s displayed and use that as your theme folder path. Was it the path you were already using?

    Kevin

  • #7 / May 12, 2011 2:38pm

    tedhutchins

    9 posts

    Hi Kevin,

    Thanks, unfortunately because of a few other issues, I decided to go back to EE1.7. Everything is working as expected so far.

    Cheers, Ted

  • #8 / May 12, 2011 7:22pm

    Sue Crocker

    26054 posts

    Hi, Ted.

    Sorry you had to go back to EE 1.7, but let us know if we can assist further.

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

ExpressionEngine News!

#eecms, #events, #releases