Question Threaded view

yes, but not tomorrow, threaded view needs to be completely redone.

grmi64 wrote:

This is a BIG deal. I will not migrate to Kunena without this feature. It seems absurd that this would be removed.

grmi64 wrote:

Hi fxstein - are there plans to add this back in? My user base won't accept a "flat only" view.

"Absurd"? I think the word you're looking for is "disappointing". The threaded-view functions were removed for logical, rational reasons not absurd ones.

I'm sure the developers have plans to reinstate the function in a later version.

Stay with the older Kunena/Fireboard if your users are resistent to change but, bear in mind, you won't have much help when things "go south" and break. Alternatively, you could poll your user base and ask them whether they'd be prepared to accept a short-term loss of the threaded-view functionality. You might be surprised with the results. Perhaps you could sell them the concept? There are always "alternatives".

My user base "copped it sweet" and "took it on the chin" without a single murmur. :side:

"Absurd"? I think the word you're looking for is "disappointing". The threaded-view functions were removed for logical, rational reasons not absurd ones.

Point taken - I should not have used the word "absurd".

The lack of a threaded view will hold me up from migrating and I'm getting a lot of complaints about bugs with the current version of FB that I'm using (version 1.04).

Question for anyone that might know - is there someone working on a threaded view who I can collaborate with? I am willing to help get this going (I'm a software engineer) but I don't want to start from scratch if someone has started working on this. Does a collaboration area exist for this?

Thanks,

-Greg

Hello,

I'm willing to help, but I'm not a php-progammer...

The main problem with the old functions is, that you have different urls for the same post (one per thread-page in the flat view, one per message for the threaded view).

I think the target should be, that it's only one url per thread-page (independent from the view)... I think this prevent to have doppelt URL's in google (better for SEO).

So, now the problem is how to get different views in the same URL?

My first idea (open for discussion): :side:

1. We need a field in userdatabase or cookie that saves the view type (flat or threaded).
2. Dependent on the view type different CSS is loaded.
3. In the threaded view at the beginning all posts closed (hidden). If you go mouseover on a post, the complete one opened just about CSS (no new pageload needed)
4. Threaded and flat views have the same URL, but different CSS dependent on a field in user-database or cookie

The opening of a message in threaded view could work like the Slides from Tabs&Slides: www.joomlaworks.gr/content/view/15/42/

The main problem with threaded view wasn't URLs. We can live with different URLs as long as Google and other search engines are not getting them both (nofollow). So URLs can and should be different, so that your link would point always to flat view or threaded view (so that it's easy to recalculate new URL or show it in the original form).

There were two huge problems:
* Threaded view didn't work with huge threads, say with 50+ messages. It always loaded all messages to one page and with 1000+ messages loading that page took 5-10 minutes. So the feature breaks large forums.
* Forums should not show all the messages, thats why we have own view for it. Showing all messages from every thread.. I've seen over 5000 messages in one page.

Solution:
* Remove threaded view for forums. It's useless: you can always click on topics.
* Add pagination to threaded view, just like in flat view. There may be different limit for threaded/flat, but THERE HAS TO BE CONFIGURABLE LIMIT!
* Fix URLs for search engines: only one URL for a page.

Another reason for the removal was that the threaded code wasn't updated for ages and it was totally broken.

Thanks for the information... Now it's a little bit clearer...


To the problems:
- I have test a thread with 90 messages (it's my biggest one...) and more threads in one view (round about 700 messages) without any time problems - but this could depend on the used server... For me also a thread with 1000 message makes no sense (and if you have such threads the threaded view is even more important to know which message answer which other one.... mhhh a limitation of the message quantity per thread would be usefull.... ).

- Thats right - in my opinion threaded view makes only sence to show one thread with all message on one site (and not all threads)

To Solutions:

• Remove threaded views for forums: You are rigth: I think this could be easily done..
• Add pagination to threaded views: There are always a pagination function integrated which counts on threads. As you written we should switch it here to count on message. Therefore a new field in backend is needed (number of message on a page) and a modified query for pagination (pagebreak not after x threads but after x messages).
• Fix URL's for search engines: Is it enough to attach a now follow?