-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New view based routing fails with raw links #9950
Comments
I can't seem to reproduce this issue. Can you give me the exact steps you took, starting from a fresh install with default sample data, that lead to getting broken links? |
@joomlajoe See #9953 Is that the problem you are reporting here? |
@joomlajoe Is this using the 3.6 branch? Notifying @Hackwar |
Yes i found the exact line to fix the issue. It's happening in the JComponentRouterRulesMenu preprocess function.
to fix the issue this should be changed as following:
Please notify @Hackwar To reproduce this it's easy, i just installed a 3.6 branch with few sample data. Navigating menu and observing menu links everything is ok. |
Hi In my joomla 3.5.1 error logs I too get the following. |
@crazynex No, this has nothing to do with your issue. That code is not active yet and your issue will have a different source. @joeforjoomla The code is the same as we have in Joomla right now. The issue looks more like a configuration issue on your end. |
I can no longer replicate this on the 3.7 branch. On my local copy going to http://localhost/~george/joomla-cms/component/content and http://localhost/~george/joomla-cms/component/tags and both perfectly accessible I can also access http://localhost/~george/joomla-cms/index.php?option=com_content&view=article&id=1 without issues I'm going to close this issue. If you can replicate it please feel free to and provide a bit more information! |
I currently tested again but the issue is still there in the 3.7 dev https://developer.joomla.org/nightlies/Joomla_3.7.0-dev-Development-Full_Package.zip By the way the problem is not about accessing pages as you say; http://localhost/~george/joomla-cms/component/tags The problem is that if a page link is not routed to any menu item all links from components using the new router or even not using the new router generated by Joomla menus are broken. See self explaining screenshots below, accessing normal page link with a routed menu item alias like http://joomla37/en/about you see that the log out menu item has correct link: http://joomla37/en/log-out Accessing normal page link without a routed menu item alias like http://joomla37/en/component/tags you see that the log out menu item has broken link: http://joomla37/en/component/users/?Itemid=101 Let me know if i should test another branch, also notice that i provided a fix for this issue months ago. |
Ahh ok I understand now. Thanks for the screenshots! That helps a lot! |
You are welcome George, happy to help if possible :) |
OK PR #12020 - this is effectively your code change but slightly further up the file |
Steps to reproduce the issue
For components implementing the new routing linked to menu items, all menu items links are broken when executing Joomla with raw URLs or URLs not routed to any menu items such as 'component/contact'
Expected result
Opening a Joomla link such as http://www.domain.com/component/contact, http://www.domain.com/component/tags or using a raw link such as a link to generate a sitemap http://www.mysite.com/index.php?option=com_osmap&view=xml&tmpl=component&id=1
will result in all Joomla menu items links broken if the linked component implements the new view based router.
Actual result
All links are broken, they don't stay the same as when clicking on a menu item having an alias.
Appending a casual alias before the raw link, even if a not existent alias, all links are generated again correctly.
http://www.mysite.com/randomstringalias/index.php?option=com_osmap&view=xml&tmpl=component&id=1
System information (as much as possible)
Testing Joomla 3.6 dev branch
Additional comments
The text was updated successfully, but these errors were encountered: