It is little weird if no bean type have defined yet but this empty type select appears.

Bean content list (before)

I think we should remove this form and the empty list completely while one bean type is not defined.

Files: 
CommentFileSizeAuthor
#1 admin-content-blocks-after.png8.71 KBDenes.Szabo
#1 remove-filter-form-1503270-1.patch1.26 KBDenes.Szabo
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch remove-filter-form-1503270-1.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
admin-content-blocks-before.png14.31 KBDenes.Szabo

Comments

Denes.Szabo’s picture

Status:Active» Needs review
StatusFileSize
new1.26 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch remove-filter-form-1503270-1.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
new8.71 KB

Attached my patch to solve this problem.
After when this patch applied the page will display like this:

Bean content list page (after)

indytechcook’s picture

Status:Needs review» Fixed

I like the idea but not the implementation. I committed it and changed bean_list to return a render array.

http://drupal.org/commitlog/commit/22232/fca2a75594be221527a76cc8294f565...

Denes.Szabo’s picture

Your empty list handling solution is better than it was, I agree with you. But, you misunderstood my intention with this patch. I meant, no real meaning of a filter form (with an empty type select) or an empty list if there has no bean type defined yet.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.