Bug category view: Item urls not using current category

Hi, I am on FC1806 and discovered a bug with category association of items. It must be a bug because it worked differently before.

This is a category link: www.muenstermann.com/en/overview ... ation.html

If you click on "Impregnating unit for refractory bricks" you will see that the heading changes from "Selected interesting projects and news" (secondary category of the item and used for the category view) to "Current and interesting refractory projects" (primary category). This should not happen and it worked differently before. "Selected interesting projects and news" should stay.

One of the consequences for example is that if the language is switched the correct corresponding view is not shown and an "invalid" item path is created and all the "correct" module settings for the link are lost. This is a big problem because Google puts all this links in the index.

Rooney

Hello

firstly,

please check if this category which is secondary category to this item is excluded from being used in item links

-- the above is configurable in advanced route plugin

if the above is not the case,
then you may send me a PM giving me super admin access

I'll send you an a PM. I have a test page running with FC 2.1.2 r1798 beta, but it shows the same behaviour accept that language switching is working. Funny...

Rooney

Hi, Have you had time to look into this?
Regards, Rooney

PS: Merry Christmas

Hello

i looked at it but was interrupted before i had time to finish looking into it,

-- the problem is not current category, which is correct in the URL,

-- it is related to header configuration / bug (i did not finish looking into it, will do)


But made a rather important improvement for item URL creation in r1826:


Improved usage of DEFAULT menu item per CONTENT TYPE
(yes we can have default menu item per content type)

-- Added option not to use this menu item by default, this corrects problematic Content Type configuration, that always requires a Default menu item for every Content type, thus causing confusion to the user that is NOT aware of this behavior !!

e.g. if you set a non-FLEXIcontent menu item as Default Menu item for a content type, then your items URLs not have an appropriate menu item will start using:

/component/flexicontent/

ggppdk wrote: -- it is related to header configuration / bug (i did not finish looking into it, will do)

Thanks for the information!
Do you know which version introduced the bug? The current behaviour is kind of inconvinient...
Rooney