• Home
  • Get help
  • Ask a question
Last post 9 hours 33 min ago
Posts last week 141
Average response time last week 4 hours 42 min
All time posts 67805
All time tickets 10478
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
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.

#7393 – SEF urls -- "item" and id showing

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 14 September 2020 15:34 UTC
Verticalife

Hi, first of all many thanks for bringing such a functional extension to joomla, I've been using this one on other websites too.
However, on a new website i'm developing i'm having some issues.
For the second time i used SP pagebuilder to try out the functionalities, which are great, but this somehow has messed up the SEF urls (i'm sure i'm missing out something very basic but i can't find what's the problem).
I'll try to be as clear as i can:
- i have a category which is a SPPB page and has a section which loads K2 items from a K2 category:
http://xxxx.it/attivita/trekking/bobbio-pellice

But as you can see, if you click on the item (K2 item) the URL is completely messy:
http://xxxx.it/item/4-rifugio-invincibili

What i'd like to achieve is something like:
http://xxxx.it/attivita/trekking/bobbio-pellice/rifugio-invincibili

I have also tried creating another menu item for a subcategory to contain all the items (feel free to check on this too if it helps, i'll give you backend access credentials at the end of this message), but to no avail.

This whole thing is strange, as for the first website i made with both SPPB and K2 i used a similar menu items nesting and everything went fine, here's the url just for comparison: https://xxxx.it/

----------------
BACKEND ACCESS
un:
xxxx

pw: 
xxxx


Looking forward to your reply, have a great day!
BR,

Andrea

Monday, 14 September 2020 16:21 UTC
wb_weeblr

Hi

sh404SEF does not build URLs for K2. It goes the opposite way, as with several large extensions: they provide support for sh404SEF instead.

Prior to K2 version 2.7, sh404SEF support was built into K2. From version 2.7 upward, they removed support from the main component and put that code into a separate "K2 for sh404SEF" plugin that you have to get separately - from them

IMPORTANT: I just had another user this morning who reported an issue with the latest version of that plugin. They have a large bug in it and it causes all URLs to go to the home page of the site. That user was supposed to report the problem after I debugged and identified it but I'm not sure they have published and update yet.

I have sent them an email but not heard from them back yet.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Monday, 14 September 2020 17:44 UTC
wb_weeblr

Hi again,

After speaking with K2, they released a new version of their plugin that fixes the problem, so you're safe to use it now.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Monday, 21 September 2020 10:09 UTC
Verticalife

Hi Yannick, thanks a lot for the reply and dedication, i will get that plugin as you suggested!
Have a nice day, best regards

Andrea

Monday, 21 September 2020 11:27 UTC
wb_weeblr

Hi

You're welcome! I will leave this ticket open in case you need to add something. It will automatically close in 2 weeks if no further comment is made.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Thursday, 22 October 2020 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
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.