Hi again!
Just want to report my findings, maybe they will be useful somewhere.
It was a template issue.
When I changed the template (my template = JA Teline 2)override file in:
templates/ja_teline_ii/html/com_content/category/blog_item.php
to the same one from Beez template, it all worked fine (well not the layout, but the jumi thing).
So searching through blog_item.php code from JA Teline 2 I found that the output of the text was stored in:
So I created a little hack in the file that says:
Code: Select all
$tochange = $this->item->introtext;
$part1 = array('{jumi [*1]}', '{jumi [*2]}');
$part2 = array('<h3 style="font-size: 150%; font-weight: 400;">', '</h3>');
$this->item->introtext = str_replace($part1, $part2, $tochange);
Note: For the sake of the story I should say that the really simple thing I wanted to use Jumi for here was to change between <h2>, <h3> or <h4> tags for the headings in the article depending on where the article is shown.
Now it works as expected in category and frontpage view (with the help of Jumi) and in category view (with intro texts enabled) with the aid of my little hack.
Off course this is not a solution that would for anything more complicated, but for this it works.
Note: I went back to using Jumi 2.0.3 instead of the 2.1 beta cause for this little task that I need to duplicate several times it was easier to write {jumi [*1]} than {jumi *1}{/jumi}. Call me lazy if you wish
Conclusion: With intro texts in category view enabled in my template things get messed up. I have my family waiting for us to go on holidays so I have not had the time to test:
1. If it works as expected in my template without using intro texts
2. Sort out why the h*ck it worked in Beez
Final note: I am not an advanced programmer of any kind so I hope this information will be helpful either to the development of Jumi or to somebody else in a similar situation.
Markus