Crisp White Skin in 5.3.* - Custom Modifications?
Thanks to this forum and all the helpful people in it, in our live store, we use a standard XC5 skin, but then modify this in many different ways, via a Custom Module and a very long list of associated modified files. Works very well, it's easy to use (after a steep module creation learning curve...) and it's very upgrade friendly, because you can test the upgrade on the Custom Module in your dev store, prior to running a live store upgrade. It simplifies things too, as no additional Theme Tweaker, Custom CSS /JS or custom_skin changes are needed because the Custom Module completes all the changes itself.
Meanwhile, we are busy deeply investigating Crisp White Skin in our dev store and the best way to re-work that in many areas. This is also, for argument's sake, a Custom Module carrying out lots of changes on a standard XC5 skin. Again, we don't want to use Theme Tweaker, Custom CSS /JS or custom_skin, so in short, can we run a Custom Module on top of an existing Custom Module? i.e. say; Crisp White skin mods module on top of Crisp White skin module? 8O Has anybody tried this? If the answer is '...yes the logic flow works and there won't be an endless loop...' then in the Main.php file that will be required to make this happen, will the Customer Interface line change from a normal: Code:
\XLite::CUSTOMER_INTERFACE => array('*custom_module*' . LC_DS . 'customer'), Code:
\XLite::CUSTOMER_INTERFACE => array('*custom_module*' . LC_DS . 'crisp_white/customer'), If the answer is no.... Then yes we can edit the existing Crisp White skin module related files, but that makes future upgrades a big problem again or we can use Theme Tweaker, Custom CSS /JS or custom_skin but those are our last choices really, but we can't think of any other ways... |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Well, this is possible, but is a bit tricky when you don't know how to do it :-)
Quote:
It will be "4" (see below) :-) Quote:
Yes, you're right. You can't have two theme modules operating at the same time. So, your custom module should extend \XLite\Module\AModule and not \Xlite\Module\AModuleSkin. However, instead of registering your template directories from getSkins() method in your module, the module should hack into the Main class of Crisp White theme. I.e. you should have the standard "Main.php" file without getSkins() method, and another file as follows: PHP Code:
I haven't tested the above code, but I think it should work. |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Hahahaha!
Brilliant! #4 The bit we didn't know / can't see for looking 8O You can see every time :D/ Thanks again and back once we have tested with a report etc |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
Quote:
Quote:
PHP Code:
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 :mrgreen: |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
We'll have a break (...deal with our normal business!!) then return. We'll apply lots of mods to the Custom White Skin view, together with all our non 'customer' area XC5.3.* mods and after some final super-tests, to see if we can break anything, we'll transfer this setup onto our live store. Thanks again @qualiteam for the guidance on this one :wink: |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
With this file, once the system reads the .less file provided by the Custom Module, the public side of the dev store simply looses all the normal view and becomes just a list of links...Remove the customised file, re-deploy and we're back to normal again. We're guessing that it's to do with the logic route involved, as we can modify .less files elsewhere e.g. within /skins/common without any issues or failures like this one. This is a little different, as we applying a change via the Custom Module to a Module that's already applying changes to the default skin :mrgreen: however, it's only this file that has this failure (so far)... The irony is that we can apply the desired change easily by Custom CSS, so that's why we are assuming it's just the logic route that's causing the issue when using the Custom Module? 8O |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
|
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Whilst waiting for some feedback on that previous question, we have a different (unconnected) question now...
Using either a Custom Module or, the XC Custom Skin Module or, Custom CSS, together with the default X-Cart Standard Template, it's possible and easy to limit the 'Maximum' size (width) of the site itself. Most store owners don't want to do this :wink: but some do. It really depends on their own chosen site view and design ideas etc. It only sets a maximum limit, so there's no effect on smaller windows obviously. Using either a modified .css file c/w Module activation or Custom CSS, here's some code which works very well (we have tried it and used it on XC5.2.* and XC5.3.* setups and it works perfectly on both these cores when using the XC standard template): Code:
@media (min-width: 1182px) { Does anybody have good bootstrap CSS experience and... enough exposure to Crisp White Skin now, so as to figure out the correct or alternative way to make this maximum window size limit work? A long reach question to the CWS Dev Team possibly? |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
Quote:
Quote:
Code:
@media (min-width: 1200px) { |
Re: Crisp White Skin in 5.3.* - Custom Modifications?
Quote:
You don't need getSkins() in your module's Main.php because your module is not a "skin" anymore. The only active theme is Crisp White, and it has its own getSkins(). So, from you custom module, you hack into that getSkins() method defined in Crisp White, and add your directories so that it looks like Crisp White registered them. If you want to override admin, common and so on, you add them through that decorated getSkins() method, not from getSkins() defined in your Main.php. Quote:
I'm waiting a reply from the XC5 dev team on this. My guess is that it is because style.less may be the "base" less file that the theme loads first. But I may be wrong. Quote:
Thank you for sharing this! |
All times are GMT -8. The time now is 10:12 AM. |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.