Contact me and explain problem, but first of all make sure :

• You've done all update, may be your bug is already fixed
• Take a look at FAQ and Troubleshooting
• Please, give me as much details as you can.

Thank you.

User permissions are a fundamental aspect of UNIX systems and are designed to ensure the security and integrity of the system. Essentially, user permissions determine who can access and manipulate files and directories on a UNIX system.

UNIX systems are typically multi-user environments, where many users can access the system simultaneously. As a result, it is important to ensure that each user can only access the files and directories that they are authorized to use. This is achieved through the use of user permissions, which allow system administrators to specify the access rights of each user.

By carefully controlling user permissions, system administrators can limit the risk of unauthorized access or modification of critical system files, as well as prevent accidental deletion or modification of important data. User permissions also help to ensure that different users can work together on a system without interfering with each other's work.

Overall, user permissions are a critical aspect of UNIX systems, allowing for fine-grained control over access to system resources and ensuring the security and integrity of the system.

One of the reasons why Apache should not be able to modify user files is that it can introduce security risks and potentially compromise the entire system. Apache is a web server software that runs on UNIX systems and serves web pages to users over the internet. In order to run effectively, Apache requires read access to files that contain the web content, such as HTML, CSS, and JavaScript files.

However, allowing Apache to modify user files can potentially expose these files to malicious attacks. If an attacker were able to gain access to Apache's user account, they would have the ability to modify any user files that Apache has access to. This could allow them to inject malicious code into the web pages served by the web server, potentially compromising the security of the entire system.

Check incoming hits

Edit common.php and add the following code

$f = fopen('path_to/log.txt', a);
fputs($f, date('H:i') . " {$_SERVER["HTTP_REFERER"]} \n");
fclose($f);

create file log.txt and chmod 666 it

As you can see the script is really easy, there's nowhere to make an error

Compare numbers from the log file with the script

Check clicks

• create log file and chmod 666 it
• add into common.php

if ($_COOKIE['from'] == 'trader.com') {
	$f = fopen('path_to_/log.txt', a);
	fputs($f, date('H:i') . " {$_SERVER["REMOTE_ADDR"]} \n");
	fclose($f);
}

where trader.com - traders you want to check

HTTP protocol (this is how browser communicates with remote server) consists of 2 parts: headers and body. Body is what you actually see in your browser, while headers hold some system information.

Script has special debug mode to see what it does.

1. set Settings -Cjsettings - add debug info = yes, wait a minute
2. Get FireFox browser and add extension (Tools-addons) Live HTTP Headers
3. Click on any link and take a look at headers

Usually those headers are self explained , I just have to notice that something link

Location: http://site.com/

is a redirect.

Script requires free PHP optimizer SourceGuardian. Installation: /scj/ixed/howto-install.php Website: sourceguardian.com

1. make sure crontab job is setup (make a look at Main tab in admin)
2. file common.php contains a path to scj folder. If you moved script from one host to another - make sure path in that file is right.