ob_get_clean

(PHP 4 >= 4.3.0, PHP 5, PHP 7, PHP 8)

ob_get_clean — Geçerli çıktı tamponun içeriğini döndürüp tamponu siler

Açıklama

ob_get_clean(): string|false

Geçerli çıktı tamponun içeriğini döndürüp tamponu siler.

ob_get_clean() esasen ob_get_contents() ve ob_end_clean() işlevlerini çağırır.

Çıktı tamponu ob_start() tarafından PHP_OUTPUT_HANDLER_CLEANABLE ve PHP_OUTPUT_HANDLER_REMOVABLE ile başlatılmalıdır. Aksi takdirde ob_get_clean() çalışmaz.

Bağımsız Değişkenler

Bu işlevin bağımsız değişkeni yoktur.

Dönen Değerler

Çıktı tamponlaması etkin değilse false, aksi takdirde çıktı tamponunun içeriğini döndürür.

Örnekler

Örnek 1 - Basit bir ob_get_clean() örneği

<?php

ob_start();

echo "Hello World";

$out = ob_get_clean();
$out = strtolower($out);

var_dump($out);
?>

Yukarıdaki örneğin çıktısı:


string(11) "hello world"

Ayrıca Bakınız

ob_get_contents() - Çıktı tamponunun içeriği ile döner
ob_start() - Çıktı tamponlamasını başlatır

add a note

User Contributed Notes 6 notes

down

geo dot artemenko at gmail dot com ¶

10 years ago


The definition should mention that the function also "turns off output buffering", not just cleans it.

down

steven at bielik dot com ¶

13 years ago


Also, don't forget that you will need to ob_start() again for any successive calls:



<?php

ob_start();

echo "1";

$content = ob_get_clean();



ob_start(); // This is NECESSARY for the next ob_get_clean() to work as intended.

echo "2";

$content .= ob_get_clean();



echo $content;

?>



Output: 12



Without the second ob_start(), the output is 21 ...

down

paul+phpnet at earth2me dot com ¶

11 years ago


Keep in mind that output may be buffered by default, depending on how you are running PHP (CGI, CLI, etc.).   You can use ob_get_level() to determine if an output buffer has already been started.  On most web servers I've used, output buffering is already one level deep before my scripts start running.

You should only end as many output buffers as you start.  Assuming that your buffer is always the first buffer, or otherwise closing pre-existing buffers, could lead to problems.  In PHP 5.5, you can ensure that output buffers are ended properly using a try-finally block.

Something like this is almost guaranteed to break stuff:

<?php
// Don't ever do this!
while (ob_get_level() > 1)
{
    ob_end_flush();
}

$content = ob_get_clean();
?>

The problem is that number, "1".  Using a fixed number there is asking for trouble.  Instead, use ob_get_level() to get the number of output buffers applied when your code starts, and return to that number, if you really must use an unknown number of output buffers:

<?php
ob_start();
$saved_ob_level = ob_get_level();

// Do stuff here:
run_something();

// If you really must close all of your output buffers except one, this'll do it:
while (ob_get_level() > $start_ob_level)
{
    ob_end_flush();
}

// And now, the final output buffer that belongs to us:
$content = ob_get_clean();
?>

down

-1

sergei dot solomonov at gmail dot com ¶

12 years ago


<?php

ob_start();

echo "1";

$content = ob_get_clean();



echo "2";

$content .= ob_get_clean();



echo $content;

?>



This script outputs 21 in CLI mode and 12 otherwise (under my apache and nginx)

down

-4

Peter Smartt ¶

7 years ago


I was trying to debug my code using error_log() and I discovered that ob_get_clean() also truncates the error_log() buffer right in the middle of its output, and well as the output buffer which it is supposed to truncate.  If you are using error_log(), use ob_get_contents() and ob_end_clean() instead of ob_get_clean().

down

-44

ludvig dot ericson at gmail dot com ¶

19 years ago


Notice that the function beneath does not catch errors, so throw in an @ before those ob_* calls

add a note