robot.txt ?

[babis1]

is missing the robot.txt or i have lost it from the installation ?

[speck]

is missing 

[rentasite]

Rev1311 ? 

[webgift]

 Files robots.txt and favicon.ico do not exist in Elxis 4.0 release but we recommend you to put them there in order to avoid error notices by robots and browsers asking them.

[babis1]

so what we have to disallow except estia and includes ? (i mean by default) and what about with repository folder ?

[rentasite]

Files robots.txt and favicon.ico do not exist in Elxis 4.0 release but we recommend you to put them there in order to avoid error notices by robots and browsers asking them.

favicon.ico exists in /media/images

[datahell]

We haven't included a robots.txt and a favicon.ico in Elxis root as these files usually exist in the web root folder and we didn't wanted users to accidentally overwrite them during Elxis installation.

Elxis has 2 favicons (ico and png) in media/images/ folder.
Elxis search if there is a favicon.ico in Elxis root folder, if yes it uses this one.
If no, searches for a favicon.png in Elxis root folder, if yes it uses this one.
If no, searches for a favicon.ico in Elxis media/images/ folder, if yes it uses this one.
If no, searches for a favicon.png in Elxis media/images/ folder, if yes it uses this one.

So favico is always correct in Elxis head section. The error messages you get in Elxis error log is because on some requests the client requests for a favicon.ico in the default position (root folder). On other site's, CMSs, past elxis versions, you may had the same warning but you have never noticed it because no one checks his site's error logs...  In Elxis 4.x error logs is very easy to watch this is why you noticed this issue. The scope of Elxis error log is to help you keep a site producing zero errors and warnings.

The robots.txt can contain something like this:

Code: [Select]

User-agent: *
Disallow: /includes/libraries
Or, better, be empty  (there is no need to disallow something in Elxis 4.x as everything is locked)
Only include a sitemap if you have one.

Security tip
Hackers use to read the robots.txt file to get an idea of site's file structure or internal/private linking. So by disallowing a secret path, eg. /secrets you already told them where you keep your secrets... Got it?
So if, for example, you have renamed the administrator folder (estia) to secretadmin and put it in robots.txt in order to "protect it" you actually told the whole world where is your administration interface...

Code: [Select]

User-agent: *
Disallow: /secretadmin
A real example (http://www.newsbeast.gr/robots.txt):
User-agent: *
Disallow: /netvolution/
Disallow: /Themes/
Disallow: /Temp/
Disallow: *pg=
Disallow: *pbid
Disallow: *search
Disallow: *Gid=
Disallow: *gid=
Disallow: *pbid
Disallow: *tagid=
Disallow: /my-newsbeast/

An other one (http://www.in.gr/robots.txt):
User-agent: *
Disallow: /netvolution/
Disallow: /Themes/
Disallow: /Temp/
Disallow: /z_   # prevent indexing of the search catalog!

Sitemap: /sitemap.aspx

An other one (http://www.protothema.gr/robots.txt)
User-agent: *
Disallow: /netvolution/
Disallow: /Themes/
Disallow: /Temp/
Disallow: /z_   # prevent indexing of the search catalog!

Sitemap: /sitemap.aspx

An easy conclusion: all these sites use the same CMS running .net framework 2.0 (netvolution)
And here is a "hidden" login page... http://www.newsbeast.gr/netvolution/ and an other one (which also tell us the exact version: Netvolution Enterprise v3.9.1.13838)

[babis1]

Or, better, be empty  (there is no need to disallow something in Elxis 4.x as everything is locked)

this is better