Kunena 6.4.8 Released

The Kunena team has announce the arrival of Kunena 6.4.8 [K 6.4.8] in stable which is now available for download as a native Joomla extension for J! 5.0.x/5.1.x/5.2.x/5.3.x/5.4.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 6.4
Important note: Go to the Kunena Dashboard after an upgrade so that the Kunena database tables are also updated. This is particularly necessary for major version jumps so that the table changes are adapted.

Solved Error 0 "Unclosed regex pattern at position: 160600" when reply/new topic

More
3 years 7 months ago #1 by Tormentor667
Error 0 "Unclosed regex pattern at position: 160600" when reply/new topic was created by Tormentor667
Dear developers and forum members,

since a few days, my users on my Kunena forum run into problems. When they try to reply or post a new thread, they get an error message (instantly after clicking the buttons):

Error 0 Unclosed regex pattern at position: 160600

The addon is at v5.2.8 and all other addons are up to date. What is going on here? Any ideas for a solution?

Link: www.realm667.com/index.php/en/forum-board

Best regards,
Torm

Please Log in or Create an account to join the conversation.

More
3 years 7 months ago #2 by Leen
Replied by Leen on topic Error 0 "Unclosed regex pattern at position: 160600" when reply/new topic
mm when I google a bit I read here and there that possibly sctript could be a mistake.
Has something changed at the hoster? or at least an extension of the website that is out of date.
i see eg this lab5_jpowertools last updated 2018
Have you turned it off for a while to test if it works?
Otherwise, set debug joomla site to maxium
maybe then comes on front which might be the cause..
With kind regards
Leen

Please Log in or Create an account to join the conversation.

More
3 years 7 months ago #3 by Tormentor667
Replied by Tormentor667 on topic Error 0 "Unclosed regex pattern at position: 160600" when reply/new topic
You rock! Lab5 JS Compressor was the problem, deactivating the compression of inline JS made the page work again. Thanks kindly :)
The following user(s) said Thank You: Leen

Please Log in or Create an account to join the conversation.

Time to create page: 0.234 seconds