diff --git a/reference/outcontrol/functions/flush.xml b/reference/outcontrol/functions/flush.xml index 7540c42719..230b93742a 100644 --- a/reference/outcontrol/functions/flush.xml +++ b/reference/outcontrol/functions/flush.xml @@ -1,54 +1,54 @@ - + - - - flush - Flush the output buffer - - - Description - - voidflush - - - - Flushes the output buffers of PHP and whatever backend PHP is - using (CGI, a web server, etc). This effectively tries to push - all the output so far to the user's browser. - - - flush has no effect on the buffering - scheme of your web server or the browser on the client - side. - Thus you need to call both ob_flush and - flush to flush the output buffers. - - - Several servers, especially on Win32, will still buffer - the output from your script until it terminates before - transmitting the results to the browser. - - - Server modules for Apache like mod_gzip may do buffering of their own - that will cause flush to not result in data being - sent immediately to the client. - - - Even the browser may buffer its input before displaying it. - Netscape, for example, buffers text until it receives an - end-of-line or the beginning of a tag, and it won't render - tables until the </table> tag of the outermost table is - seen. - - - Some versions of Microsoft Internet Explorer will only start to display - the page after they have received 256 bytes of output, so you may need to - send extra whitespace before flushing to get those browsers to display the - page. - - - + + + flush + Flush the output buffer + + + Description + + voidflush + + + + Flushes the output buffers of PHP and whatever backend PHP is + using (CGI, a web server, etc). This effectively tries to push + all the output so far to the user's browser. + + + flush has no effect on the buffering + scheme of your web server or the browser on the client + side. + Thus you need to call both ob_flush and + flush to flush the output buffers. + + + Several servers, especially on Win32, will still buffer + the output from your script until it terminates before + transmitting the results to the browser. + + + Server modules for Apache like mod_gzip may do buffering of their own + that will cause flush to not result in data being + sent immediately to the client. + + + Even the browser may buffer its input before displaying it. + Netscape, for example, buffers text until it receives an + end-of-line or the beginning of a tag, and it won't render + tables until the </table> tag of the outermost table is + seen. + + + Some versions of Microsoft Internet Explorer will only start to display + the page after they have received 256 bytes of output, so you may need to + send extra whitespace before flushing to get those browsers to display the + page. + + + + - - - ob_clean - - Clean (erase) the output buffer - - - - Description - - voidob_clean - - - - This function discards the contents of the output buffer. - - - This function does not destroy the output buffer like - ob_end_clean does. - - - See also ob_flush, - ob_end_flush and - ob_end_clean. - - - + + + ob_clean + Clean (erase) the output buffer + + + Description + + voidob_clean + + + + This function discards the contents of the output buffer. + + + This function does not destroy the output buffer like + ob_end_clean does. + + + See also ob_flush, + ob_end_flush and + ob_end_clean. + + + + - - - ob_end_clean - - Clean (erase) the output buffer and turn off output buffering - - - - Description - - boolob_end_clean - - - - This function discards the contents of the topmost output buffer and - turns off this output buffering. If you want to further - process the buffer's contents you have to call - ob_get_contents before - ob_end_clean as the buffer contents are - discarded when ob_end_clean is called. - The function returns &true; when it successfully - discarded one buffer and &false; otherwise. Reasons for failure are first - that you called the function without an active buffer or that for some - reason a buffer could not be deleted (possible for special buffer). - - - The following example shows an easy way to get rid of all output buffers: - - - - <function>ob_end_clean</function> example - + + + ob_end_clean + Clean (erase) the output buffer and turn off output buffering + + + Description + + boolob_end_clean + + + + This function discards the contents of the topmost output buffer and + turns off this output buffering. If you want to further + process the buffer's contents you have to call + ob_get_contents before + ob_end_clean as the buffer contents are + discarded when ob_end_clean is called. + The function returns &true; when it successfully + discarded one buffer and &false; otherwise. Reasons for failure are first + that you called the function without an active buffer or that for some + reason a buffer could not be deleted (possible for special buffer). + + + The following example shows an easy way to get rid of all output buffers: + + + + <function>ob_end_clean</function> example + ]]> - - - - - - If the function fails it generates an E_NOTICE. - - - The boolean return value was added in PHP 4.2.0. - - - - See also ob_start, - ob_get_contents, and - ob_flush. - - - + + + + + + If the function fails it generates an E_NOTICE. + + + The boolean return value was added in PHP 4.2.0. + + + + See also ob_start, + ob_get_contents, and + ob_flush. + + + + - - - ob_end_flush - - Flush (send) the output buffer and turn off output buffering - - - - Description - - boolob_end_flush - - - - This function will send the contents of the topmost output buffer (if - any) and turn this output buffer off. If you want to further - process the buffer's contents you have to call - ob_get_contents before - ob_end_flush as the buffer contents are - discarded after ob_end_flush is called. - The function returns &true; when it successfully - discarded one buffer and &false; otherwise. Reasons for failure are first - that you called the function without an active buffer or that for some - reason a buffer could not be deleted (possible for special buffer). - - - - This function is similar to ob_get_flush, except - that ob_get_flush returns the buffer as a string. - - - - The following example shows an easy way to flush and end all output - buffers: - - - - <function>ob_end_flush</function> example - + + + ob_end_flush + Flush (send) the output buffer and turn off output buffering + + + Description + + boolob_end_flush + + + + This function will send the contents of the topmost output buffer (if + any) and turn this output buffer off. If you want to further + process the buffer's contents you have to call + ob_get_contents before + ob_end_flush as the buffer contents are + discarded after ob_end_flush is called. + The function returns &true; when it successfully + discarded one buffer and &false; otherwise. Reasons for failure are first + that you called the function without an active buffer or that for some + reason a buffer could not be deleted (possible for special buffer). + + + + This function is similar to ob_get_flush, except + that ob_get_flush returns the buffer as a string. + + + + The following example shows an easy way to flush and end all output + buffers: + + + + <function>ob_end_flush</function> example + ]]> - - - - - - If the function fails it generates an E_NOTICE. - - - The boolean return value was added in PHP 4.2.0. - - - - See also ob_start, - ob_get_contents, - ob_get_flush, - ob_flush and - ob_end_clean. - - - + + + + + + If the function fails it generates an E_NOTICE. + + + The boolean return value was added in PHP 4.2.0. + + + + See also ob_start, + ob_get_contents, + ob_get_flush, + ob_flush and + ob_end_clean. + + + + - - - ob_flush - - Flush (send) the output buffer - - - - Description - - voidob_flush - - - - This function will send the contents of the output buffer (if - any). If you want to further - process the buffer's contents you have to call - ob_get_contents before - ob_flush as the buffer contents are - discarded after ob_flush is called. - - - This function does not destroy the output buffer like - ob_end_flush does. - - - See also ob_get_contents, - ob_clean, - ob_end_flush and - ob_end_clean. - - - + + + ob_flush + Flush (send) the output buffer + + + Description + + voidob_flush + + + + This function will send the contents of the output buffer (if + any). If you want to further + process the buffer's contents you have to call + ob_get_contents before + ob_flush as the buffer contents are + discarded after ob_flush is called. + + + This function does not destroy the output buffer like + ob_end_flush does. + + + See also ob_get_contents, + ob_clean, + ob_end_flush and + ob_end_clean. + + + - - - ob_get_clean - - Get current buffer contents and delete current output buffer - - - - Description - - stringob_get_clean - - - - This will return the contents of the output buffer and end output - buffering. If output buffering isn't active then &false; is returned. - ob_get_clean essentially executes both - ob_get_contents and - ob_end_clean. - - - - A simple <function>ob_get_clean</function> example - + + + + ob_get_clean + Get current buffer contents and delete current output buffer + + + Description + + stringob_get_clean + + + + This will return the contents of the output buffer and end output + buffering. If output buffering isn't active then &false; is returned. + ob_get_clean essentially executes both + ob_get_contents and + ob_end_clean. + + + + A simple <function>ob_get_clean</function> example + ]]> - - - Our example will output: - - + + + Our example will output: + + - - - - - See also ob_start and - ob_get_contents. - - - + + + + + See also ob_start and + ob_get_contents. + + + + - - - ob_get_contents - - Return the contents of the output buffer - - - - Description - - stringob_get_contents - - - - This will return the contents of the output buffer without clearing it - or &false;, if output buffering isn't active. - - - - A simple <function>ob_get_contents</function> example - + + + ob_get_contents + Return the contents of the output buffer + + + Description + + stringob_get_contents + + + + This will return the contents of the output buffer without clearing it + or &false;, if output buffering isn't active. + + + + A simple <function>ob_get_contents</function> example + ]]> - - - Our example will output: - - + + + Our example will output: + + - - - - - See also ob_start and - ob_get_length. - - - + + + + + See also ob_start and + ob_get_length. + + + - - - ob_get_flush - - Flush the output buffer, return it as a string and turn off output buffering - - - - Description - - stringob_get_flush - - - ob_get_flush flushes the output buffer, return - it as a string and turns off output buffering. - ob_get_flush returns &false; if no buffering is - active. - - - - This function is similar to ob_end_flush, except - that this function returns the buffer as a string. - - - - - <function>ob_get_flush</function> example - + + + + ob_get_flush + Flush the output buffer, return it as a string and turn off output buffering + + + Description + + stringob_get_flush + + + + ob_get_flush flushes the output buffer, return + it as a string and turns off output buffering. + ob_get_flush returns &false; if no buffering is + active. + + + + This function is similar to ob_end_flush, except + that this function returns the buffer as a string. + + + + + <function>ob_get_flush</function> example + ]]> - - &example.outputs; - + + &example.outputs; + - - - - - See also ob_end_clean, - ob_end_flush and - ob_list_handlers. - - - + + + + + See also ob_end_clean, + ob_end_flush and + ob_list_handlers. + + + + - - - ob_get_length - - Return the length of the output buffer - - - - Description - - intob_get_length - - - - This will return the length of the contents in the output buffer - or &false;, if output buffering isn't active. - - - - A simple <function>ob_get_length</function> example - + + + ob_get_length + Return the length of the output buffer + + + Description + + intob_get_length + + + + This will return the length of the contents in the output buffer + or &false;, if output buffering isn't active. + + + + A simple <function>ob_get_length</function> example + ]]> - - - Our example will output: - - + + + Our example will output: + + - - - - - See also ob_start and - ob_get_contents. - - - + + + + + See also ob_start and + ob_get_contents. + + + + - - - ob_get_level - - Return the nesting level of the output buffering mechanism - - - - Description - - intob_get_level - - - - This will return the level of nested output buffering handlers - or zero if output buffering is not activated. - - - See also ob_start and - ob_get_contents. - - - + + + ob_get_level + Return the nesting level of the output buffering mechanism + + + Description + + intob_get_level + + + + This will return the level of nested output buffering handlers + or zero if output buffering is not activated. + + + See also ob_start and + ob_get_contents. + + + - - - ob_get_status - - Get status of output buffers - - - - Description - - arrayob_get_status - - bool - full_status - FALSE - - - - ob_get_status returns status information on - either the top level output buffer or all active output buffer levels - if full_status is set to &true;. - - - If called without the full_status parameter - or with full_status = &false; a simple array - with the following elements is returned: - - - Simple <function>ob_get_status</function> output - + + + + ob_get_status + Get status of output buffers + + + Description + + arrayob_get_status + bool full_status FALSE + + + ob_get_status returns status information on + either the top level output buffer or all active output buffer levels + if full_status is set to &true;. + + + If called without the full_status parameter + or with full_status = &false; a simple array + with the following elements is returned: + + + Simple <function>ob_get_status</function> output + Array ( [level] => 2 @@ -38,29 +32,29 @@ Array [name] => URL-Rewriter [del] => 1 ) - - - - - Simple <function>ob_get_status</function> results - KeyValue - levelOutput nesting level - typePHP_OUTPUT_HANDLER_INTERNAL (0) or PHP_OUTPUT_HANDLER_USER (1) - statusOne of PHP_OUTPUT_HANDLER_START (0), PHP_OUTPUT_HANDLER_CONT (1) or PHP_OUTPUT_HANDLER_END (2) - nameName of active output handler or ' default output handler' if none is set - delErase-flag as set by ob_start - - - - If called with full_status = &true; an array - with one element for each active output buffer level is returned. - The output level is used as key of the top level array and each array - element itself is another array holding status information - on one active output level. - - - Full <function>ob_get_status</function> output - + + + + + Simple <function>ob_get_status</function> results + KeyValue + levelOutput nesting level + typePHP_OUTPUT_HANDLER_INTERNAL (0) or PHP_OUTPUT_HANDLER_USER (1) + statusOne of PHP_OUTPUT_HANDLER_START (0), PHP_OUTPUT_HANDLER_CONT (1) or PHP_OUTPUT_HANDLER_END (2) + nameName of active output handler or ' default output handler' if none is set + delErase-flag as set by ob_start + + + + If called with full_status = &true; an array + with one element for each active output buffer level is returned. + The output level is used as key of the top level array and each array + element itself is another array holding status information + on one active output level. + + + Full <function>ob_get_status</function> output + Array ( [0] => Array @@ -87,24 +81,24 @@ Array ) ) - - - - The full output contains these additional elements: - - Full <function>ob_get_status</function> results - KeyValue - chunk_sizeChunk size as set by ob_start - size... - blocksize... - - - - See also ob_get_level and - ob_list_handlers. - - - + + + + The full output contains these additional elements: + + Full <function>ob_get_status</function> results + KeyValue + chunk_sizeChunk size as set by ob_start + size... + blocksize... + + + + See also ob_get_level and + ob_list_handlers. + + + + - - - ob_gzhandler - - ob_start callback function to gzip output buffer - - - - Description - - stringob_gzhandler - stringbuffer - intmode - - - - ob_gzhandler requires the zlib - extension. - - - - ob_gzhandler is intended to be used as a - callback function for ob_start to help - facilitate sending gz-encoded data to web browsers that support - compressed web pages. Before ob_gzhandler - actually sends compressed data, it determines what type of - content encoding the browser will accept ("gzip", "deflate" or - none at all) and will return its output accordingly. All - browsers are supported since it's up to the browser to send the - correct header saying that it accepts compressed web pages. - If a browser doesn't support compressed pages this function returns - &false;. - - - - mode was added in PHP 4.0.5. - - - - - <function>ob_gzhandler</function> example - + + + ob_gzhandler + ob_start callback function to gzip output buffer + + + Description + + stringob_gzhandler + stringbuffer + intmode + + + + ob_gzhandler requires the zlib + extension. + + + + ob_gzhandler is intended to be used as a + callback function for ob_start to help + facilitate sending gz-encoded data to web browsers that support + compressed web pages. Before ob_gzhandler + actually sends compressed data, it determines what type of + content encoding the browser will accept ("gzip", "deflate" or + none at all) and will return its output accordingly. All + browsers are supported since it's up to the browser to send the + correct header saying that it accepts compressed web pages. + If a browser doesn't support compressed pages this function returns + &false;. + + + + mode was added in PHP 4.0.5. + + + + + <function>ob_gzhandler</function> example + ]]> - - - - - - You cannot use both ob_gzhandler and - - zlib.output_compression. Also note that - using - zlib.output_compression is preferred over - ob_gzhandler. - - - - See also - ob_start and - ob_end_flush. - - - + + + + + + You cannot use both ob_gzhandler and + + zlib.output_compression. Also note that + using + zlib.output_compression is preferred over + ob_gzhandler. + + + + See also + ob_start and + ob_end_flush. + + + + - - - ob_implicit_flush - - Turn implicit flush on/off - - - - Description - - voidob_implicit_flush - intflag - - - ob_implicit_flush will turn implicit - flushing on or off (if no flag is given, - it defaults to on). Implicit flushing will result in a flush - operation after every output call, so that explicit calls to - flush will no longer be needed. - - - See also flush, - ob_start, and - ob_end_flush. - - - + + + ob_implicit_flush + Turn implicit flush on/off + + + Description + + voidob_implicit_flush + intflag + + + ob_implicit_flush will turn implicit + flushing on or off (if no flag is given, + it defaults to on). Implicit flushing will result in a flush + operation after every output call, so that explicit calls to + flush will no longer be needed. + + + See also flush, + ob_start, and + ob_end_flush. + + + - - - ob_list_handlers - - List all output handlers in use - - - - Description - - arrayob_list_handlers - - - - This will return an array with the output handlers in use (if any). If - output_buffering is - enabled or an anonymous function was used with - ob_start, ob_list_handlers will - return "default output handler". - - - - <function>ob_list_handlers</function> example - + + + + ob_list_handlers + List all output handlers in use + + + Description + + arrayob_list_handlers + + + + This will return an array with the output handlers in use (if any). If + output_buffering is + enabled or an anonymous function was used with + ob_start, ob_list_handlers will + return "default output handler". + + + + <function>ob_list_handlers</function> example + ]]> - - &example.outputs; - + + &example.outputs; + default output handler -) +) ]]> - - - - - See also - ob_end_clean, - ob_end_flush, - ob_get_flush, - ob_start. - - - + + + + + See also + ob_end_clean, + ob_end_flush, + ob_get_flush, + ob_start. + + + + - - - ob_start - Turn on output buffering - - - Description - - boolob_start - callbackoutput_callback - intchunk_size - boolerase - - - This function will turn output buffering on. While output - buffering is active no output is sent from the script (other than - headers), instead the output is stored in an internal buffer. - - - The contents of this internal buffer may be copied into a string - variable using ob_get_contents. To output - what is stored in the internal buffer, use - ob_end_flush. Alternatively, - ob_end_clean will silently discard the - buffer contents. - - - An optional output_callback function may - be specified. This function takes a string as a parameter and - should return a string. The function will be called when - ob_end_flush is called, or when the output - buffer is flushed to the browser at the end of the request. When - output_callback is called, it will receive - the contents of the output buffer as its parameter and is - expected to return a new output buffer as a result, which will be - sent to the browser. If the output_callback is not - a callable function, this function will return &false;. - If the callback function has two parameters, the second parameter is filled - with a bit-field consisting of - PHP_OUTPUT_HANDLER_START, - PHP_OUTPUT_HANDLER_CONT and - PHP_OUTPUT_HANDLER_END. - If output_callback returns &false; original input - is sent to the browser. - - - - In PHP 4.0.4, ob_gzhandler was introduced - to facilitate sending gz-encoded data to web browsers that - support compressed web pages. ob_gzhandler - determines what type of content encoding the browser will accept - and will return its output accordingly. - - - - - Before PHP 4.3.2 this function did not return &false; in case the passed - output_callback can not be executed. - - - - - Some web servers (e.g. Apache) change the working directory of a script - when calling the callback function. You can change it back by e.g. - chdir(dirname($_SERVER['SCRIPT_FILENAME'])) in the - callback function. - - - - If the optional parameter chunk_size is passed, the - callback function is called on every first newline after - chunk_size bytes of output. - The output_callback parameter may be bypassed by - passing a &null; value. - - - If the optional parameter erase is set to &false;, - the buffer will not be deleted until the script finishes (as of PHP 4.3.0). - - - Output buffers are stackable, that is, you may call - ob_start while another - ob_start is active. Just make - sure that you call ob_end_flush - the appropriate number of times. If multiple output callback - functions are active, output is being filtered sequentially - through each of them in nesting order. - - - ob_end_clean, - ob_end_flush, ob_clean, - ob_flush and ob_start - may not be called from a callback function. If you call them from - callback function, the behavior is undefined. If you would like to - delete the contents of a buffer, return "" (a null string) from callback - function. - You can't even call functions using the output buffering functions like - print_r($expression, true) or - highlight_file($filename, true) from a callback - function. - - - - User defined callback function example - + + + ob_start + Turn on output buffering + + + Description + + boolob_start + callbackoutput_callback + intchunk_size + boolerase + + + This function will turn output buffering on. While output + buffering is active no output is sent from the script (other than + headers), instead the output is stored in an internal buffer. + + + The contents of this internal buffer may be copied into a string + variable using ob_get_contents. To output + what is stored in the internal buffer, use + ob_end_flush. Alternatively, + ob_end_clean will silently discard the + buffer contents. + + + An optional output_callback function may + be specified. This function takes a string as a parameter and + should return a string. The function will be called when + ob_end_flush is called, or when the output + buffer is flushed to the browser at the end of the request. When + output_callback is called, it will receive + the contents of the output buffer as its parameter and is + expected to return a new output buffer as a result, which will be + sent to the browser. If the output_callback is not + a callable function, this function will return &false;. + If the callback function has two parameters, the second parameter is filled + with a bit-field consisting of + PHP_OUTPUT_HANDLER_START, + PHP_OUTPUT_HANDLER_CONT and + PHP_OUTPUT_HANDLER_END. + If output_callback returns &false; original input + is sent to the browser. + + + + In PHP 4.0.4, ob_gzhandler was introduced + to facilitate sending gz-encoded data to web browsers that + support compressed web pages. ob_gzhandler + determines what type of content encoding the browser will accept + and will return its output accordingly. + + + + + Before PHP 4.3.2 this function did not return &false; in case the passed + output_callback can not be executed. + + + + + Some web servers (e.g. Apache) change the working directory of a script + when calling the callback function. You can change it back by e.g. + chdir(dirname($_SERVER['SCRIPT_FILENAME'])) in the + callback function. + + + + If the optional parameter chunk_size is passed, the + callback function is called on every first newline after + chunk_size bytes of output. + The output_callback parameter may be bypassed by + passing a &null; value. + + + If the optional parameter erase is set to &false;, + the buffer will not be deleted until the script finishes (as of PHP 4.3.0). + + + Output buffers are stackable, that is, you may call + ob_start while another + ob_start is active. Just make + sure that you call ob_end_flush + the appropriate number of times. If multiple output callback + functions are active, output is being filtered sequentially + through each of them in nesting order. + + + ob_end_clean, + ob_end_flush, ob_clean, + ob_flush and ob_start + may not be called from a callback function. If you call them from + callback function, the behavior is undefined. If you would like to + delete the contents of a buffer, return "" (a null string) from callback + function. + You can't even call functions using the output buffering functions like + print_r($expression, true) or + highlight_file($filename, true) from a callback + function. + + + + User defined callback function example + ]]> - - - Would produce: - - + + + Would produce: + + @@ -141,20 +141,20 @@ ob_end_flush(); ]]> - - - - - See also ob_get_contents, - ob_end_flush, - ob_end_clean, - ob_implicit_flush, - ob_gzhandler, ob_iconv_handler - mb_output_handler, and - ob_tidyhandler. - - - + + + + + See also ob_get_contents, + ob_end_flush, + ob_end_clean, + ob_implicit_flush, + ob_gzhandler, ob_iconv_handler + mb_output_handler, and + ob_tidyhandler. + + + - - - output_add_rewrite_var - - Add URL rewriter values - - - - Description - - booloutput_add_rewrite_var - stringname - stringvalue - - - This function adds another name/value pair to the URL rewrite mechanism. - The name and value will be added to URLs (as GET parameter) and forms - (as hidden input fields) the same way as the session ID when transparent - URL rewriting is enabled with session.use_trans_sid. Please - note that absolute URLs (http://example.com/..) aren't rewritten. - - - This functions behavior is controlled by the url_rewriter.tags &php.ini; - parameter. - - - - Calling this function will implicitly start output buffering if it is - not active already. - - - - - <function>output_add_rewrite_var</function> example - + + + + output_add_rewrite_var + Add URL rewriter values + + + Description + + booloutput_add_rewrite_var + stringname + stringvalue + + + This function adds another name/value pair to the URL rewrite mechanism. + The name and value will be added to URLs (as GET parameter) and forms + (as hidden input fields) the same way as the session ID when transparent + URL rewriting is enabled with session.use_trans_sid. Please + note that absolute URLs (http://example.com/..) aren't rewritten. + + + This functions behavior is controlled by the url_rewriter.tags &php.ini; + parameter. + + + + Calling this function will implicitly start output buffering if it is + not active already. + + + + + <function>output_add_rewrite_var</function> example + print_r(ob_list_handlers()); ?> ]]> - - &example.outputs; - + + &example.outputs; + link link2 @@ -70,17 +68,17 @@ Array [0] => URL-Rewriter ) ]]> - - - - - See also - output_reset_rewrite_vars, - ob_flush and - ob_list_handlers. - - - + + + + + See also + output_reset_rewrite_vars, + ob_flush and + ob_list_handlers. + + + - - - output_reset_rewrite_vars - - Reset URL rewriter values - - - - Description - - booloutput_reset_rewrite_vars - - - - This function resets the URL rewriter and removes all rewrite - variables previously set by the output_add_rewrite_var - function or the session mechanism (if session.use_trans_sid - was set on session_start). - - - - <function>output_reset_rewrite_vars</function> example - + + + + output_reset_rewrite_vars + Reset URL rewriter values + + + Description + + booloutput_reset_rewrite_vars + + + + This function resets the URL rewriter and removes all rewrite + variables previously set by the output_add_rewrite_var + function or the session mechanism (if session.use_trans_sid + was set on session_start). + + + + <function>output_reset_rewrite_vars</function> example + link'; ?> ]]> - - &example.outputs; - + + &example.outputs; + link link ]]> - - - - - See also - output_add_rewrite_var, - ob_flush, - ob_list_handlers and - session_start. - - - + + + + + See also + output_add_rewrite_var, + ob_flush, + ob_list_handlers and + session_start. + + +