644 should be fine. What are the permissions of the directory '/rellect/AdblockDetector' and '/rellect'?Here is a screen shot of my cpanel.
View attachment 87998
These are located at: board/js/rellect/AdblockDetector
What type of permissions should those files have? currently they have 644
Change to 755700 for both.....i'm guessing 744 is what it should be? (I really thought I changed that on one of my previous install attempts.)
Are the file sizes correct? I have very crappy internet here.
Click on the rating stars in here (the Information block) and you'll get a field to write a review. Thanks!SOB.......I changed the rellect to 755 last install....forgot the AdblockDetector. Awesome Dev, where do I leave a review?
I have very crappy internet here.
Suggestion:
IMHO, it would be great, if it is possible to be able to see statistics of people who deactivates their adblocker and continue to site. Also, people who doesn't and leave the site.![]()
Tracking of adblock users is planned for v2 of the addon.Put some logs of people that are detected as using adblock and ones without and you will get a definite sale from me.
When is V2 planned to be released?Tracking of adblock users is planned for v2 of the addon.![]()
May take few months. No specific date at the moment.When is V2 planned to be released?![]()
I will add the browser to the tracking information, but creating a guide for each browser is not very practical, mainly because there are few adblock extensions, and each one has a different UI.Another thing that would be great would be for the addon to determine which browser the visitor is using and then give a link on how to stop the adblock for that browser. Is that possible?
The adblocker warning popups seems to appear momentarily for me from time to time. It appears to happen more often when I click somewhere before the page is totally done loading. And no, I'm not using an adblocker. This is in Firefox on a mac.
Send me a link to your forum please, I'll take a look.Got this today from one of my active visitors...
Oh so yea, that could be the reason. Pretty sure the code to handle this was added in 1.4v1.3.1
Will upgrade and re-test. PM'ing you the link.
We use essential cookies to make this site work, and optional cookies to enhance your experience.