Make phpinfo()/MySQL info links more obvious

+1 for this. I missed them too, and create a phpinfo.php when needed.

I found those links quite by accident some time ago -- or actually, now that I think about it, I think I may have heard chx make some comment in #drupal about the built-in phpinfo() and went looking for it.

The only small gripe I have with putting additional text here -- and it is only a very very small gripe -- is that people sometimes copy-and-paste the info in this table into various posts, and and additional text would then be in the middle of that. We even have "It may be useful to copy and paste this information into support requests filed on drupal.org's support forums and project issue queues." at the top of that page.

@keith: I understand that gripe, but it's also common practice to include an "ops" column for things like this, as well as "run cron manually", etc.

@angie: I found it only after I added similar functionality to Sitedoc... ;-)

++
imho phpinfo deserves it's own menu entry but I've heard devel has something like that. Gotta check it out... but more severe is that the phpinfo call does exclude a lot of useful information because it is called with INFO_GENERAL | INFO_CONFIGURATION instead of INFO_ALL...

Here's a patch that implements more visible "more information" links.

I always forget these are there, so +1 to making them more obvious. I'm wondering if the PHP link should mention phpinfo() specifically to make it really obvious where it goes - otherwise it could look like "more information about PHP 5.2.1. Maybe.

Patch has a commented line in it which needs taking out.

This one removes the commented line.

Note that there are some minor code style violations in the patch (spacing around concatenation operators and string literals).

This corrects the spacing around the concatenators and strings.

Have we settled on the wording for this? The patch more or less implements webchick's proposed wording (as seen in the screengrab at http://drupal.org/files/issues/status_more_links.png), which is good enough for me.

works for me

Be carefull. We have to check if phpinfo is disabled via the php.ini
maybe function_exists would help. Ill test it

@Zothos, that's a really good point. This patch tests for that and displays a message if phpinfo() is disabled. It's a REQUIREMENTS_INFO message instead of a REQUIREMENTS_WARNING so that it won't appear during installation.

I also added a handbook page at http://drupal.org/node/243993 that explains why phpinfo() may be disabled (and what to do about it) and added a link to it in the message.

Patch #13 no longer applies.

I'd like to see this get fixed quickly, can somebody reroll please

database stuff isn't on status report any more, so I've rerolled with just the phpinfo() additions

No: "} else {" - coding standards violation.

else fixed

Slight rewording making it a bit shorter:
"has been disabled" -> "is disabled"
Don't use please (http://drupal.org/node/501452) and put the main message (the handbook link) first:
Read the handbook page for more information.

I know it's not strictly belongs this patch but if you are meddling with this, could you please save phpversion into a variable and use it throughout? It's an eyesore to see so many needless function calls. (There is at least one after the block of code you use)

+1 Why not make it a global so everyone can access it?

Making it a global seems like overkill to me, but I've variablised it locally in the attached patch

Looks good!