Solution to Blank Lines Appearing in PHP Template_PHP Tutorial

It was solved locally, but there were still blank lines when uploading to the server. After working on it all morning, it almost crashed. Finally, I decided to find a way to solve it myself. After several hours of exploration, I finally found a perfect solution.
Using the PHP display buffer display principle, successfully removed
Add a line of ob_start() at the top of PHP; Then add an ob_end_clean() before the template is displayed; Add an ob_end_flush() after the template is displayed;
The problem is solved. Now give the overall structure example code:

Additional comments from other netizens:
A problem that has never been solved during development, collection
The page uses UTF8 encoding, and the header and tail use the template inclusion file method , as a result, there is an extra blank line of about 10px at the head and the tail for no reason, and there is nothing.
The reason is that all UTF8 encoding is used. When including files, the final binary stream contains multiple UTF8 BOM tags. IE cannot parse pages containing multiple UTF8 BOM tags normally and directly replaces them with the actual displayed carriage return. This results in a blank line, but Firefox does not have this problem.
Therefore, if the template uses the inclusion method to contain multiple utf8 files and needs to be saved with ultraedit, select the save as function and select utf8 without BOM format to save.
In addition, if the Chinese page puts the title tag in front of in the html head tag, it will cause the page to blank.
So the utf8 page should use the standard order


BOM header: xEFxBBxBF, PHP4 and 5 still ignore BOM, so they are output directly before parsing.
There is a special description of this issue in the w3.org standard FAQ:

http://www.w3.org/International/questions/qa-utf8-bom

The details are as follows:

There is a character called "ZERO WIDTH NO-BREAK SPACE" in UCS encoding, and its encoding is FEFF. FFFE is a character that does not exist in UCS, so it should not appear in actual transmission. The UCS specification recommends that we transmit the characters "ZERO WIDTH NO-BREAK SPACE" before transmitting the byte stream. In this way, if the receiver receives FEFF, it indicates that the byte stream is Big-Endian; if it receives FFFE, it indicates that the byte stream is Little-Endian. Therefore, the character "ZERO WIDTH NO-BREAK SPACE" is also called BOM.

UTF-8 does not require a BOM to indicate the byte order, but can use the BOM to indicate the encoding method. The UTF-8 encoding of the character "ZERO WIDTH NO-BREAK SPACE" is EF BB BF. So if the receiver receives a byte stream starting with EF BB BF, it knows that it is UTF-8 encoded.

Windows is an operating system that uses BOM to mark the encoding method of text files: WindowsXP Professional, default character set: Chinese

1) notepad: can automatically identify utf- without BOM 8 encoding format file, but you cannot control whether to add BOM when saving the file. If you save the file, BOM will be added uniformly.

2) editplus: cannot automatically recognize UTF-8 encoding format files without BOM. When saving the file, select UTF-8 format and will not write BOM header in the file header.

3) UltraEdit: The most powerful function for character encoding, it can automatically identify UTF-8 files with and without BOM (can be configured); when saving, you can choose whether to add BOM through configuration.

(Special It should be noted that when saving a newly created file, you need to choose to save it as utf-8 no bom format)

Later I found that Notepad ++ also has better support for utf-8 bom, and it is recommended for everyone to use it.