It has bee a while since I have played around with new versions of ERPNext and this window was a surprise:
My question is (and I know this sound sooo newbie) what command do I run to update my system to these newest patches?
I have spent the past 2 years keeping clients locked into whatever version I installed for them and have never seen this window before. Heck, I have not updated a ERPNext system in over 2 years now. So, I guess I just forgot how.
Is there a way to disable this window from poping up?
Hmm… This is going to be a problem. Once I settle a client on a specific point version, they do not change for up to 3 years. So, this message constantly popping up is going to create a ton of hate mail for me.
They are going to view this as the kind of nagging pop-ups they would get from something like a free gmail account or some free app on their phone that conastantly nags them to buy something or upgrade.
I have just started evaluating v11 for my newest clients and it pops up not only for the administrator but for the 3 other users that also logged into the new system.
The fact that it is NOT limited to the Administrator is the most concerning part.
This is also NOT hosted on the erpnext cloud. This is hosted on one of my own VPS server accounts and it is really quite invasive. I cannot provide this to clients with the constant pop-ups when there is a newer version available.
No, I installed ERPNext about a week ago when I was testing installation steps on Ubuntu 18.04 and I didn’t start adding information to the system until today. When I logged in as the Administrator I saw the message and thought it was odd.
After about 30 min I logged in as one of the other users to test the POS Profile I had created for it. That user had the same message pop-up as the Administrator.
After being puzzled by the pop-up in more than the Admin account I proceeded to lo into two additioal user accounts only to have the same message on both additional users.
It was on the last user that I made a screenshot for this thread.
I keep multiple VPS servers in various states of readiness for testing new versions ut this one was the oldest.
Thanks. I am fine with editing at this point. I already lost a potential client this afternoon that I only got setup to test last Wed. I had installed it a few weeks ago and spent a over a week converting data and loading it up via the import tool.
So, it was left on v11.1.4 just because I was afraid to change anything until they finish testing. This issue blew that idea out of the water.
Thankfully the ‘bench build’ command is verbose in it’s execution. I initially left an errant # symbol in the desk.js file when trying to comment out the line. The build command was very good at alerting me to the error so I could go back and fix it.
Evidently you are supposed to use // for comments in desk.js and use # for comments in hooks.py
All appears to have gone well though. I will have to wait and see what happens on the next point update.
Thanks again for jumping in to relieve the pressure.
@brian_pond Thank you as well for that great offer to jump in and assist even while traveling.