[#9712] - Isis and hathor frontend links: Frontend uri scheme can be different from admin
- Fixed in Code Base
- 25 May 2016
- Medium
- Build: staging
- # 9712
- Diff
- andrepereiradasilva:solves-8109
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success JTracker/HumanTestResults Human Test Results: 2 Successful 0 Failed. Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #8109 .
Summary of Changes
This updates Isis and hathor templates frontend links because joomla allows different schemes for admin and frontend site.
Testing Instructions
- Use latest staging.
- Set the site to "Force SSL" in "Administrator Only" in global config.
- Notice, that you are in
httpsin admin as you selected, but:- the frontend preview link (top right) is
https - the "View site" link in (bottom left) of the admin panel is
https - the "Go to site home page." link in the backend login page is
https(in isis and hathor templates)
- the frontend preview link (top right) is
- Apply the patch.
- Repeat steps 2 and 3 and you will notice the links are now
httpas they should.
| Status | New | ⇒ | Pending |
| Labels |
Added:
?
|
||
| Title |
|
||||||
| Title |
|
||||||
| Rel_Number | 0 | ⇒ | 8109 |
| Relation Type | ⇒ | Pull Request for |
| Category | ⇒ | Administration |
I have tested this item 
successfully on f8c13c5
Tested with success for both Isis and Hathor templates.
@andrepereiradasilva Maybe you should update the summary of changes ("This updates isis template preview links ..."= so it reflects that also Hathor has been changed.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
done
@andrepereiradasilva can you have a look into the merge conflicts?
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
This PR has received new commits.
CC: @richard67
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
conflicts fixed
I have tested this item successfully on b33de49
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
I have tested this item
Fantastic!!
Thanks :)
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9712.
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
?
|
||
| Milestone |
Added: |
||
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-05-25 19:47:01 |
| Closed_By | ⇒ | roland-d |
| Labels |
Removed:
?
|
||
Thanks everybody
@stellainformatica can you check this PR solves the issue?