Results 1 to 8 of 8
  1. #1
    Join Date
    Aug 2009
    Location
    Greeneville, TN USA
    Posts
    51
    Plugin Contributions
    0

    Default Admin CSS blowout while trying to install COWOA

    As background, I am working to install COWOA (beta 2.7) on a v1.5.5a site. I've had to switch back and forth a couple of times between the new files and my backup (through cpanel). The first couple of switches were fine with no issues.

    However, after a few passes, my admin menu CSS is blown out. I've tried multiple restores, and removed both the admin and includes folders before the last restore. My main store files appear fine.

    FWIW, I had a bookmark that goes to my admin, but doesn't go to the https version (made during pre-cert development). The CSS there works, until I click something and it shifts to https.

    I've also looked at file/folder permissions, and tried the htaccess files. No luck there either.

  2. #2
    Join Date
    Jul 2012
    Posts
    16,444
    Plugin Contributions
    17

    Default Re: Admin CSS blowout

    Do you have a SSL certificate installed to your store?

    What are the contents of your admin/includes/configure.php file?
    Do not post your DB_USERNAME or your DB_PASSWORD, and if your admin directory is presented, obscure it as well.
    Please press the # button in the message box toolbar to wrap in code tags before pasting the contents.
    ZC Installation/Maintenance Support <- Site
    Contribution for contributions welcome...

  3. #3
    Join Date
    Aug 2009
    Location
    Greeneville, TN USA
    Posts
    51
    Plugin Contributions
    0

    Default Re: Admin CSS blowout

    Quote Originally Posted by mc12345678 View Post
    Do you have a SSL certificate installed to your store?

    What are the contents of your admin/includes/configure.php file?
    Do not post your DB_USERNAME or your DB_PASSWORD, and if your admin directory is presented, obscure it as well.
    Please press the # button in the message box toolbar to wrap in code tags before pasting the contents.
    Yes. It has an SSL certificate.

    Code:
    <?php
    /**
     * @package Configuration Settings
     * @copyright Copyright 2003-2016 Zen Cart Development Team
     * @copyright Portions Copyright 2003 osCommerce
     * @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
     * File Built by Zen Cart Installer on Wed Mar 30 2016 10:47:32
     */
    
    
    /*************** NOTE: This file is VERY similar to, but DIFFERENT from the "store" version of configure.php. ***********/
    /***************       The 2 files should be kept separate and not used to overwrite each other.              ***********/
    
    /**
     * Enter the domain for your Admin URL. If you have SSL, enter the correct https address in the HTTP_SERVER setting, instead of just an http address.
     */
    define('HTTP_SERVER', 'https://mywebsite.com');
    /**
     * Note about HTTPS_SERVER:
     * There is no longer an HTTPS_SERVER setting for the Admin. Instead, put your SSL URL in the HTTP_SERVER setting above.
     */
    
    /**
     * Note about DIR_WS_ADMIN
     * The DIR_WS_ADMIN value is now auto-detected.
     * In the rare case where it cannot be detected properly, you can add your own DIR_WS_ADMIN definition below.
     */
    
    /**
     * Enter the domain for your storefront URL.
     * Enter a separate SSL URL in HTTPS_CATALOG_SERVER if your store supports SSL.
     */
    define('HTTP_CATALOG_SERVER', 'http://mywebsite.com');
    define('HTTPS_CATALOG_SERVER', 'https://mywebsite.com');
    
    /**
     * Do you use SSL for your customers login/checkout on the storefront? If so, enter 'true'. Else 'false'.
     */
    define('ENABLE_SSL_CATALOG', 'true');
    
    /**
     * These DIR_WS_xxxx values refer to the name of any subdirectory in which your store is located.
     * These values get added to the HTTP_CATALOG_SERVER and HTTPS_CATALOG_SERVER values to form the complete URLs to your storefront.
     * They should always start and end with a slash ... ie: '/' or '/foldername/'
     */
    define('DIR_WS_CATALOG', '/');
    define('DIR_WS_HTTPS_CATALOG', '/');
    
    /**
     * This is the complete physical path to your store's files.  eg: /var/www/vhost/accountname/public_html/store/
     * Should have a closing / on it.
     */
    define('DIR_FS_CATALOG', '/home1/XXXXXX/public_html/');
    
    /**
     * NOTE about DIR_FS_ADMIN
     * The value for DIR_FS_ADMIN is now auto-detected.
     * In the very rare case where there is a need to override the autodetection, simply add your own definition for it below.
     */
    
    /**
     * The following settings define your database connection.
     * These must be the SAME as you're using in your non-admin copy of configure.php
     */
    define('DB_TYPE', 'mysql'); // always 'mysql'
    define('DB_PREFIX', 'BS'); // prefix for database table names -- preferred to be left empty
    define('DB_CHARSET', 'utf8'); // 'utf8' or 'latin1' are most common
    define('DB_SERVER', 'localhost');  // address of your db server
    define('DB_SERVER_USERNAME', 'XXXXX_DDDD');
    define('DB_SERVER_PASSWORD', '[email protected]@###');
    define('DB_DATABASE', 'XXX_FFF');
    
    /**
     * This is an advanced setting to determine whether you want to cache SQL queries.
     * Options are 'none' (which is the default) and 'file' and 'database'.
     */
    define('SQL_CACHE_METHOD', 'none');
    
    /**
     * Reserved for future use
     */
    define('SESSION_STORAGE', 'reserved for future use');
    
    /**
     * Advanced use only:
     * The following are OPTIONAL, and should NOT be set unless you intend to change their normal use. Most sites will leave these untouched.
     * To use them, uncomment AND add a proper defined value to them.
     */
    // define('DIR_FS_SQL_CACHE' ...
    // define('DIR_FS_DOWNLOAD' ...
    // define('DIR_FS_LOGS' ...
    
    // End Of File

  4. #4
    Join Date
    Aug 2009
    Location
    Greeneville, TN USA
    Posts
    51
    Plugin Contributions
    0

    Default Re: Admin CSS blowout

    Follow-up. When looking at the admin menu in the httpS/broken view, it's looking for an admin/includes/index.css that doesn't exist in the backup. I found and installed a copy, but that didn't help. I've also restored the admin/index.php to make sure it's the correct version.

    FWIW, I've attached screen dumps with the "Sources" tab from Chrome to show the error. I'm looking into the lack of a "CSS" folder showing up on the broken version.

    Click image for larger version. 

