Arrow Trader 5

Installation Guides
Admin Modules
References

Arrow Trader Core

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V2

Installation Guides
Admin Modules
References

Arrow Trader eXtreme V1

Installation Guides
Admin Modules
References

Arrow Trader Lite 3

Installation Guides
Admin Modules
References

Q&A

Getting started

Search

This is the username + password combo that is used to login. Whenever a surfer clicks more than the Max amount of clicks, the clicks will still be counted, but a trade will not receive extra credit for it. For example, if you set this limit to 10, and a surfer comes from a trade and clicks 100 times (either these are real clicks, or he's downloading your site and his site-sucker program hits every link), only the first 10 clicks will be counted as real ones and used to calculate the prod; the other 90 are ignored. This way ATX will not return more to a trade than what it's really worth. Trades in the watchlist do not receive any traffic. By setting a range of like 0 - 50, you can basically set a minimum size for trades. Any trade that is small than 50 hits will not receive hits back. There are a couple of exceptions to this. 1) Trades with a hourly force and a force time of more than 0 hours (a temporarily force) do receive traffic. 2) Trades with a high or extreme boost do receive traffic. Trades with a permanent force (force time of -1) do not receive traffic. The idea behind this is that you can give all your trades a force, but that you won't waste hits when a trade stops returning hits. Surfers that don't support cookies shouldn't be send to trades, because even though your trades will be able to see where the hit came from (you), any clicks generated by this surfer will not be counted as coming from you. As a result, your trade prod on your trades looks much lower than it is. A better idea is to send nocookie surfers to galleries so there's a good chance that a surfer will bookmark your site, and comes back later with cookies enabled. You can give noref traffic (bookmarkers for example) a different skim % than what the URL defines. You can give notrade traffic (hits coming from a domain that is not listed as a trade) a different skim % than what the URL defines. Once a surfer has visited all your active trades, but clicks a link that normally would send him to another trade, the exout module is loaded. You can select to send this surfer than to one specific url, or to galleries.

IP access masks Direct access to the ATX admin can be limited to certain IPs to secure the site against brute-force attacks designed to fetch the user + pass. Write down 1 IP per line. The IPs work as masks, so writing down 200.40 will allow access to any IP that starts with 200.40 If they know the user + pass of course. For added security fill out the masks and then set the file /cgi-bin/atx/d/uip to read-only (444) blocked referrer traffic When a surfer clicks a link that goes to /out.cgi, normally your own domain is set as the referring domain. If the http_referer field however is empty, ATX cannot tell where the hit came from, and worse, when this surfer would be redirected to a trade, your trade would not be able to tell that it came from you. So a blocked-ref hit sent to a trade is a hit wasted. See also the optimal settings guide rebuild & repair The ATX 1.2 database system is designed around the idea that every single minute the crontable runs a cronjob that updates the database. This way we were able to keep it incredibly fast, even when you have thousands of trades in your database and millions of hits. However, when a cron-run is missed - because the server was rebooting for example - the database goes out-of-sync and will not show the correct stats anymore. ATX can auto-detect instable crons and auto-repair the database. Set the rebuild module to 5) run when corrupted.