• Home
  • Get help
  • Ask a question
Last post 4 hours 8 min ago
Posts last week 141
Average response time last week 4 hours 42 min
All time posts 67794
All time tickets 10475
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.

#3457 – I found the source for view=categories URLs (ticket #3421)

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.
Thursday, 30 March 2017 13:52 UTC
TheSDHotel
Hey there man,
How are you?

I wanted to let you know that I found out the source for the issue described in ticket #3421, more specifically the weird URLs containing the "view=categories" option, which get created for several menu items (but all point to the root category) and that can be found stored in sh404sef URL manager with a SEF URL as: "name-of-the-menu-item".
Again if you don't remember the issue in detail you can read ticket #3421 again.

So, I temporarily activated data recording to see if I could find out more about where they come from... and I did. I found out that those URLs are created upon editing an article from the frontend. More specifically, upon SAVING an article from the frontend. This can be replicated on a stock Joomla too.

For example:

- Create a Menu Item as a Category Blog
- Enter that Category Blog Menu in the frontend
- Enter an article inside that Category Blog
- Click the Edit button to edit the article from the frontend
(at this point the "issue" still didn't happen)
- Save the article. (even without changing anything)
- Boom, here it is, the weird URL with "view=categories" has been stored in URL Manager, with a SEF URL formed by the name of the menu item from which the article belonged to. For example if the menu item was called "test-menu", now you will have an URL called "test-menu" which for some reason randomly lists all categories contained in the root category.

I'm really not sure why this gets created by Joomla as this is a broken link in all effects. It has no purpose in existing and it doesn't get used anywhere.

To give you more information on why this might get generated and then stored by sh404sef, I also compared the article editing URL when sh404sef is enabled and when is disabled

Normal Article Editing Non-sef URL with sh404sef disabled:
?view=form&layout=edit&a_id=3&catid=8&return=...

Article Editing Non-sef URL with sh404sef enabled:
index.php?option=com_content&Itemid=103&a_id=3&catid=8&lang=en&layout=edit&return=...

As you can see they're different, sh404sef adds the menu id, which is not even present in the default Joomla article editing URL.
Now, I'm not sure if this has anything to do with those "view=categories" URLs that get stored, but it's a difference that I thought I'd report in case it helps you.

Either way, do you think it's possible for you to prevent sh404sef to store these nonsensical URLs every time you edit an article from the frontend?

Thank you very much in advance
Thursday, 30 March 2017 17:29 UTC
wb_weeblr
Hi

Great finding! I will make a note and try to look at it, but as mentioned before, and as confirmed by your finding here, those URLs are not exposed to search engines, so there is no big harm done, just some waste.

The difference in URL doesn't matter, especially the Itemid, as we do not use menu items to build URLs, and that's not the URL in question anyway. What's more surprising is the lack of view=form, I would have to check what's happening here.

As for avoiding those being stored, it entirely depends on why Joomla is creating the URL in the first place, and it might not be possible, because when we receive a URL to be transformed into a SEF, we have no idea of the context, where it comes from, and so it's not usually possible to make such decisions.

I'll keep you updated here.

Rgds
 
Friday, 31 March 2017 09:49 UTC
TheSDHotel
Thanks for your detailed and complete reply, let me know if you find a way to do it and thank you very much!
Tuesday, 04 April 2017 13:14 UTC
TheSDHotel
Hey there man,
I noticed that the other ticket about the other "pending issue" (the one where the &lang=paramater gets inserted in the wrong order in certain cases) got closed automatically, so I'll re-send you the link to it too: https://weeblr.com/helpdesk/sh404sef/3411-two-new-bugs-this-time-reproducible
Just in case.
So we can keep track of these two pending issues if you make any progess on them :)

Tuesday, 04 April 2017 13:56 UTC
wb_weeblr
Hi

We keep tracks of reported bugs, or features that we want to build in in our internal bug tracker. Nothing of our discussion is being lost, simply the tracking is not done here, that would be impractical for development - and of course much of the new features/changes are not coming from here anyway.

Rgds
 
Tuesday, 04 April 2017 14:03 UTC
TheSDHotel
Oh okay sure, that makes sense. If you can/want, keep me updated on the eventual resolvings of the bugs! :)
Thanks
Best Regards
Thursday, 20 April 2017 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.