Recently, a pigcms is installed on the server, and the server environment is centos6.5 + nginx + php-fpm. pigcms learned that it was developed with thinkphp. after being installed, the style of opening the homepage is messy, later, I checked a method on the Internet. change one field in ini to default_mimetype & quot;. other browsers are normal. only the mime type in ie9 does not match. This is now the case, but after pigcms is bound to a public platform, classification templates are always available for category management of micro-websites and cannot be selected. The page styles of the articles filled in for this classification are all messy, and the nginx server phppigcms
Recently, pigcms was installed on the server. the server environment is centos6.5 + nginx + php-fpm. pigcms learned that it was developed with thinkphp,
After the installation, the style of the homepage is messy. later, I checked a method on the Internet, in php. change one field in ini to default_mimetype = "". other browsers are normal. only the mime type in ie9 does not match. This is now the case, but after pigcms is bound to a public platform, classification templates are always available for category management of micro-websites and cannot be selected. Then, the page styles of the articles filled in for this category are all out of order. Then, compare the normal pages and find that the forwarding path of this page is incorrect, add/api/(the token of this number)/between normal pages. It should be wrong when the pathinfo path is overwritten, but the specific step of the error cannot be found. do you know this? deployment of pigcms in nginx environment