[Sequal7]

I doubt there is any reason to be concerned, since all your creating is referral links to the other "affiliate schemes" you have. If someone clicks the link and your referral is incorrect than it will just load their default sign up page. They don't need permissions to be set.
You can check your referral links to make sure they work after you set them, that would be the smart thing to do.

About server permissions, scripts uploaded to your server need to be set when they are in the servers folder. If you want to avoid this you could set the folders value (NOT THE ROOT FOLDER) 777 or 667 then each file you upload the permissions should be inherent to the folders permissions.

Don't get too much into the permissions, it is only for scripts that need to write to files on the server, or execute files, not for the other files. You may need to chmod 1 or two script files and that is all.

[tomdkat]

Originally Posted by howard.a.s

I downloaded Core FTP and used it to FTP into my 110mb.com account. Unfortunately, when I right-clicked on SETPERMISSIONS, and although more options were available in the drop-down list, CH-MOD/Set Permissions still wasn't offered.

Ok, which options were offered?

After a bit of a rethink I tried using SmartFTP again, and when right-clicking on SETPERMISSIONS inside the CGI-BIN folder, the drop-down list offered me the option to CH-MOD/Set Permissions. BINGO!

Great!

Next, and as shown in the video, I went to the browser bar and entered the address of the website folder that I'm working on, followed by /cgi-bin/setpermissions.sh, which, according to the video, should then take me to a screen saying 'permissions have been set'.

Unfortunately, it took me to a screen saying that config.php required adjustment. The on-screen message told me what three numerals to enter into config.php.

Did it say the permissions of config.php needed adjustment or a number need to be put inside config.php?

This time I didn't get an error message, nor did I get the correct screen saying permissions have been set. Instead, a download window appeared on screen, inviting me to open/save/cancel, or search for a suitable program to open this file/page with.

You were prompted to download setpermissions.sh? If so, that means something is wrong on the server side. When you point your browser at [website domain]/cgi-bin/setpermissions.sh, that script should actually execute on the server. I'll watch more of the video to see what is supposed to happen.

EDIT: Ok, I watched more of the video and have a better understanding of what you're talking about. You probably had to update the permissions of config.php when the setpermissions script ran the first time. Please post which file you were prompted to download when you ran setpermissions the second time.

Peace...

[howard.a.s]

As you read, Smart FTP does allow me to set permissions from the drop-down list, so that was O.K. I also downloaded and installed Filezilla, as someone suggested, but haven't tried it out yet.

When the message came up on screen, it said something like the wrong number was entered in config.php, and it told me what number I should enter. So, off I went, found the file, entered the suggested number and when I went back to the first screen the error message had gone and I was prompted to download the set permissions file, instead of seeing the message (as described in the video) that permissions had been set. Anyway, I was then allowed to access the admin area, which I did. So, from this, I assumed that everything was O.K? But wasn't sure!

Basically, this uncertainty over not seeing exactly the same messages and screens as shown in the video was what prompted me to ask the most recent questions, as I really just wanted to understand whether permissions were just something that stopped the entire site from being accepted by the server, or whether incorrect permissions would likely affect the site in other ways. For instance, stop adsense ads from working, despite my adsense I.D being entered correctly.

Moving on, I also asked about some other sites that I have, in which my adsense I.D had to be entered in files contained within a folder called 'includes'. The files have a .ini extension (if my memory serves me correctly). Details that I followed when adding my I.D into these files said to do this before upload. My question is, would this have worked?

I mean, I know that my adsense pub I.D is saved in each relevant file, but would this information be 'seen' by the server, because I didn't make those changes when the files were actually on the server? Or does this only apply to files with the .php extension?

Here's what also worries me. I have another existing website that, since last autumn has had three adsense ad units placed on its homepage. O.K, so the site ain't Amazon, but it does get traffic and yet, according to my Google account, not one click has been registered, not one penny earned. Apart from this site, I have lots of other pages with adsense units installed and not one has registered a single click in months. Strange?

Again, according to my Google account I have no blocked urls, so I must be staying within the rules, which is always my intention.

So, why no clicks?

Guess I'm paranoid, but there seems little point in uploading adsense units if they aren't going to prove even slightly worthwhile.

