Official support hours: from 9 AM — 6 PM Monday to Friday (GMT +2).
The support staff may not reply on technical inquiries on weekends; all requests will be answered necessarily during working days. Reply time: depending on the complexity of your issue, the answer can be provided between a few hours up to 48 hours. In the particular instances we will notify you if extra time will be required to solve the issue.



The forum is in read only mode.

Template Kunena 5.1.1 crashes template RND Kinstance

5 years 3 months ago - 5 years 3 months ago #796 by Wouter NL
Tody I have updated my website to Kunena 5.1.1
After that update, the site is crashing when I open the menu-item Forum.
When I swith to an other tempolate like Crypsisb3, the forum is back again.

But I don't like that template.
I like the RND Kinstance.

So is it possible to update RND Kinstance soon, so it is compatible with the latest Kunena release?
5 years 3 months ago #797 by Dmitry

Can you be more specific - is it some error displayed or...?

Best regards,
5 years 3 months ago #800 by Wouter NL
When I select this template and visit tghe forum page, I see an error page in Firefox which tells me there is an unsupported way of compression ndetected.
5 years 3 months ago - 5 years 3 months ago #801 by Dmitry
That is not a easy and straight forward error to solve. See:

I do not have such error with RND Kinstance on test website (Kunena 5.1.1 and Kinstance 1.2.0).

Is this error only on index page or on all forum pages?

5 years 3 months ago #802 by Wouter NL
I've checke the settings but there is no gzip compression active.

And ithe error will appear at every kunena URL in combination with the RND Kinstance template.
At the moment I have Crypsisb3 as defauklt template and then Kunena is running well.
5 years 3 months ago #803 by Dmitry
Well this will take time to check all template files for issues and compare it to default Kunena template. A lot of changes has been made in 5.1.

The main problem here is that on our testing server there is no such error, so we will never know - our changes will fix this particular issue or not :(

Moderators: Eugene S.