Last post 8 hours 44 min ago
Posts last week 80
Average response time last week 29 min
All time posts 45419
All time tickets 7253
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#6475 – Problem with zoo urls

Posted in ‘Pre-sale questions’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 01 December 2017 16:28 UTC
There is a problem with sh404sef and zoo.
I have several zoo items called in various pages accessible from menus (so have different Itemid). Among these zoo items some are also called on the home page (which is a menu item with id 800 of a "hidden" menu that we do not visualize on the frontend) through the zooitempro module. The link to the item is recalled with the zoo route $this->app->route->item($this->_item). The non-sef url generated is index.php?option=com_zoo&Itemid=763&item_id=289&lang=IT&task=item, where Itemid 763 is the item menu zoo category of the maincategory of the item. The problem is that the sh404sef component does not add this url to the duplicates of other urls of the same item, so have the same item_id where I have already set the default non-sef like: index.php?option=com_zoo&itemid=256&item_id=289&lang=IT&task=item. This generates a sef-url it/item/[alias-item] and when click there is a redirect 301.
I need zoo items to be united as duplicated.
Friday, 01 December 2017 16:50 UTC

Thanks for your message. You are on public forum, where we can only reply to pre-sale questions.

We provide support to our subscribers through our helpdesk.
After logging in, please open a ticket describing as clearly as possible the problem you're experiencing.

Thanks and regards
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.