The documentation on how to install the module should be changed, and it should report to move the robots.txt file from the root Drupal directory to the module directory. In this way, the user would have a recent robots.txt file he can then change.

Comments

hass’s picture

hass commented
Status: Active » Closed (won't fix)

Hm... I'd like more to keep the modules robots.txt file up to date. It's better if people won't start copy any files from core to modules and so... not the best usability and may overwrite files that shouldn't be overwritten. Changes on the core robots.txt are really rare, but I see the point if we talk about D 6.8... we should package a new release soon.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Still, the module doesn't work if there is a file which is named like the URL to which the module callback replies to.

hass’s picture

hass commented

Should we really stop the installation on modules page with hook_requirement() if the robots.txt file in root exists? This would be a hard action...

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I didn't say that.
I just said that maybe it would be preferable to instruct the user to move the robots.txt file into the module directory.
In that way, the file would be moved, and not deleted (that would be useful when the user wants to uninstall the module). As the module cannot clearly function with the file being present, it is better to instruct the user to move the file, otherwise he could even delete it.