Yeah ... Yeah I know, why do you have to read all the B.S. from this guy, just get to the point already.
Doing up the block style was easier that I thought. I actually stumbled across that after making a couple of changes then refreshed and saw the changes held. So it does not hurt to experiment even on production site. Seems right now xmline uses the block named below for the display of the custom blocks. And I stumbled in while playing.
What did I do?
I set up some styles on the module templates and tweaked styles in the xmline css file in the xmline/include dir too affect the display of the expanded pages. Again, images cannot be displayed in the "custom" blocks that's strictly a rss text feed. As other's have mentioned it would take quite a bit more investigation to alter the image idea. Images are in the expanded portion... that's good enough for me right now.
On the front page of
servicelance the look is controlled by the block template and a simple style tweak. I'm still playing with it to display it more to my liking. I know how just have not done it yet.
But here are the changes you need to know for the blocks.
ie., this will not affect the story title only the block text.
In the XMline templates section of your web site open xmline_block_spotlight.html
Change this line
<{$item.description}>
to this
<div style="font-size:0.9em;"><{$item.description}>div>
You could do fonts in px or pt as well I used em. You can also ad padding to inset the block content so it does not hug the borders.
To remove additional vertical spacing above below item. description remove
statements to shift up or down.
Quote:
I've also just installed Drupal, so would be interested in learning how to "pull" feeds from it. I've set up the aggregator in it.
In my reference to blog code like Drupal. The major difference to XOOPS and xmline module combination. The content you pull in with xmline works on the FIFO (first in first out) principal. So the content never really resides in any database on your site for future reference. You might get it indexed but that will lead to dead links on your site. However your internal "expand" url's will all be indexed but they will not work as expected since the content is ever changing.
Drupal on the other hand has it's own "built-in" aggregator and allows admin/user categorical freedom to feed the aggregated content to site visitors based on a determined taxonomy. Since Drupal also is a "blog style" storage medium it happily catalogs that information for future SE reference based on, taxonomy, that word again. For instance google would index the drupal site and all content beneath the link because it's there visible all the time, while the RSS feeds in XOOPS do not do that at all.
All that for a single line of code
![](https://xoops.org/uploads/smil42e7a3d4c7b9f.gif)
Have fun!
regards,
rocket98