https block by click


einherz

Recommended Posts

for what? i did it yet(del from global), and for pirate work just *exoclick*(in rules), and now pirate stoped redirect to https from http so must be admuncher block everything first, i stay in pirate rules *exoclick* because never know, when it will force redirect to https again

so with http work admuncher, but if this again force redirect to https, *exoclick* in rules block all banners there

p.s. must be my first post some confuse+n+frustrate, i meant need for rebuild maxthon "block by click", not me, because i did yet(write needed rules)

Link to comment
Share on other sites

I think I understand what you're saying now.

Using the "block ads by click" option to select ads isn't working. Nothing gets added to the rules list and none of the ads that are supposed to be blocked actually get blocked.

Adding rules manually as noted above works fine. But with that said, I removed all my added rules including extras in the global list, and AdHunter still blocked every ad?!

EDIT: seems like it's an issue with that site only. Tried on a few others and it works fine.

Link to comment
Share on other sites

global rules i meant in my rules sections, in that section global rules is empty, i didn't touch rules what was in maxt

but you can manualy add *555* to 123.net rules, thats ithon as defoult, block by click do strange thing - create rules for add's page forexample if you serf www.123.net and in this site adds with www.555.org, when you block by click, hunter made rule for www.555.org page, not for www.123.net

p.s. it's nonesens - maxthon forum got problem* with maxthon but not for chrome

*glitches sending or edit post

Link to comment
Share on other sites

when you block by click, hunter made rule for www.555.org page, not for www.123.netDo you mean the rule created is something like www.555.org/ad/* - which would make sense if that is the link to where the ad is from. Or is it that the rule is listed under the site www.555.org - which wouldn't make sense unless the site was redirected somehow?!

A screenshot of what is happening might help a lot here.

Link to comment
Share on other sites

yes, block by click made rules for site from adds are

you searf xxx.com adds got web address yyy.org/*.* and maxthon's hunter made rules for yyy.org, so you have to crate your own rules for xxx.com and put in this rules *yyy*

as you can to see i put *exoclick* for pirate, but when i use block by click in pirate site, hunter create page rules for exoclick.(don't remember domen) but not for pirate

as i say above, now tpb no redirect to https, so in http banners rules block ok by muncher, for https you can to see what rules was added manually

post-6750467-14315121286252_thumb.jpg

Link to comment
Share on other sites

I'm sorry, but I feel more confused with every post. I'm not really sure what the problem is?

As I pointed out above it seems block by click doesn't work on this site, BUT for me at least, all the ads on the page are blocked using the standard global block list, meaning adding extra rules isn't required. The only extra one would be *poptest.js to stop the popup.

Screenshots of every point you are trying to make might help out. As the one above just shows that you have added one rule to that domain (which I already understood). I don't understand what happens when you use block by click, or where exactly these rules are being created.

Link to comment
Share on other sites

if http don't reopen as https i don't see any banners, may be hunter block it may be muncher, i don't know, when site redirect to https(what no happens 2 days yet) block by click create wrong rules for page where baners from, but not for site where banners live

first screenshot was after copypast your settings to "my rules>global rules", remove it

second screenshot - my rule for site, what i did manualy, because block by click do it in wrong place - create rules for web page were banners from, but not where banners add

Link to comment
Share on other sites

Had another look... a finally I understand what you're getting at (i hope). I never noticed the exoclick.com domain added to my list earlier.

So here is the explanation as far as I can tell. I'm not 100% about it, but makes sense to me.

On TPB the ads are coded as iframes, which basically means the site is showing a webpage within a webpage - so as far as Maxthon is concerned the page the ad belongs to is exoclick.com, not TPB.com.

Apart from adding rules manually for the correct domain or having global rules that work, there's no way block by click can do anything about it. I'm not sure what/how the dev's can work around that? I thought it would have used the domain in the address bar, but it seems it gets the address from elsewhere. In this case it's the page that is actually hosting the banner via the iframe.

I don't believe this is a bug,

Link to comment
Share on other sites

yes is bug, and devs could repair it just as you say, add rules only from address bar, not from banners which was clicked for bloking, exoclick could be any other site where banners from, banners adds some time depending of your ip, so if your ip will from usa it could be not exoclick as your ip will from australia, but my israely ip catch on tpb exoclick only if http redirect https, so if you have not redirect to https, you can never see any banners on tpb just with defoult maxthon rules or(and) with 3rd party addblocker

so with diferent way you could got different behavior

any way if i click for block and in my rules add page of banner's site with rules, but rules of address bar site where i click for block stay empty, so this is bug

Link to comment
Share on other sites

Hi Guys,

Thank you very much for your time and effort you put in the explanation of this problem.

I couldn't get your problem at the begging but now i get what you meant.

Let's say we have 10.0.1.87 in http://10.0.1.87/main.html

Using "Block by click" function and click on the image, the created rule http://bbs.maxthon.cn/static/image/common/* is saved under 127.0.0.1 instead of 10.0.187.:(

I just reported this issue to our development team and i hope to be fixed in the future versions.

Thanks again for your support!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.