Nivo Slider code in 5.5.1 core files?
Permalink
When I wanted to customize the Nivo Slider add-on in 5.4.x, I used to edit the following files:
1. packages/nivo_slider/blocks/nivo_slider/css/default.css
2. packages/nivo_slider/blocks/nivo_slider/css/nivo-slider.css
3. packages/nivo_slider/blocks/nivo_slider/js/jquery.nivo.slider.js
>>> That was enough.
In 5.5.1, however, the Nivo Slider code is included in the core files, already:
1. concrete/css/ccm.app.css
2. concrete/js/ccm.app.js
>>> Now, I have to edit/override these files, too.
This doesn't make sense to me. I'm just wondering why an add-on code is included in the core files. Isn't this unnecessary?
Can anybody explain this to me?
1. packages/nivo_slider/blocks/nivo_slider/css/default.css
2. packages/nivo_slider/blocks/nivo_slider/css/nivo-slider.css
3. packages/nivo_slider/blocks/nivo_slider/js/jquery.nivo.slider.js
>>> That was enough.
In 5.5.1, however, the Nivo Slider code is included in the core files, already:
1. concrete/css/ccm.app.css
2. concrete/js/ccm.app.js
>>> Now, I have to edit/override these files, too.
This doesn't make sense to me. I'm just wondering why an add-on code is included in the core files. Isn't this unnecessary?
Can anybody explain this to me?
It might make sense for us to customize the naming of our nivo slider functions so that they don't conflict.