[SOLVED] Module Class Not Working in CB 2+

Just a little bug report. Or a big bug report if you use multiple CB login modules and need to separate the styles. The 'Module Class Suffix' field doesn't work.

This will also cause issues when upgrading from 1.X to 2.X if you have styled your login module using the module class suffix.

If you create a new login module, it will work but only shows in the main module <div>.... not on the <form> or on the <input>s like it did on the old module. The module itself hasn't actually changed. I'm going to go ahead and put the class in mod_cblogin.php in hopes that this will get fixed during the next update.

It's a standardized parameter that Joomla handles entirely when processing module output (modules.php template file). It's not supposed to be a part of the modules code or layout. The suffix should append to the container div of the module. See Joomlas login module as it has the same behavior, which our module is now designed to mimic. Previously in CB 1.x the suffix was added all over the place, which was wrong. If it's not being output it's possible your Joomla template doesn't have a modules.php template file resulting in it being missing.

Actually, I created a new test module just to check... and it does work if you create a new module. But if you upgrade from CB 1.x to CB 2.x, for some reason, it doesn't work. Exact same module... I see that there really isn't any changes to mod_cblogin.php. Yes, it was all over the place. Which is a bummer when you upgrade if you used those for your styles. But it's not too big of a deal to re-name the classes/IDs. In this case, I won't alter the mod_cblogin.php file.

If you do choose to alter the display leave the PHP file alone. Our modules completely support Joomlas layout functionality. You could create a new layout for the module or copy and modify the existing then add it to your Joomla template and select it as your layout in the module. This avoids having to modify any core module code, but allows you to adjust its display.

That's what I was going to do. I'm using it in a menu though; so I just used the menu item ID to differentiate the styling.

By the way, thanks for the super quick responses, Kyle.