This article mainly introduces the reason and solution of thinkphp display verification code, combined with specific examples to analyze the thinkphp about verification code display related configuration methods and considerations, the need for friends can refer to the following
In this paper, the reasons and solutions of thinkphp display verification code are described. Share to everyone for your reference, as follows:
Today to the company, after the SVN update code, after entering the domain name in the browser, in the verification code that block display, looked for half the morning, and then carefully read the next Apache configuration file
<virtualhost *:80> ServerName admin.exam.com documentroot e:/www/exam/trunk/server/admin/ < Directory e:/www/exam/trunk/server/apps/admin/> Options followsymlinks allowoverride all Order deny , allow to Satisfy all </Directory></VirtualHost>
It turns out documentroot and directory inconsistencies.
<virtualhost *:80> ServerName admin.exam.com documentroot e:/www/exam/trunk/server/admin/ < Directory e:/www/exam/trunk/server/admin/> Options followsymlinks allowoverride all Order deny, Allow to Satisfy all </Directory></VirtualHost>
Should be added backstage, when the configuration file copy in a module, careless.
Other than that:
Today, a colleague encountered a similar problem, I think the above method can be solved, but try not to, in a pragmatic manner I went to see the next generation of verification code source files, and finally found that the original is that Crystal.ttf font file does not display, no wonder just show a line, Moving the font file to the directory where the source file is located is OK.