Blog view: FC creates no rows

Hi,

I am currently converting a big page from Joomla 1.5 to 2.5. Especially in the template area and its flexibility J 2.5 has been a huge step forward. I believe that the main FC template and output code is based on J 1.5 code. So, we are running into more and more issues the more we digg deeper into FC templates.

I just want to point some of this issues out from time to time. Perhaps for future templates they can be taken into account. For example in Joomla blog view Joomla takes the items per row, counts them and puts a div around every row. FC does the following:

So even if 3 is selected for items per row, the items are not counted, but even more put in one ul (can be easily changed into div, does not matter). The main pitfall is that it is impossible to design the items individually, like individual padding or shadows or so.

The standard Beez template gives the following output:

Do you know, what I mean?

Rooney

mmm, odd - even poses no problem , since it indicates a difference from the previous column

what is missing is adding a few CSS class names, i ll add this

Please note though, that FLEXIcontent blog template is not exactly based to neither J1.5 nor J2.5

But it makes sense to add these classes to match joomla template CSS for blog views ...

Also there are other changes that would be beneficial like change to match the CSS styling imposed for pagination by various joomla templates for J1.5 / J2.5

We, Angie Radtke, added that in our template and it was not that easy. Shall I send you the file?

Rooney

hello
can you post code and a link to see problem ?

Yannick,

i think he the original example is probably enough, the suggestion to match the CSS classes of Joomla's blog view in our FLEXIcontent blog template makes sense, since we would benefit of using the CSS styling of the Active J2.5 template.

I have opened this issue not to forget:
code.google.com/p/flexicontent/i ... ail?id=481

Same must be done for container tags and CSS for pagination ...

ggppdk wrote: I have opened this issue not to forget:
code.google.com/p/flexicontent/i ... ail?id=481

Same must be done for container tags and CSS for pagination ...

Yippihh!

Please consider to change all the needed class names (for example .pageslinks to .pagination) also.

Rooney