Pending

User tests: Successful: Unsuccessful:

avatar jamesfu
jamesfu
1 Dec 2017

Currently, regardless of which Module tag is selected when creating a Custom module (Custom > Advanced > Module Tag), the <div> tag is always applied. This PR fixes the bug by applying the user-desired HTML tag.

Pull Request for Issue # .

Summary of Changes

Updated hardcoded div tag with $params->get('module_tag')

Testing Instructions

Create a new Custom module, and change Module Tag to something other than div

Expected result

Resultant Custom module should be enclosed in selected tag

Actual result

Resultant Custom module still enclosed in div tag

Documentation Changes Required

avatar jamesfu jamesfu - open - 1 Dec 2017
avatar jamesfu jamesfu - change - 1 Dec 2017
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 1 Dec 2017
Category Modules Front End
avatar brianteeman
brianteeman - comment - 1 Dec 2017

Doesnt this depend on the chrome being used for the template position?


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18934.

avatar franz-wohlkoenig franz-wohlkoenig - change - 2 Dec 2017
Status Pending Information Required
avatar jamesfu
jamesfu - comment - 2 Dec 2017

Whoops, sorry! Didn't realise the module tags are implemented by chromes, not the module template.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/18934.

avatar jamesfu jamesfu - change - 2 Dec 2017
Status Information Required Closed
Closed_Date 0000-00-00 00:00:00 2017-12-02 08:22:15
Closed_By jamesfu
avatar jamesfu jamesfu - close - 2 Dec 2017

Add a Comment

Login with GitHub to post a comment