Question: What Should I do with every Update

What Should I do with every Update

This month there are a lot of updates, every time after download I start to make some changes then another update come then start again, so why just give us the only file and tell us the loc

K

karim

Asked
This month there are a lot of updates, every time after download I start to make some changes then another update come then start again, so why just give us the only file and tell us the location to put it in the location
  • MS

    Mian Saleem

    Answered
    That's not possible as we can't manage to list all the modified files for each update. Thank you
  • WC

    Willy CN

    Answered
    There are some of instructions for update that i dont quite understand.

    8. Please import the files files/db_updates/version one by one starting from the next version you are updating from using phpmyadmin after selecting your database. Please import files/db_updates/POS files too, if you have purchased SMA with POS.

    Will my database become empty again ?
  • K

    karim

    Answered
    It will be very difficult for everyone to use the system, It must be any solution to save our old work with the new update
  • K

    karim

    Answered
    **[saleem](/u/saleem)** It will be very difficult for everyone to use the system, It must be any solution to save our old work with the new update
  • MS

    Mian Saleem

    Answered
    I can understand but as there is no plugin architecture and the changes done directly to the code files. It's not possible for us to list the changed files with each update.
  • MS

    Mian Saleem

    Answered
    **[mibou_kyosiro](/u/mibou_kyosiro)** Please post new question.
  • K

    karim

    Answered
    **[saleem](/u/saleem)** How can I work like this, If this I can't work because every short time we have an update, so when I will be stable?
  • HS

    Harpreet Singh

    Answered
    I think there is one solution to at least preserve front-end changes (JS/CSS/HTML).

    I am using header.php and footer.php to do all the frontend changes (using JavaScript).

    I suggest you to include an empty custom.css and custom.js files in footer of admin section. And custom-pos.css and custom-pos.js in POS module. By default, these files should be empty in "default" theme and I can make any changes that I want to frontend using my custom theme and updating any changes using these files only.

    Any better idea?
  • HS

    Harpreet Singh

    Answered
    **[klar07](/u/klar07)** How about using a private Git repo (multiple branches?) for file comparison?

    I am facing the same problem and I think Git could help.

    Please share your views.
  • MS

    Mian Saleem

    Answered
    **[hs](/u/hs)** There is option to have completely different theme so adding the few assets files won't help. For assets and views, you can add new theme. The main issue is controllers, models and libraries as there is no alternate to avoid overwrite there. You are right about `git` as it's would be very helpful to those need to know the files modified. But it need to be private repository only.
  • Login to Reply