Topic-icon Page class suffix parameter doesn't work for SCLogin module !!!!

Active Subscriptions:

None
7 years 11 months ago - 7 years 11 months ago #58082 by ventluc
I use Joomla 3.5.1 and JFBConnect 7 in my web site (www.venturaluca.com/portal). I need to use "Page class suffix" parameter of a particular instance of SCLogin module (that I put in custom "SCLogin" position of my template for the registered users assigning it to all pages except for the home page) but it doesn't work. In fact I have more instances of SCLogin module in different pages of my web site and only for one of them (that I put in custom "SCLogin" position of my template for registered users assigning it to all pages except for the home page) I need to modify default css style of the module because I would like to change the text color: so the best thing to do would be to use the "Page class suffix" feature of Joomla. The problem is that when I insert "css_sclogin" (that is to say the name of css class that I defined to change the text color of the module) as value of the parameter "Page class suffix" of the SCLogin module, this css class is never used in the css code of the module (I checked it examining the css code of the SCLogin module in the front-end of my web site) !!!

How come?

Let me know,

thanks.

Luca
Last edit: 7 years 11 months ago by ventluc.
The topic has been locked.
Support Specialist
The moduleclass suffix parameter is a feature of Joomla. Templates in Joomla must be configured to apply the proper 'chrome' to each module position that you want to enable the moduleclass suffix to work on. You can see a list of the different types of chrome available and how the moduleclass suffix would be applied on the page below:
docs.joomla.org/Standard_Module_Chromes

In general, the XHTML option is the most common. If your template isn't supplying the chrome attribute, then the suffix will be ignored.

I hope that helps explain,
Alex
The topic has been locked.
Active Subscriptions:

None
7 years 11 months ago - 7 years 11 months ago #58104 by ventluc
Alex,
in this case the problem doesn't depend on the template that I used because "Page Calss Suffix" feature works perfectly with other components and with the same template! :-)

Other ideas? :-)

Thanks in advance,

Luca
Last edit: 7 years 11 months ago by ventluc.
The topic has been locked.
Support Specialist
Can you do the following:
* Configure the standard Joomla login (mod_login) to display in the same module position
* Set the class suffix parameter similar to what you did in SCLogin
* Check if that works.

If not, then it means your template isn't rendering the module how you want. If it does add the suffix properly, please leave the mod_login and SCLogin modules enabled in that position and let us know the URL to look at. We'll need to investigate why our module is behaving differently.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
Hello!!

I did the tests you suggested me to do with the same result !! Anyway I discovered that the problem resides on the position I choose for the module: in fact if I put the module "ScLogin" in position "sclogin" (a custom position that I added in my template) the page class suffix is ignored !!! Instead if I put the module SCLogin in other default positions of the template Page Class Suffix parameter is used correctly!! How come? Can you check the problem by yourself? If you want I can give you access to my Joomla Admin Panel..

Thanks a lot in advance.

Luca
The topic has been locked.
Support Specialist
I figured that would be the case :) Again, it's your template. The template itself defines each module position that will be displayed *and* the 'chrome' to use for that position. It's out of our hands if the template sets up the module position in a state that doesn't use the moduleclass_sfx. You'd need to contact the template vendor for how to change the chrome setting for the specific module position you're trying to use.

Since it sounds like you created the module position yourself, look at how the other module positions are being inserted by the template and make sure you're using the same code as the position that works properly.

Thanks,
Alex
The topic has been locked.