[#5502] - Routing: Legacy Router Rule for com_contact
- Closed
- 2 Aug 2015
- Medium
- Build: staging
- # 5502
- Diff
- Hackwar:com_contact_router_legacy
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
This implements the current routers behavior of com_contact as a legacyrouter. This is meant for those that want to keep the old behavior at all costs. Later, parameters will be introduced to switch between the legacy behavior and new features.
This router is copied verbatim from the current router to make sure that the same behavior is kept. No changes should be done to it until Joomla 4.0, when this is supposed to be deleted. The component routers right now are so fragile, that a slow transition will be next to impossible. To prevent any breaks in backwards compatibility, this legacy router is introduced, so that people having problems with the new router can switch back.
How to test
- Check your site before applying the patch and see the URLs of com_contact.
- Apply the patch.
- See the URLs of com_contact to stay the same.
Dependencies
This PR requires #5446 to be accepted by the project before it can be applied.
This was made possible through the generous donation of the people mentioned in the following link via an Indiegogo campaign: http://joomlager.de/crowdfunding/5-contributors
jissues-bot
- | Labels |
Added:
?
|
||
| Category | ⇒ | Router / SEF |
designbengel
- 
| Status | Pending | ⇒ | Ready to Commit |
RTC based on testing. Thanks!
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5502.
| Status | Ready to Commit | ⇒ | Pending |
Thanks @Hackwar moving back to pending. This also needs to be updated to staging as github say we have merge problems. Thanks 
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5502.
joomla-cms-bot
- | Labels |
Added:
?
|
||
This has been updated to work with the latest implementation of JComponentRouterView. Please test.
No, this is expected. The original PR was from a time where no 3.5-dev branch existed. Since the basic classes were merged into the 3.5-dev branch, I had to pull in the 3.5-dev branch into this one to make everything work. Since we can't switch branches for PRs after they have been created, I can't correct that. But overall, this is perfectly fine this way.
Same as in the other one. Please close this PR and create a new PR from this branch against 3.5-dev. then.
Same as in the other PR: no.
#5444 was against staging and was merged by you guys into 3.5-dev. The other PRs are depending on that code and thus I need to merge that code into this PR. I did discuss this with George. I know how to use git and this here was the reason why I proposed to use a different branching scheme than the current one.
If we were to create a branch for the current minor release and let people create bugfixes against that branch instead of creating a branch for the NEXT minor release and thus force ALL PRs that are meant to go into a minor release to be closed and re-opened or manually merged, we could develope the future version of Joomla in staging and bug-releases would really just be bug-releases, because only serious issues/regressions would be solved by PRs that are targeted at the current minor release branch. But the way it is now, a feature that I'm working on (like for example the routing) would either have to be aimed at staging and then create this mess that we have right now, or you would have to open it against the next minor release branch, then see it not getting merged, close it, open it against the then next minor release branch, again not seeing it being merged, closing, re-opening and then hoping that people will finally get this.
| Status | Pending | ⇒ | Ready to Commit |
| Status | Ready to Commit | ⇒ | Pending |
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-08-02 16:21:58 |
| Closed_By | ⇒ | Hackwar |
tested successfully
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/5502.