In step 2 of the "Sass Fallback Structure", it indicates specific directories that you are allowed to delete. However there are some files that you MUST have in your custompackage/customtheme/scss directory, and those are:
If you have those files in your scss ...
NOTE: In my answer I will describe how to do this for Magento's default package and theme. This should work in the same way for the
RWD package and <SCSS> files. The important part is step 2 and to
notice that there are multiple selectors in which the background color
To change the background color of Magento e-mail templates in ...
It depends on how you reference the image.
If you reference the image in a template file via a call to $this->getSkinUrl('images/sth.jpg'), then the fallback should work as expected.
But if you reference the image in a SCSS file with e.g.
Then there is no other chance than copying the respective image ...
You can edit your transactional emails templates in the backend at:
System -> Transactional Emails
In addition to modifying the content, you have the possibility to change the template style. Either it is to change in content area itself or in the template style area...
Hope that helps.
It can be a little confusing. Here is my attempt at giving you an example of how it can be done.
Create a new theme by creating new folder in:
Magento uses inheritance when loading theme files. So you really don't need to copy all the files from rwd/default to your new theme folder. You only really need to copy the files ...
The path to the Ruby configuration file given in the tutorial seems odd to me.
Shouldn't we put this add_import_path at the custom theme level? i.e.
(Which does not even exist as it's in the scss subfolder)
One other thing: by following the instruction ...
I wouldn't recommend copying over the styling from the Luma theme, providing your theme is set up correctly to use Luma as a parent (it looks like it is) you shouldn't need to make any changes.
It looks correct to me when compared with the Luma theme, can you attach a screenshot of the problem please?
Also you should be aware that it isn't a good idea to ...
It is not a good idea to edit the core magento2 files. You are going to run into horrible maintenance problems when you come to try and upgrade to the next version (which you should always be able to do promptly and without extra fuss).
Fortunately the magento devs have a solution. You have two choices for adding css rules, modules or themes. Modules are ...
I don't think this accepts SCSS files, and even if it did your browser can't render them.
What you need to do (unless you're doing something custom) is to pass it a CSS file, and compile your SCSS into CSS.
you can follow these steps to compile files with Gulp:
1.In magento root directory, create an empty package.json and copy-paste the following code:
"author": "Magento Commerce Inc.",
"description": "Magento node modules dependencies for local
It looks like you installed this module manually. In readme they wrote that
This module is intended to be installed using composer
Maybe you missed some dependency.
Another thing according to text under , do you see generated css file in this location after run deploy command ?
php bin/magento setup:static-content:deploy
command and view files in ...
You should only need to create the files for the styles/modules you intend to overwrite, but I wouldn't throw them all into one file.
They should get compiled by Magento anyways, and having them isolated should make maintaining them a bit easier for you.
If you have created a new theme that uses the blank theme as a parent then all the styling will be coming from LESS files within vendor/magento/theme-frontend-blank.
You will need to search this directory for the element you want to modify. For example searching for .block-static-block will return magento/theme-frontend-blank/Magento_Cms/web/css/source/...
My solution to fix that checkout Problem on a Luma Parent Theme.
#app/design/frontend/[YOUR THEMENAME]/[YOUR THEMEMODEL]/web/css/source/_theme.less
Browsers doesn't support some fonts.And instead of using google links, You just give this a try.
1.Download the font family you want.
2.Create a folder named 'fonts' inside skin/frontend/package/theme/css/
(I used only css to style my site. so I created inside css folder.If it didnt work try creating it under scss folder)
3.Copy the font files which you ...
You can follow the next tutorial of Magento: http://devdocs.magento.com/guides/m1x/ce19-ee114/RWD_dev-guide.html#theme-compass
1.) You must configure a Compass Watchers to generate the css from scss
2.) And add your own Sass Partials for your custom module: http://devdocs.magento.com/guides/m1x/ce19-ee114/RWD_dev-guide.html#customze-theme-sass-partials
This disclaimer is shown because you're trying to edit the default theme (note that you're in a subdirectory of /frontend/**rwd**/default. This theme will be updated when Magento is updated and therefore the file will be reset eventually and your changes will be lost.
To override this style, create your own theme (or copy an existing one like rwd) and ...
There are several Compass-only functions that are contained in the RWD Sass files. If you remove those functions, Sass compilation should work. You will also need to recreate the config.rb files in Sass config files, including the fallback (if you are using it).
A simple way to determine which Compass functions are being used would be to try to compile the ...
This just means they are partials, the underscore lets Sass know that the file is only a partial file and that it should not be generated into a CSS file but only used with the @import directive.
The leading underscore is ignored when you include the files using @import so doing @import "partial" and @import "_partial" generates the same output.
You can ...
That error means you are missing the template file for the category menu. Your theme defines a template for it, but it's not installed.
To find out which template it's looking for, you can try:
grep -E '(catalog/navigation|page/html/topmenu)' app/design/frontend/*/*/layout/*.xml
Look for template="path/to/template.phtml" in the output and try to locate ...
Thank you for pointing this out. I rearranged the steps to make it more clear that the object is not to copy files and delete them but rather to end up with only the partials you want to edit in your custom theme.
If you followed our instrux to create the custompackage/customtheme directories, you'll have to delete the partials then add back the ones you ...