Hi Himasha, Denuwanthi
Thanks for the reply.
I could fix it as Himasha mentioned, I guess, the helper js first looks for
the resource in our extension and if it is not there it goes to the default
location. The mistake that I made was, in the first place I edited the
navigaion.js's content to poi
Hi Senduran,
Did you add your edited navigation.css under your asset extension? What you
can do is, under your new extension(ex: myAsset) which will be located in
store/extensions/assets/myAsset , add your edited navigation.css under
myAsset/themes/store/css and then under myAsset/themes/store/hel
Hi,
You can create a 'helper' folder inside your extension, and create a
'navigation.js' helper there.
Inside that helper, you can specify the parent navigation.js as mentioned
below. Then, use, 'o.css.push('navigation.css'), to put your customized css.
var name;
var hps = require('/themes/store
Hi all,
I am currently using the Enterprise store’s extension model to customize a
particular rxt type in the store. Here I have a scenario to override a
default css (/themes/store/css/navigation.css) within my extensions. I
found that the navigation.css is return as a resource from the
navigation