XoopsCore
XoopsCore copied to clipboard
Background for each block
I have a wish to our core developers:
I have created my latest websites as real onepage-website, and I am using only blocks to provide all information/functionallities. If I want to have a striped design or different backgrounds for the different blocks, I solved it at the moment in the way, that I defined diffent backgrounds for the block groups (e.g. left blocks = grey, top left block = white, top center block = dark grey, top right block = white, and so on...) But now I can only but one block in one area. It would be helpful, if it would be possible to define for each block himself the background when editing the block properties/options (like weight, visible in...)
I hope, its clear, what I mean
Hi, yes, it's clear and i understand what you want but you can use css with the same define too, no ?
In the css I can define the backbround for e.g. the left block area. if you have 3 blocks in the left block area, then all 3 blocks get the same html (structure, classes,...), only the content himself (title, text,..) is different. The html is build by xoops system (title by system, content based on the module block template), the content will be filled in by module block function. but they have all the same background. To solve this, I have to put manually in the template from the various blocks an unique identifier, then I can make via css a different background, but only for the content background, because the header is build by the system, the template for a block contains only the html for the content range.
clear?
Sure i understand. it's not implemented on the core but it will be great if we can add a tag for css in the block creation.
But, may be you can use a tip : Modify your template :
< d iv class="blockContent cssblock-{$block.id}"><{$block.content}> < /d iv >
and define in your cssfile : cssblock-2 cssblock-5 cssblock-17 ...
hi alain, yes, i know this. But it includes only the block content, not the complete block ;-) But, whatever, thank you for the tip. but I hope, they implement it in the core, this would be much more elegant :-)
its only a suggestion for the future ;-)