Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"'NoneType' object is not iterable" on "Expand all" in BOM Tree #2474

Closed
strixaluco opened this issue Dec 19, 2016 · 4 comments
Closed

"'NoneType' object is not iterable" on "Expand all" in BOM Tree #2474

strixaluco opened this issue Dec 19, 2016 · 4 comments
Labels

Comments

@strixaluco
Copy link
Contributor

strixaluco commented Dec 19, 2016

Steps to reproduce:

  1. go to https://beta.erpnext.com/desk#Tree%2FBOM;
  2. choose any BOM;
  3. click on Expand all button

Expected result:
BOM tree expands

Actual result:

Traceback (most recent call last):
  File "/home/frappe/frappe-bench/apps/frappe/frappe/app.py", line 55, in application
    response = frappe.handler.handle()
  File "/home/frappe/frappe-bench/apps/frappe/frappe/handler.py", line 19, in handle
    execute_cmd(cmd)
  File "/home/frappe/frappe-bench/apps/frappe/frappe/handler.py", line 36, in execute_cmd
    ret = frappe.call(method, **frappe.form_dict)
  File "/home/frappe/frappe-bench/apps/frappe/frappe/__init__.py", line 888, in call
    return fn(*args, **newargs)
  File "/home/frappe/frappe-bench/apps/frappe/frappe/desk/treeview.py", line 22, in get_all_nodes
    to_check = [d.value for d in data if d.expandable]
TypeError: 'NoneType' object is not iterable

Environment:
beta.erpnext.com
ERPNext: v7.2.0-beta
Frappe Framework: v7.2.0-beta
Firefox ESR 45.5.1

@rmehta
Copy link
Member

rmehta commented Dec 20, 2016

@strixaluco please raise this in ERPNext Issues (ok for now)

@rmehta rmehta added the bug label Dec 20, 2016
@strixaluco
Copy link
Contributor Author

Sorry, I assumed it's related to Frappe because of traceback (eg. File "/home/frappe/frappe-bench/apps/frappe/frappe/app.py")

@rmehta
Copy link
Member

rmehta commented Dec 20, 2016

No issues. Just easier to track issues on one repo!

@strixaluco
Copy link
Contributor Author

Got it. To be honest, I always thought better to be specific and open issue in corresponding repo.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants