Bug 283778 - Only current blog post shown when switching to normal to combined view
Summary: Only current blog post shown when switching to normal to combined view
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.7.2
Platform: Fedora RPMs Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-11 11:28 UTC by Graham Flett
Modified: 2017-01-07 22:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot after Step 3. (206.15 KB, image/jpeg)
2011-10-11 11:28 UTC, Graham Flett
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Flett 2011-10-11 11:28:35 UTC
Created attachment 64405 [details]
Screenshot after Step 3.

Version:           4.7.2 (using Devel) 
OS:                Linux

When switching between normal view mode and combined view mode while a blog entry is shown in the bottom pane, only the post being read is shown in the combined view. It looks as if this is the only entry for that blog feed.

Selecting a different feed and then re-selecting the feed corrects the problem.

(This is on Fedora 16 Beta with KDE 4.7.2)

Reproducible: Always

Steps to Reproduce:
1) Select normal view.
2) Select a post from a feed (say planet.kde.org). The post appears in the bottom pane.
3) Select combined view.

Actual Results:  
Only the selected post (in step 2) is shown.

Expected Results:  
The entire blog feed is listed.
Comment 1 Denis Kurz 2016-09-24 19:43:32 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:01:53 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.