Otherwise, the layouts and styles will be inherited from the parent theme. If the clone theme has layouts or styles, they will be used. The layouts and styles folders of a theme won’t be merged.If a file appears in both themes, the file from the clone theme will be preferred.Files exclusive to the clone theme will be taken into account.Files missing in the clone theme will be taken from the parent theme.The css, media, and templates folders will be merged for the clone theme and the parent theme in runtime:.The rest of the data is automatically taken from the theme specified in manifest.json as parent_theme: Starting with CS-Cart 4.4.1, a cloned theme only includes the manifest.json file, logos, and the default style. Click the gear button in the top right corner.You can do it right in the Administration panel: The easiest way to do it is by cloning your current active theme. If you need to change the look of the store, don’t modify the default Responsive theme. This can become a hassle, especially if some pieces of the default code were removed or replaced. But if you applied some modifications directly to core files, you’d have to revert them too, just to be sure. Normally, the first suggestion is to disable other add-ons to make sure that the problem isn’t caused by them.
Let’s assume that you have a modified core file, and a third-party add-on doesn’t work properly, although it should work on your version of CS-Cart. Things can get problematic even without an upgrade. It may result in a bug, which you’d be able to fix only by reverting the changes in the core file. Some other file gets changed, and that change affects your modification.The core file gets overwritten and you lose your changes.If you decide to upgrade a store with a modified core file to a new version of CS-Cart/Multi-Vendor, here’s what might happen during the upgrade: Reverting the changes may get just as complicated as making them. You can also lose your changes or have them cause a bug after an upgrade. Short answer: Changing core files can result in issues with add-on compatibility.
0 kommentar(er)
