Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
system.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Apr 2015 at 10:17 UTC
Updated:
21 Apr 2015 at 07:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
willzyx commentedComment #2
dom. commentedHi !
- patch review for Drupal standard
- patch manually applied and checked
Therefore, patch #1 is RTBC+1 !
However I would suggest the following, thus not applying the RTBC tag. If you don't agree with the following, please apply the RTBC tag since #1 is ok :
- add "visit" in the last sentence since otherwise it is a fragment (looks weird that there are no verb, but I'm not native english so I'm probably wrong.)
For more information, visit <a href="@phpinfo">Enabling and disabling phpinfo()</a> handbook page.- remove the empty lign before return statement.
Comment #3
andypostNot sure that the text makes sense, you suggest to revert security setting on server to enable
phpinfo()that disabled for reason.The link to d.o page makes a lot of sense, so I think text should be like.
Suppose
The phpinfo() function has been disabled for security reasons. For more info....Comment #4
willzyx commented@Dom.
- it makes sense
- on coding standards there is no reference of the standard to follow for this thing. it's just a matter of preference. For me the change you made is fine
@andypost
It's the same sentence used in the status report page (see
system_requirements()); we suggest to revert setting on server to enable phpinfo() IF you want to see your server's phpinfo() information.However, the requested change makes sense
Comment #5
dom. commentedRTBC+1
Comment #6
webchickHuh. Had no idea this was an option. You learn something new every day. :)
Can't envision a useful way to automated test this, so...
Committed and pushed to 8.0.x. Thanks!