The collection view at taxonomy/term needs to work for all vocabularies

same issue

Thanks for reporting.

The issue appears when editing a taxonomy term. And this looks like a breadcrumb issue...

I'm attaching a screenshot !

I have the same issue and additional the problem, that taxonomy menu doesn't generate menu links. Does this issue stops taxonomy menu from working?

M. Schwarzenberg

This bug is related to the #1677268: Other taxonomies than collection has no links issue, cause when drupal try to collects local tasks it check for term accessibility and since any terms is accessible, except those from collections and categories, it fails.

Fixing the above issue should fix this one too.

my test results: it seems this error message it's somehow related with Commerce Kickstart (Lite) Product UI modules.
disabling these modules, make the error history.
any ideas about what could generate such error?
imho it's something related with the features inside modules.

source of this issue : #1677268-4: Other taxonomies than collection has no links
should we mark this as duplicate?

Same issue.

@bojanz: It seems that you know how to fix that :) !

Tagging

is my issue same as here's ? I created a new vocab and terms added, but visiting those terms will show 404 ERROR

EDIT:

editing those term will show error
"Notice: Undefined index: href in menu_local_tasks() (line 2048 of /home/victori2/public_html/dev/includes/menu.inc)."

This depends on #1717236: Cleanup the styling of the Collection view header which won't be ready in time for today's beta, so I'm tagging it as an RC blocker.
Also changing status, since we don't have any code yet.

Basically, the plan is this:
1) Fix the theming in #1717236: Cleanup the styling of the Collection view header
2) Patch the relationship handler to determine the vocabulary from the term in the url
3) Remove vocabulary limitations from the view itself. This way taxonomy/term starts to work for all terms, as it should.

any updates on this? is just so annoying seeing error 404 every time clicked the terms..

I got the same error with Taxonomy Menu as well. Menus don't generate. Looks like the collection view overriding my taxonomy term pages here /taxonomy/term/% is blocking this.

Notice: Undefined index: href in menu_local_tasks() (line 2048 of /mysite/includes/menu.inc).

I am having this same issues as well.
Is any work being done on this?

This is a major blocker for me. Please help?

As bojanz said :

I'm tagging it as an RC blocker.

That means that we'll fix it before the next release ! Feel free to help on that !

here is a gerrit commit that Removes vocabulary validation from Contextual filter validator for the "Collection Taxonomy term" views
https://code.drupalcommerce.org/#/c/414/

I have applied this commit but it does not solve the problem.

After many several trials i have found the "culprits" of this behaviour.
Fresh installation (without new commit):
In contextual filter: Content: Has taxonomy term ID (with depth)
1) On Specify validation criteria add vocabulary(s) you want to setup with Taxonomy Menu
and want show on term pages or unset "collection" to anable all.
2) Unset "Transform dashes in URL to spaces in term name filter values "

Now , Taxonomy Menu, Collections pages and Terms pages works well.

In a old installation (with commit) i had to make the same changes to obtain the same result. (Maybe "Transform dashes in URL to spaces in term name filter values" can influence the Taxonomy Menu module?)

Hope this help

#20 solution works fine.

thx senzaesclusiva.

blueblot

#20: great, that fixed all Taxonomy related bugs I had! Thanks a lot!

Patch from #19 rewritten & should work. You just need to clear your cache to make it work.

#20 confirmed works.

Jonathan is working on major changes to this view (make it work for all node taxonomies, but not product taxonomies, make it use Search API so that facets are possible, add a custom relationship handler so that it joins to the proper vocabulary based on the term in the url).

Marking this as 2.0 release blocker

We decided to remove the taxonomy/term/% view that we created and use a product display view instead.
Here's a big change that does that => https://code.drupalcommerce.org/#/c/487/

Hi,

I am having major problems with this in the new Kickstart distribution.

I am not using the Taxonomy Menu systems, but kept it on anyway.

I have 2 separate instances of the exact same site I have been working on, so that I ca A/B test some stuff.

I have a taxonomy setup called discounts, with a term called 'free this month'.

On one instance of this site this field is part of the product variation, on the other it is on the content type created by the product (still not 100% as to what the difference is and when to use each but never mind!)

Anyway, in the instance where the taxonomy field is on the content type, the term links no problem to a taxonomy list page and shows a list of all products tagged with this.

However, on the version where the field is within the variation this does not work. I get 'There is currently no content classified with this term.'

This is not true....I know there are products with this term.

I am guessing that this has something to do with view, on the forums people have mentioned this view ' collection taxonomy terms' .... this view doesn't exist in Kickstart 2.0.

I disabled the kickstart taxonomy and taxonomy menu modules on both site instance, this had no effect on either, still works ok on one and not at all on the other.

So...

I can only guess my issue has nothing to with the taxonomy menu but something to do with the way the taxonomy term page is building the view??

On one the field being part of the node is ok, but if the field is part of the variation it is not???

The problem is, if I use the field as part of the node, it breaks a whole heap of other stuff, for example I cant get the search api to create a block to filter by free products and also I cannot get the pricing rule to bring the field into scope to apply the discount (both of which I can achieve if the field is part of the variation!!!)

Very very very frustrating....and very little help here on the drupal commerce forums....I have had several issues with kickstart 2.0 (which is by and large an epic distribution!) but so many small bugs and very little support! :(

I can't remember why I didn't use the built in discount system in Kickstart but I think it was because I couldnot discount 100% as it is done using a different calculation.

Anyone???

PLEASE!! :(

Thanks in advance.