What I don't get is why Google don't have a system whereby I could click on my own ads just to make sure they work. Obviously this is not allowed, but it would be good to remove the uncertainty of not knowing.

Any feedback gratefully received.

[howard.a.s]

Further to your question:

Please post which file you were prompted to download when you ran setpermissions the second time.

Firstly, after setpermissions was adjusted to the number shown in the video, I was then instructed to set the config.php file to 666 (think it was previously set to 5 something).

When going to cgi-bin/setpermissions using the browser (as shown in the video), the prompt is to download setpermissions.sh, which it says is an unknown filetype - 704 bytes.

Hope that helps.

[tomdkat]

Originally Posted by howard.a.s

Firstly, after setpermissions was adjusted to the number shown in the video, I was then instructed to set the config.php file to 666 (think it was previously set to 5 something).

Ok, that's setting the permissions of config.php.

When going to cgi-bin/setpermissions using the browser (as shown in the video), the prompt is to download setpermissions.sh, which it says is an unknown filetype - 704 bytes.

Hope that helps.

Ok, this is not good. That means the server isn't running the script but actually trying to send the script file itself to your computer. Since you actually ran setpermissions successfully once already, there is a chance it did everything it needed to do, outside of you having to update the permissions on config.php manually. If this is the case, you shouldn't need to run setpermissions again.

If the site does what you want/need, you're probably in good shape.

Peace...

[tomdkat]

Originally Posted by howard.a.s

As you read, Smart FTP does allow me to set permissions from the drop-down list, so that was O.K. I also downloaded and installed Filezilla, as someone suggested, but haven't tried it out yet.

Yep, but I was asking which menu options CoreFTP provided to you when you right-clicked on setpermissions.sh.

When the message came up on screen, it said something like the wrong number was entered in config.php, and it told me what number I should enter. So, off I went, found the file, entered the suggested number and when I went back to the first screen the error message had gone and I was prompted to download the set permissions file, instead of seeing the message (as described in the video) that permissions had been set. Anyway, I was then allowed to access the admin area, which I did. So, from this, I assumed that everything was O.K? But wasn't sure!

I'm not sure either. The downloading of setpermissions.sh isn't a good sign, but if the site generally works you might be ok.

Basically, this uncertainty over not seeing exactly the same messages and screens as shown in the video was what prompted me to ask the most recent questions, as I really just wanted to understand whether permissions were just something that stopped the entire site from being accepted by the server, or whether incorrect permissions would likely affect the site in other ways. For instance, stop adsense ads from working, despite my adsense I.D being entered correctly.

The impact of correct file permissions will vary upon the nature of the files in question and how they are used. For security reasons, a script-based web application (like a PHP web mail client like SquirrelMail) will refuse to run if certain config files are present or have incorrect permissions. This is to prevent hackers from getting access to your private config data and settings and exploiting your site. That's just one example. Obviously, what you're installing wanted certain permissions set so it could function correctly (or at least as intended) but we're not 100% sure if that's the case right now. If the site seems to behave the way you want it to, chances are all is well even with the setpermissions.sh downloading issue.

Moving on, I also asked about some other sites that I have, in which my adsense I.D had to be entered in files contained within a folder called 'includes'. The files have a .ini extension (if my memory serves me correctly). Details that I followed when adding my I.D into these files said to do this before upload. My question is, would this have worked?

These kinds of changes should be down before uploading the files since you won't have login access to the server to update them on the server. These kinds of changes are different than setting server-side file permissions, which can only be done after the files have been uploaded to the server.

Here's what also worries me. I have another existing website that, since last autumn has had three adsense ad units placed on its homepage. O.K, so the site ain't Amazon, but it does get traffic and yet, according to my Google account, not one click has been registered, not one penny earned. Apart from this site, I have lots of other pages with adsense units installed and not one has registered a single click in months. Strange?

Not necessarily. Just because an ad is on your site that doesn't mean someone will click it. Also, some people might have ad blockers installed in their browsers which might be blocking your adsense ads. If you give me the URL of a site that isn't getting any adsense clicks, I'll click and ad and you can see if it was properly registered with Google.

What I don't get is why Google don't have a system whereby I could click on my own ads just to make sure they work. Obviously this is not allowed, but it would be good to remove the uncertainty of not knowing.

I guess it's just the nature of the "beast", how the ads work, etc.

Peace...