View Single Post
  #4  
Old 11-24-2016, 09:56 PM
 
Triple A Racing Triple A Racing is offline
 

X-Wizard
  
Join Date: Jul 2008
Location: Manchester UK
Posts: 1,028
 

Default Re: Crisp White Skin in 5.3.* - Custom Modifications?

Quote:
Originally Posted by qualiteam
Well, this is possible, but is a bit tricky when you don't know how to do it
We have seen the light... (sic Blues Brothers) It's gone from possible to reality. Thanks!
Quote:
Originally Posted by qualiteam
It will be "4" (see below)
Ha! It's now currently at "4.5" a new kind of blend... See below
Quote:
Originally Posted by qualiteam
I haven't tested the above code, but I think it should work
It does. Perfectly. However, we couldn't see how the getSkins() total deletion from Main.php and then the addition of an extra file only covering the 'customer' area, would process any changes to items located in 'admin', 'common' and 'mail. So brute force over ignorance we added getSkins() back into Main.php but removed the line that refers to 'customer' area. Simply because that is now processed by an additional file in the module directory, exactly as per your previous suggestion on here (our personalised version of it..) and it works perfectly already. The replacement get skins() 'skinny latte' version within Main.php now looks a bit like this:

PHP Code:
public static function getSkins()
    {
        return array(
            \
XLite::ADMIN_INTERFACE    => array('new_directory' LC_DS 'admin'),
            \
XLite::COMMON_INTERFACE   => array('new_directory' LC_DS 'common'),
            \
XLite::MAIL_INTERFACE     => array('new_directory' LC_DS 'mail'),
        );
    } 

In effect, Main.php and the additional file work side by side within the Custom Module. That's fine by us and from the results all of our tests that we have run so far. The sev store current status is:

All changes that we apply to 'admin', 'common', 'customer' (aka the Crisp White skin Module and its visible results that are already applied prior to any changes by ourselves...) and 'mail' are all processed by this single Custom Module, plus all the associated files (copied then customised) located within /skins/new_directory/*

The only challenge that we haven't figured out yet, is applying a logic change to an existing XC Module. Initially, it appears that these MUST still be applied via the XC Custom Skin Module...but we'll work out how to include these in the Custom Module soon... We can apply custom JS and that was only applied by us using the XC Custom Skin Module previously too, so there will be a way to do this.... somewhere.... Back soon
__________________
Dev Store & Live Store XC Business 5.4.1.35
Server; Ubuntu 22.04.2 LTS (HWE 6.2.0.26.26 Kernel)) / Plesk Obsidian
Nginx 1.20.4 / Apache 2.4.52 (Ubuntu Backported) / MariaDB 10.11.4 / PHP 7.4.33
Reply With Quote