-
AuthorPosts
-
June 26, 2013 at 8:19 pm #188511
Details: Joomla 3.1, T3 Framework Blank Template
After I created a module style, it only works in certain parts of the template. For example: The assigned module style works in the sidebar 1 and sidebar 2. However, it does not work in the spotlight or footer. Why would this work in one area, but not the other? Everything is assigned properly in the backend. Any advice would be greatly appreciated!!
June 26, 2013 at 9:20 pm #497063It appears that the module styles work in the ‘mainbody.php’ block, but do NOT work in the spotlight-1.php, spotlight-2.php, footer.php blocks.
phong nam Friendphong nam
- Join date:
- May 2015
- Posts:
- 3779
- Downloads:
- 1
- Uploads:
- 587
- Thanks:
- 499
- Thanked:
- 974 times in 888 posts
June 27, 2013 at 9:05 am #497134Hi sdczen,
By default, on our T3 blank template, all published modules will be covered by this div tag:
<div class="t3-module module_suffix" id="Mod1">
</div>But when I used firebug to check out your modules, they are:
<div class="module-outline-2">
with outline-2 suffix css styles in your custom.css:
.span3 .module-outline-2, #t3-spotlight .module-outline-2, #t3-spotlight-2 .module-outline-2, #t3-mainbody .module-outline-2, #t3-sidebar .module-outline-2, #t3-footer .module-outline-2, #t3-footnav .module-outline-2 {
background: url('/images/RBSS.png') right bottom no-repeat;
padding-bottom: 13px;
}Not sure but I guess this issue is caused by our modified changes on our default blocks. Pls try to test your suffix class on the fresh T3 blank installation if possible.
June 27, 2013 at 4:41 pm #497207I was having problems with the module class suffixs showing up while using t3blank. I then created a new module style using chrome, in modules.php. The style I created works great when a module is loaded in the mainbody.php, but for some reason when this module style is called in the spotlight-1 & 2, and footer.php, it doesn’t display.
I still cannot get any module class suffix to show up in firebug when I add it in the backend. There is something different about the spotlight & footer blocks. At least on my end.
Here is the module function I created in the modules.php that works fine when modules are loaded in the mainbody.php (sidebar1 &2).
function modChrome_dropshadow($module, &$params, &$attribs)
{
if (!empty ($module->content)) : ?>
<?php if ($params->get('moduleclass_sfx')!='') : ?>
<div class="<?php echo $params->get('moduleclass_sfx'); ?>">
<?php endif; ?>
<div class="module-outline-1">
<div class="module-outline-2">
<div class="t3-block">
<?php if ($module->showtitle != 0) : ?>
<div class="module-title">
<h2 class="title"><?php echo $module->title; ?></h2>
</div>
<?php endif; ?>
<div class="module-content">
<div class="in-module-content">
<?php echo $module->content; ?>
</div>
</div>
</div>
</div>
</div>
<?php if ($params->get('moduleclass_sfx')!='') : ?>
</div>
<?php endif; ?>
<?php endif;
}The working CSS is:
.span3 .module-outline-1,
#t3-spotlight .module-outline-1,
#t3-spotlight-1 .module-outline-1,
#t3-spotlight-2 .module-outline-1,
#t3-mainbody .module-outline-1,
#t3-sidebar .module-outline-1,
#t3-footer .module-outline-1,
#t3-footnav .module-outline-1,
#t3-module .module-outline-1,
#container .module-outline-1
{
background: url("/images/LBSS.png") left bottom no-repeat;
}
.span3 .module-outline-2,
#t3-spotlight .module-outline-2,
#t3-spotlight-1 .module-outline-1,
#t3-spotlight-2 .module-outline-2,
#t3-mainbody .module-outline-2,
#t3-sidebar .module-outline-2,
#t3-footer .module-outline-2,
#t3-footnav .module-outline-2,
#t3-module .module-outline-2,
#container .module-outline-2
{
background: url('/images/RBSS.png') right bottom no-repeat;
padding-bottom: 13px;
}
.span3 .t3-block,
#t3-spotlight .t3-block,
#t3-spotlight-1 .t3-block,
#t3-spotlight-2 .t3-block,
#t3-mainbody .t3-block,
#t3-sidebar .t3-block,
#t3-footer .t3-block,
#t3-footnav .t3-block,
#t3-module .t3-block,
#container .t3-block
{
padding: 0px;
-moz-box-shadow: 2px 2px 9px rgba(0,0,0,0.1), -2px -2px 9px rgba(0,0,0,0.1);
-webkit-box-shadow: 2px 2px 9px rgba(0,0,0,0.1), -2px -2px 9px rgba(0,0,0,0.1);
box-shadow: 2px 2px 9px rgba(0,0,0,0.1), -2px -2px 9px rgba(0,0,0,0.1);
background: url('/images/MGS.png') left bottom repeat-x #fff
padding: 5px;
border: 1px solid #fff
}In the joomla backend > module > Options > Advanced options > Module style > dropshadow
June 27, 2013 at 6:10 pm #497225It appears for some reason, the module class suffix (not module style) was not working with some of the modules. I have a rudimentary style that will probably be acceptable. I’d still rather have the multi-layered module style.
I don’t know why some modules won’t allow the module class suffix to work properly. I’ll keep you posted if I find anything more
phong nam Friendphong nam
- Join date:
- May 2015
- Posts:
- 3779
- Downloads:
- 1
- Uploads:
- 587
- Thanks:
- 499
- Thanked:
- 974 times in 888 posts
June 28, 2013 at 10:05 am #497283Hi sdczen,
I will have to spend lots of my time to check out your overriden module functions in both footer & spotlight position.
Pls try to take backup your files & replace your overriden functions in modules.php by our default ones:
function modChrome_T3Xhtml($module, &$params, &$attribs)
{
$badge = preg_match ('/badge/', $params->get('moduleclass_sfx'))? '<span class="badge"> </span>' : '';
?>
<div class="t3-module module<?php echo $params->get('moduleclass_sfx'); ?>" id="Mod<?php echo $module->id; ?>">
<div class="module-inner">
<?php echo $badge; ?>
<?php if ($module->showtitle != 0) : ?>
<h3 class="module-title"><span><?php echo $module->title; ?></span></h3>
<?php endif; ?>
<div class="module-ct">
<?php echo $module->content; ?>
</div>
</div>
</div>
<?php
}Then check out the module styles after changing.
Leo
1 user says Thank You to phong nam for this useful post
June 14, 2014 at 12:39 pm #538906Where do you put this code at? I am having the same problem.
June 14, 2014 at 1:23 pm #538912disregard!
-
AuthorPosts
This topic contains 9 replies, has 4 voices, and was last updated by Adam M 10 years, 5 months ago.
We moved to new unified forum. Please post all new support queries in our New Forum