Improvements to the bean administration page [#1184498]

Visit the block overview/management page at /admin/content/blocks

Click the edit link next to one of the beans to edit it.

Edit it and hit save.

You end up viewing the bean, which breaks the workflow as you then need to navigate back to the block overview/management page at /admin/content/blocks to continue editing your Blocks. I think you should use ?destination to ensure that after editing the bean, you end up on the bean overview page. Just like with normal node editing that is done from /admin/content

Comment	File	Size	Author
#2	1184498-bean-admin-improvments.patch	3.08 KB	mrfelton
#2

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

mrfelton CreditAttribution: mrfelton commented 10 June 2011 at 09:11

Component:

Code

» User interface

Comment #2

mrfelton CreditAttribution: mrfelton commented 18 June 2011 at 12:11

Title:	After editing a bean, you should be taken back to the content/bean page rather than to the bean	» Improvements to the bean administration page
Status:	Active	» Needs review

File	Size
1184498-bean-admin-improvments.patch	3.08 KB

The attached patch adds a couple of nice improvements to the block administration page, making it a little more inline with the content management page. It:

1) Ensures that after editing a bean, you get taken back to the bean admin page
2) Ensures that after deleting a bean, you get taken back to the bean admin page
3) Adds sorting capability to the table
4) Adds paging ability to the page (shows 50 items per page, as per node.module)
5) Add a 'Add block' local task (possibly negates the need for #1170204: Improve process of creating new Beans.

Comment #3

indytechcook CreditAttribution: indytechcook commented 18 June 2011 at 18:45

Status:

Needs review

» Reviewed & tested by the community

I like it. Commit it :) We can use the table select (http://api.drupal.org/api/drupal/developer--topics--forms_api_reference....) element later if we want to add bulk actions or something.

Comment #4

mrfelton CreditAttribution: mrfelton commented 18 June 2011 at 19:06

Status:

Reviewed & tested by the community

» Closed (fixed)

Yes, I looked at using tableselect but just wanted to keep the changes minimal at this point, whilst delivering enough improvements to make the system a lot more usable. I've committed this in http://drupalcode.org/project/bean.git/commitdiff/b2bc09a?hp=153a868f754... and may create follow up issue to further enhance it with the likes of tableselect.