AttributeError on loading every doc

ERPNext
1

I’m facing server erron onload of every doctypes
“AttributeError: module ‘frappe.email.doctype.email_account.email_account’ has no attribute ‘get_automatic_email_link’”
any idea for resolving?

This was happened after the update!

1 Like
2

Also having the same issue… Below is the complete traceback

    Traceback (most recent call last):
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/app.py", line 62, in application
    response = frappe.api.handle()
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/api.py", line 56, in handle
    return frappe.handler.handle()
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/handler.py", line 22, in handle
    data = execute_cmd(cmd)
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/handler.py", line 50, in execute_cmd
    raise e
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/handler.py", line 47, in execute_cmd
    method = get_attr(cmd)
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/handler.py", line 205, in get_attr
    method = frappe.get_attr(cmd)
  File "/opt/erpnext/frappe-bench/apps/frappe/frappe/__init__.py", line 1046, in get_attr
    return getattr(get_module(modulename), methodname)
AttributeError: module 'frappe.email.doctype.email_account.email_account' has no attribute 'get_automatic_email_link'
3

whats ur version?

4

Erpnext v12.7.1

Frappe v12.5.1

Started after update, I have tried all other bench commands including migrate, update —reset update patch etc, to no avail. What did you end up doing?

1 Like
5

Add this code:
@frappe.whitelist()
def get_automatic_email_link():
return frappe.db.get_value(“Email Account”, {“enable_incoming”: 1, “enable_automatic_linking”: 1}, “email_id”)
at the end of “frappe/email/doctype/email_account/email_account.py”

This commit remove the above code whithout changing the javascript code
https://github.com/frappe/frappe/commit/39850513ed2fa9859111db4fd6a0bb8e42a8d34a

1 Like
6

ERPNext: v12.11.1 (version-12)
Frappe Framework: v12.9.0 (version-12)

Getting same error, do we know if fix will be pushed to to 12.x ?