Discuz Forum Home page access to a blank solution summary

First: The MySQL component did not add to the resulting resignation

warning:unexpected character in input: "(ascii=92) state=1 in e:139163 wwwbbsinstall.php on line 976
Parse error:parse error, unexpected '} ' in e:139163 wwwbbsinstall.php to line 979

Check that MySQL is connected properly and can be viewed using the Phpinfo () function.

If the MySQL component is not displayed, see if Lib_mysql.dll and Php5ts.dll are in the C:windowsystem32 directory.

Second: Caching problems

Delete all files in the following two folders
Forumdata/cache and/forumdata/templates

Solution:

Re-established, will Forumdata/cache and forumdata/templates

Third: Rewrite rule issues

Check the Httpd.ini rule below the root directory for problems

Four: Some space does not support gzip led, solution:

or use phpMyAdmin Click SQL to run the following SQL statement to copy the contents to the Clipboard code: UPDATE ' cdb_settings ' SET ' value ' = ' 0′where ' variable ' = ' gzipcompress ' LIMIT 1;

Fifth: Can not write to cache files, please check directory/forumdata/and./forumdata/cache/ .

You begin to view the permissions for the corresponding directory and find that you have given the Write permission. According to the information that is searched, say need to delete all the files under the Forumdata/cache directory, let discuz! The new cache was regenerated, but there were 400 errors after deleting all the files under the Forumdata/cache directory.

This time cannot enter the forum management backstage to empty the cache, later thought discuz! The official provided a tool for repair, so went to discuz! The official website downloads the original installation package, and then uploads the tools.php to the discuz! The root directory of the forum, but when the runtime unexpectedly prompts:

./forumdata/cache cleanup failed.
./forumdata/templates cleanup failed.

Oddly, the directory itself exists, and the directory has write permissions.

When I was helpless, I suddenly saw a post that mentioned discuz! The cache and Eaccelerator conflict, will eaccelerator disabled off on it, but will eaccelerator disabled after the problem is still, even eaccelerator the corresponding temporary directory files are deleted or invalid. Because Eaccelerator is placed in the/tmp directory by default, when you view the/tmp directory, Found a lot of shapes such as tcmalloc.4187 files, suddenly think of nginx in the use of Tcmalloc, while the nginx.conf file specified in the Tcmalloc directory for the/tmp/tcmalloc directory, but do not know why/ There is no Tcmalloc directory below the TMP directory, so create the directory and set 777 properties, restart Nginx invalid, so the system restart, the site will be normal access.