this is a brilliant module for CMS sites that are built around 'heavy' taxonomies.

It would be even better if , at the top of the 'assign catagories' tab we could have the Filter selection thing from the (administer/content/) 'list' tab. This would help editing alot!

great module,
thanks
JohnG

CommentFileSizeAuthor
#4 taxonomy_multi_edit_1.module5.41 KBalobamor
#3 taxonomy_multi_edit.patch7.84 KBalobamor

Comments

moshe weitzman’s picture

moshe weitzman commented

depends on http://drupal.org/node/17416

moshe weitzman’s picture

moshe weitzman commented

this might be possible in current HEAD. hope someone looks at it and contributes a patch.

alobamor’s picture

alobamor commented
Version: 4.6.x-1.x-dev » master
StatusFileSize
new taxonomy_multi_edit.patch7.84 KB

Hi,

I've made the patch for this feature. It work ok, for me.

This patch also includes the changes to enable paging and the migration to version 4.7

Regards

alobamor’s picture

alobamor commented
StatusFileSize
new taxonomy_multi_edit_1.module5.41 KB

By the way, here is the full file. There are so many changes that I thought to attach the full file, just in case.

neurojavi’s picture

neurojavi commented
Version: master » 5.x-1.0
Priority: Normal » Critical

I think the patch provided here is for 4.7. Am I right?

I think that filters are a critical feature in nearly all drupal sites. Without the filters its very difficult to use the module in a site with 100's or 1000's of nodes. It would be very useful to filter by content type, but a more advanced filtering (by asigned taxonomy terms) would be very useful too. This would augment a lot the usability of this module.

Is there any chance for this feature to be included in the 5.x version?

Many thanks for this great module!

Javi.-

dman’s picture

dman commented
Status: Active » Closed (won't fix)

The tab 'assign categories' is awkward due to its lack of filtering, however it's pretty tricky to work in.
This patch is too old to work with, sorry.

We CAN use the filtering provided by core to do bulk operations at admin/content/node - so try that.
For more hardcore requirements, look at http://drupal.org/project/views_bulk_operations

So I'll retire this issue.