Quote:
|
Originally Posted by qualiteam
I've tried this locally and it works for me. I'm attaching a sample module that will "decorate" Crisp White theme with its own "skin" directories. It changes the left sidebar menu template in the backend (so a new "Custom header" title appears above it), plus it makes some sidebar blocks in the storefront yellow (check a category page to see it). I didn't try other "interfaces" (mail and common), but I believe it should be done exactly the same as I did for the "admin interface" (check the MainCrispWhite::getSkins() method). Also, I've found that when you adjust getSkins() method of CrispWhite, X-Cart 5 does not include the new skin directories into the archive with your module files when you create one. That's why instead of placing new skin files into skins/my_custom_theme/... I split these into multiple skins/customer/modules/... directories (check the structure of the attached archive). Does this work for you?
|
In a word... No
Well not yet anyway.
After creating a new custom module as per the example in the download and customising it for our own use / setup, we installed it and enabled it with no issues, but we cannot then get it to actually do anything... This will be our error we're sure, because you found it worked okay. Maybe it's just our mis-understanding of the modified file positions when using this version of the custom module? i.e. Placement of the modified files which it implements is only mentioned in the message (not the sample download data). FWIW We have located modified files in: /skins/admin/modules/dev-name/module-name/... & /skins/customer/modules/dev-name/module-name/... to test things initially before adding them in common and mail, which is correct as we understand it from the last message, but to no avail...