Name:	BrokenHTTPS.JPG 
Views:	45 
Size:	22.8 KB 
ID:	16671
    Click image for larger version. 

Name:	WorkingHTTP.JPG 
Views:	33 
Size:	22.2 KB 
ID:	16670

  5. #5
    Join Date
    Jun 2015
    Location
    California
    Posts
    54
    Plugin Contributions
    0

    Default Re: Admin CSS blowout while trying to install COWOA

    I had the same css problems when installing COWOA on 1.5.5 on both the front end and the the admin, but in order to fix it I just had to make sure I properly merged the new CSS with my old code.

    I think my problem was old code from my modified 1.3.9 install that didn't play well with the new COWOA css. Is your 1.5.5 a clean install or an upgrade from an earlier version?

  6. #6
    Join Date
    Aug 2009
    Location
    Greeneville, TN USA
    Posts
    51
    Plugin Contributions
    0

    Default Re: Admin CSS blowout while trying to install COWOA

    If I recall correctly, we started with a fresh v1.5.5, but shortly upgraded to v1.5.5a before doing the COWOA testing.

    One interesting wrinkle, it's only doing it on Chrome on Win 10. Another station with Chrome on Win 7 doesn't have the issue. I've compared Chrome settings between the stations, and I don't see any significant differences.

  7. #7
    Join Date
    Jun 2015
    Location
    California
    Posts
    54
    Plugin Contributions
    0

    Default Re: Admin CSS blowout while trying to install COWOA

    Quote Originally Posted by bbsbcastle View Post
    If I recall correctly, we started with a fresh v1.5.5, but shortly upgraded to v1.5.5a before doing the COWOA testing.

    One interesting wrinkle, it's only doing it on Chrome on Win 10. Another station with Chrome on Win 7 doesn't have the issue. I've compared Chrome settings between the stations, and I don't see any significant differences.
    That makes it sound like it could be a cache issue? Have you tried clearing the cache?

  8. #8
    Join Date
    Aug 2009
    Location
    Greeneville, TN USA
    Posts
    51
    Plugin Contributions
    0

    Default Re: Admin CSS blowout while trying to install COWOA

    Well duh!

    Of course. Thanks!
    That's why it's always useful to have someone to talk through these things.

 

 

Similar Threads

  1. File Merge Help - Trying to install css/js mod
    By Miff in forum General Questions
    Replies: 0
    Last Post: 30 Nov 2011, 12:36 PM
  2. Replies: 5
    Last Post: 21 Apr 2008, 11:11 AM
  3. Replies: 23
    Last Post: 18 Mar 2007, 10:28 PM
  4. Fresh install layout blowout
    By quag2000 in forum Installing on a Linux/Unix Server
    Replies: 2
    Last Post: 29 Jun 2006, 04:07 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
disjunctive-egg
Zen-Cart, Internet Selling Services, Klamath Falls, OR