Bug 156905 - Akregator article view does'n use adblock filters
Summary: Akregator article view does'n use adblock filters
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.10.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 203549 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-29 12:22 UTC by Maciej J . Woloszyk
Modified: 2018-02-01 09:45 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej J . Woloszyk 2008-01-29 12:22:18 UTC
Version:           1.2.8 (using 3.5.8, Gentoo)
Compiler:          Target: i686-pc-linux-gnu
OS:                Linux (i686) release 2.6.23-gentoo

As I use a lot of adblock filters in Konqueror I thought that filters are global for every KHTML instance in KDE. Unfortunately Akregator seems to disable/not enable this function when rendering full article using KHTML.
Comment 1 xdmx 2009-02-27 13:03:25 UTC
up for this wish.. it should block both when the full article is loaded and also when is just the summary
Comment 2 Sergei Andreev 2009-04-19 11:12:39 UTC
*** This bug has been confirmed by popular vote. ***
Comment 3 Roberto 2009-09-23 08:55:46 UTC
Still exists on kde 4.3.2 !!
Comment 4 Christophe Marin 2010-09-26 17:38:02 UTC
*** Bug 203549 has been marked as a duplicate of this bug. ***
Comment 5 tnemeth 2010-10-29 13:47:06 UTC
Up for this whish too...
Comment 6 Thomas Tanghus 2011-11-17 08:31:49 UTC
And now we are at 4.7.3...
Comment 7 Mathias Dietrich 2012-01-26 21:25:16 UTC
This bug still exists under KDE 4.8 for me. Even after enabling a number of blocklists in Konqueror.
Comment 8 nulll 2012-05-08 12:08:51 UTC
KDE 4.8.2
rekonq 0.9.1
Kubuntu 12.04
konqueror is no longer installed by default

I configured adblock on rekonq but akregator seems to ignore it.

An integration between akregator and adblock filters would be a great feature
Comment 9 l33tmmx 2012-05-17 15:10:45 UTC
+1 for this (lack of) feature, too!!!

I've been using Liferea until now, but because it crashes way too often to my liking, I wanted to switch to Akregator. But because of lack of any working adblock in Akregator, reading the feeds becomes a pain. Sadly, I think I have to stick with Liferea until this is fixed...

KDE 4.8.3 on Gentoo
Comment 10 nulll 2012-05-17 15:29:31 UTC
The bug was reported 4 years ago (2008) I hope that soon or late it will be checked...
Comment 11 Roberto 2012-05-17 15:42:41 UTC
meanwhile, it's three years that I use google-reader...
Comment 12 tnemeth 2012-05-18 07:33:41 UTC
(In reply to comment #9)
> I've been using Liferea until now, but because it crashes way too often to
> my liking, I wanted to switch to Akregator. But because of lack of any
> working adblock in Akregator, reading the feeds becomes a pain. Sadly, I
> think I have to stick with Liferea until this is fixed...

    RSSOwl seems to fit for the task, too...
Comment 13 Martin 2013-05-09 11:47:22 UTC
This is still valid.
Comment 14 Bugs.kde.org 2015-01-11 09:41:19 UTC
Is there any posibility to avoid ads?
Comment 15 okgomdjgbmoij 2015-12-09 00:10:48 UTC
It would be nice to implement that. Including blocking tracking crap.
Both for the summary and the full article.
Comment 16 okgomdjgbmoij 2015-12-09 23:24:20 UTC
beh, this is actually implemented, but the configuration part is a bit sloppy.
You have to activate and configure adblocking from ....inside konqueror
The config from rekonq is ignored.
If this can be configured from system settings, it's not obvious.

But of course your distribution may have installed just firefox....
All this is valid in KDE4, i don't know about plasma5.
If some one can confirm this for plasma5?

This should have been marked as implemented.
Comment 17 Denis Kurz 2017-06-23 20:20:34 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 18 Denis Kurz 2018-02-01 09:45:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.