package building/customizing/upgrading
Permalink 1 user found helpful
Sometimes it's needed to customize blocks, single pages and controllers from packages, but it seems like copying stuff from a package folder to the webroot doesn't work fine. This is the way to go if we want to prevent changes we made to be overridden by upgrading to a new package version.
how to build packages that work with customized stuff, which is copied from the package folder to the webroot folder like this can be done with concrete5s core files?
thx core team
how to build packages that work with customized stuff, which is copied from the package folder to the webroot folder like this can be done with concrete5s core files?
thx core team
Items in your local directory should override those in a package's directory. I know a couple places where this isn't the case, but those are bugs. Some will be fixed in 5.4.1 - some we probably haven't identified but we'd love to know about.
Themes installed as a package are NOT overwritten by copying to the /themes folder.
Please make this happen. Thanks!
Please make this happen. Thanks!
+1
That answers my question :-( I'd also love to see this.
Hey Andrew,
will there be any changes regarding this issue in one of the next version?
Greets
Ron
will there be any changes regarding this issue in one of the next version?
Greets
Ron
I'm looking for best practices regarding customizing packages. Is it now the case that to customize a package the entire directory should be copied to a theme folder and files customized from there?
Say I only need to customize the packages css file. Would I just copy that file?
Say I only need to customize the packages css file. Would I just copy that file?
