@n0fear:

The latest Joomla! Version. Which one? I think you use Joomla 1.5.2 ... Hm?!

The warning results from the fact, that Clexus isn't compatible with Joomla! 1.5.x (not native / not legacy) like myPMS and myPMS-enhanced aren't compatible also (not native / not legacy). The only PMS's I know, that are compatible with Joomla 1.5.x today, are Messages (native), uddeIM (legacy) and Primezilla (legacy). No other one of the PMS's are working today with Joomla! 1.5.x. Try another PMS and you will see, it works

Greets
Frank

Joomla Advanced Message - J1.5 native

hi guys, i've found out this topic looking for a solution for the font size issue, but i don't understand..is there a fix? it seemed to me someone tried with no success..is it right or i didn't understand the solution? can anybody help?
font size is not working ..as i change it nothing happens.
thanks

Still random thread crashing, details here :
http://www.bestofjoomla.com/component/op...d,73/id,48180/#48180

jerry wrote:
Joomla Advanced Message - J1.5 native

Thanks Jerry, I'll give it a try too

Greets
Mc

@mcrollo No not 1.5. its 1.0.15 and well after changing in fireboard to mypms pro system and changing the links in the source to clexus it works, strange

Now the only bugs i still have is the font size, but here in this forum it works now, so there must be a fix but i can not find it =(

Well i am having a problem if you are checking a thread and in it few pages

lets say you are on page 3 and you wana go back to page 1

it doesnt let you

how to fix that?

thanks

Regards,

no answer for the font resizing fix?

Still no answer for the favorite and subscribe bug???

homy wrote:
Hello,

Here is the new bug!

I del a Topic / Thread sucessfully.
But the counter (Thread / Answer Counter) in the front, isn't set back.
I look in post.php, but in the code the database #_fb_categories is not coded.
So I must open the database and del it manuell.
I think this is a bug, isn't it?!

(SORRY FOR MY BAD SCHOOLEnglish , but I'm German )

Christian

Having the same bug. And it's not only in this version but in all the previous versions of Fireboard. And it must be a "high priority" bug and yesterday I upgraded my FireBoard to 1.0.4 with the hope to fix that bug but unfortunately it remains. Any solutions for that ?