Error after Update to version 8.0.14

@Ujjawal

do bench update and try again

i tried Bench Update as Well.
Still the problem persists.
What could be wrong?

@Ujjawal

have you deleted Employee record . May be that’s why it’s not accessible.
If not try

bench clear-cache
bench clear-website-cache
bench build

For every Document it is throwing this error when using google chrome browser in console it displays error as follows:

Cannot set property ‘get_query’ of undefined
in file form.min.js

I’ll try these commands hope it solves.

It hasnt solved the problem.
In Console it shows error in file
erpnext.min.js(729:1) and form.min.js(4182:28)

Any update with the solution?

Thanks. I did not notice that before your suggestion.

Regards
Mijan

Hi!
Any update for the error.
I am still facing it.

@Ujjawal

Please take update one more time. Maybe it resolved.
Also try above commands.

@Ujjawal

do bench doctor and paste results here, as the will give a better clue as to what the issues are.
You can also do bench run-tests to highlight any issues, but it does take a while to run.

If all else fails and this is simply a dev/test installation might as well do a bench reinstall it will save you time & grief :slight_smile:

bench reinstall:
i guess it will wipe my database.

bench doctor gives the following output:

user@User-ThinkPad-T400:~/frappe-rk$ bench doctor
-----Checking scheduler status-----
Workers online: 3
-----None Jobs-----

Moreover the error right now i am facing is on Mozilla Firefox and not in chromium Browser.
I tried clearing cache and wiping the history too.
The problem is quite strange.

Yes it will, but as I mentioned, might be easier. If you have not done any changes to the install

Did clearing the cache & rebuild help?

Did everything but still facing it.
It works on one browser and not in another.
So problem is not with bench rebuild.
I’ll paste the console error to let you know exactly about the error:

@Ujjawal you need to upgrade your browser so that it supports ES6 syntax. Though, we are releasing a new build system that will avoid this later today.

Alright.

Thanks for the support.

Is the error solved?

Has the error solved
I am also facing the same issue