Category module support

Very interesting question, I too is puzzled. Really nobody uses Localizer together with Category module?

I would advise staying away from the category module until it is more stable. I am not exactly sure what its status is at present, but I remember that the developer was on leave for a while. In this case I would imagine that the difficulty you are having is related to the category module and not the localizer. See if you can achieve your requirements with the core taxonomy module, which will be of benefit to you in the long run.

At begining I also think catagory module is a great one, but now I also stay away from it. I don't like the way all node become a category, since if you have >1000 nodes, it would be really very dofficult to set parent category from a 'very very' long drop-down selection list. Indeed, I find that combining taxonomy context and custom pager modules, we can reach same but more flexible and convenient results.

I'm trying to achieve the same - Category and Localizer modules on one site. Since the core Taxonomy module is replaced with a wrapper module from Category module, changes of the Localizer patch for taxonomy.odule no longer exist.

My first try was to re-inject those lines at appropriate places but it seems that Category module does not use the wrapper module for displaying categories and containers. However, those changes are certainly needed for legacy taxonomy functions and so I'm attaching a patch as a starting point for Category module support.

Category module support is available in Localizer v2.x now. Please test.