Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Here's a patch that I've found helps the usability for some of my modules. Adds a warning message on admin/settings/robotstxt if there are warnings from robotstxt that would be shown in the status reports. Users don't necessarily always check the status reports for new modules, but we increase the chance for them to see a problem if they view a module configuration page.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | 0-robotstxt-show-potential-issues-2-D6.patch | 2.56 KB | dave reid |
| #1 | drupal-robotstxt-warnings.png | 61.43 KB | dave reid |
| 0-robotstxt-show-potential-issues-D6.patch | 2.46 KB | dave reid |
Comments
Comment #1
dave reidScreenshot for review.
Comment #2
dave reidI guess an alternative to this is to just provide a link the the admin/reports/status instead of showing the actual messages, much like the error message you see at /admin if there is something wrong.
Comment #3
hass commentedWe install the standard robots.txt file via hook_install, not on page load (tooooo slow as said in the other case). Why don't you like to re-use core functionality (status page)? I'm not a friend of re-inventing a new wheel.
Comment #4
hass commentedA
if (file_exists('./robots.txt')) { drupal_set_message('foo'); }on the robots.txt config page is really enough. Do not overcomplicate this, please.Comment #5
hass commented