I am going to use NOP while I'd have some customization and bug fixes on it, what would be the best approach to keep upgrading to newer NOP versions while also keeping my own customization? I found this thread. Do you any other idea?
By Vincent Driessen https://nvie.com/posts/a-successful-git-branching-model/
NOP commerce Instructions:
Production branch: master Development branch: develop Feature and issue branches: Should start with "feature" or "issue". It should be followed by issue ID (according to our Github issue list) and some friendly name (example, "multistore"). Finally, it should look like "feature-34-multistore" or "issue-35-paypal-redirection-bug" Release branches: Should start with "release". It should be followed by version number (example, "3.00"). Finally, it should look like "release-3.00"
create a custom folder in each of the projects name it starting with a z so it will appear last "zCustom" write all your code in these folders u can also add your own dependency register file for your services and and data since most of the classes are partial u can use any class with in the project
part for the views u can place all files in the custom folders
name your controllers starting with a z as well "zCustomer" so the view will be placed last on the list
when upgrading clone the new project and drag and drop your custom folders and views (5 minutes)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.