Skip to content
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

Classes added to Module Class Suffix in custom html module break in certain positions #9115

Closed
N8Solutions opened this issue Feb 13, 2016 · 3 comments

Comments

@N8Solutions
Copy link

commented Feb 13, 2016

There is a bug where if you add a class to a custom html module using the Module Class Suffix box under the Advanced tab it replicates the classes entered showing it on the front end twice. Twice meaning that it adds the classes once around the container which includes the Title and a second time around the text inside the custom html module.

To duplicate this, simply add any class you want in the Module Class Suffix box for a published custom html module. Preferably a class that you can see such as a border or drop shadow. Make sure the custom html module is published in either one of the Side positions or the Footer positions such as these from the Beez3 template.
Footer Top: position-9
Footer Middle: position-10
Footer Bottom: position-11
Left Middle: position-4
Left Bottom: position-5
Left Top: position-7
Right Middle: position-8
Right Bottom: position-6
Right Top: position-3

It appears to work fine if published elsewhere.

This is also not template specific as I have reproduced this using Protostar, Beez3, and several other 3rd party templates.

Original Joomla forum post for this issue can be found here:
http://forum.joomla.org/viewtopic.php?f=728&t=906976

screen shot 2016-02-13 at 07 00 48
screen shot 2016-02-13 at 07 00 48

@Webdongle

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2016

Can confirm this is happening with Staging and 3.5.0 beta 2.

custom 01

@Bakual

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2016

It's the case for most modules. The reason is that this parameter is used both in the module chrome from the template and the module output itself.

I doubt we can change it without breaking something. Just write your CSS rules so it matches only one instance (eg combine your CSS rule with the other class present)

@Webdongle

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2016

Yep, got it ... thanks

custom 02

@Bakual Bakual closed this Feb 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.