Kunena 7.0.4 Released

The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.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 7.0

This category is for the module developed, endorsed, maintained and supported by the Kunena project team. The topics in this category only relate to the module developed for K 1.6 and later versions.

Question Unread-Status only on first post

More
14 years 4 months ago - 14 years 4 months ago #112947 by bkaertner
I had already tried the exchange of the response.php. No help.

I am just wondering. Is the unread-information stored on one place per thread per user ?
I ask, because usually all the posts from one thread are marked als unread.

If so, then in my opinion it should be a problem of the visualization, not the system itself.
The information, that the thread is marked "unread" is there, which can be seen on the marked first post.
Last edit: 14 years 4 months ago by bkaertner.

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

More
14 years 4 months ago - 14 years 4 months ago #112948 by bkaertner
I've just tested another thing: I opened two threads, to test the behaviour of the "normal" Kunena-View. I opened one thread with 1 post an one thread with two posts (one reply).

In the index-view of the content-window it shows on both threads "1 New" (1 Neu). Is this correct, or shouldn't it say "2 New" on one of them ?

EDIT: I redraw that one. :-) It shows the number of the new threads. If I enter the thread, it shows 2 posts. So this is correct.
Last edit: 14 years 4 months ago by bkaertner.

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

More
14 years 4 months ago #113179 by Matias
Unread indication is very limited in Kunena (that's the last larger task I really need to do for K2.0).

It works like this:

Every post which have been written during this session (logout/login doesn't clear it -- you need to wait) are marked as unread by default.
When you read the topic, that topic gets marked as read.
If someone posts to the topic, the whole topic gets marked back to unread using the same time limit.

So if you read topic with 20 new messages in it and someone replies.. You have all 21 messages as unread.

It's so annoying that I'm going to fix it before 2.0 gets out. :)

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

More
14 years 4 months ago #113192 by bkaertner
Thanks, that was what I had assumed. For the Module-Output I use "Latest Post", not "Latest Topics".

You have all 21 messages as unread.

If I understand right, this means, that if the topic is -however- marked as unread, ALL posts in mod_kunenalatest should be shown marked, which is not, only the first post of the topic.

So there must be a problem within the visualization of mod_kunenalatest. This has always worked before I used 1.7.1.

I've just tested it on another site of mine.
I could reproduce the problem.

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

More
14 years 4 months ago #113203 by Matias
You're right. Add a new menu item which displays the same information inside Kunena view. Can you reproduce the issue in there, or is it just the module?

Can someone from our team verify this issue and report it as a bug?

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

More
14 years 4 months ago #113219 by bkaertner
I'm not sure, but I think there is no comparable "Latest Posts"-View for menu items, as in the module. I am not sure, but ít seems to me, this "Latest"-view once acted like "Latest/Recent Posts" in the module.

In English its called "Recent Topics". (in german it was always called "Aktuell", but this is a translator-thing of the language-files, not sure 'bout the english names.)

"Recent Topics" seems to work as designed and shows for example "3 New !" after the topic.

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

Time to create page: 0.211 seconds