Use of undefined constant STDIN - assumed 'STDIN' in C:\wamp\www\study\sayHello.php on line 5

Question

I want to Learn php & mySQL and I purchased a book (php&mySql: the missing manuals 2edition)

I installed Wampserver2.4 on win8 64bit machine.

Server Configuration

Apache Version : 2.4.4
PHP Version : 5.4.12

in first lesson i got this error :(

Notice: Use of undefined constant STDIN - assumed 'STDIN' in C:\wamp\www\study\sayHello.php on line 5

this is the php code on file "sayHello.php"

<?php

echo "Hello there. So I hear you're learning to be a PHP programmer!\n";
echo "Why don't you type in your name for me:\n";
$name = trim(fgets(STDIN));

echo "\nThanks, " . $name . ", it's really nice to meet you.\n\n";

?>

Answer 1

Just define STDIN constant at top of your file,

define('STDIN',fopen("php://stdin","r"));

Answer 2

when you are trying to run migration form a PHP file using

Artisan::call('migrate');

seems that's time also produce these type of error. For solve this problem you can simple replace your code with

Artisan::call('migrate', ['--force' => true ])

Make sure you use --force flag if you are in production.

Answer 3

Explanation

Only the CLI (command line) SAPI defines I/O constants such as STDIN, STDOUT, and STDERR, purely for convenience in that environment.

---

Solution

As stated in other answers, you can simply define these constants in your PHP code. You can also check defined() to avoid errors when invoked via CLI. For example:

<?php

if (!defined('STDIN')) {
  define('STDIN', fopen('php://stdin', 'r'));
}

However, keep in mind that php://stdin may not work the way you expect in a non-CLI SAPI, such as Apache or FPM. For example, to access the raw POST body when executed via FPM, you would use php://input instead.

---

More Info

PHP has many different SAPI (Server Application Programming Interface), that allow you to execute PHP code in various environments such as your Web server, email server, or the command line (CLI). Examples include:

• CGI
• FPM
• Milter (email filters)
• Apache
• etc

Each SAPI may have slightly different initial conditions and behavior. Some other differences between the CLI SAPI and other SAPIs include:

• header() has no effect.
• Some ini settings such as html_errors and output_buffering have different default values (more appropriate for the CLI).
• Does not change the current working directory (CWD) to the script you executed.