[#11826] - Specifying template causes incorrect data to be used
- Fixed in Code Base
- 29 Aug 2016
- Medium
- Build: staging
- # 11826
- Diff
- mbabker:template-override-incomplete
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success JTracker/HumanTestResults Human Test Results: 3 Successful 0 Failed. Details
User tests: Successful: Unsuccessful:
Summary of Changes
The frontend supports overriding the active template by passing a template= query parameter. However, when this is passed, only the template name is overridden, ignoring all other data associated with the template (i.e. its params). This is also inconsistent with our fallback behavior onto Beez3 when the specified or configured template cannot be found which does use that template's full configuration object. This is corrected.
Testing Instructions
Pre-patch, with Protostar as the active template, make a request to index.php?template=beez3 and in the Beez3 index.php file add this line: var_dump($this->params)
You should have the Protostar template's parameters here. Apply the patch and refresh the page, you should now have the Beez3 template's parameters.
Documentation Changes Required
N/A
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Libraries |
| Labels |
Added:
?
|
||
- I have tested successfully.
- Before patch wrong parameter display and after patch it's working correct.
-
-
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11826.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11826.
| Status | Pending | ⇒ | Ready to Commit |
| Labels |
Added:
?
|
||
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11826.
wilsonge
- | Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-08-29 12:35:30 |
| Closed_By | ⇒ | wilsonge |
| Labels |
Removed:
?
|
||
I have tested this item✅ successfully on a0a1bb2
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11826.