Nginx - wordpress在子目录中,应传递哪些数据?

时间:2011-05-27 16:04:24

标签: php wordpress path nginx webserver

我尝试过很多不同的事情。我现在的观点是:

location ^~ /wordpress {
    alias /var/www/example.com/wordpress;
    index index.php index.html index.htm;
    try_files $uri $uri/ /wordpress/index.php;

    location ~ \.php$ {
        include fastcgi_params;
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_split_path_info ^(/wordpress)(/.*)$;
        fastcgi_param SCRIPT_FILENAME /var/www/example.com/wordpress/index.php;
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }
}

现在,据我所知,所有资源(图片等)都正确加载。并且http://www.example.com/wordpress加载了wordpress,但是页面上显示“找不到页面”。 (尽管Wordpress正在使用中)。如果我尝试任何帖子网址,我会得到相同的结果,“找不到网页”。所以我知道问题是wordpress没有获得有关路径或其他东西的数据。另一个潜在的问题是,如果我运行example.com/wp-admin.php,它仍会运行index.php

需要传递哪些数据?这可能会出错?

3 个答案:

答案 0 :(得分:48)

由于您的位置别名最终匹配,您应该只使用root。此外,所有都不会通过wordpress afaik上的index.php进行路由。另外,除非你知道你需要路径信息,否则你可能不会。我想你想要的东西:

location @wp {
  rewrite ^/wordpress(.*) /wordpress/index.php?q=$1;
}

location ^~ /wordpress {
    root /var/www/example.com;
    index index.php index.html index.htm;
    try_files $uri $uri/ @wp;

    location ~ \.php$ {
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $request_filename;
        fastcgi_pass 127.0.0.1:9000;
    }
}

或者如果你确实需要路径信息(网址看起来像/wordpress/index.php/foo/bar):

location ^~ /wordpress {
    root /var/www/example.com;
    index index.php index.html index.htm;
    try_files $uri $uri/ /wordpress/index.php;

    location ~ \.php {
        fastcgi_split_path_info ^(.*\.php)(.*)$;
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $fastcgi_path_info;
        fastcgi_param PATH_TRANSLATED $document_root$fastcgi_path_info;
        fastcgi_pass 127.0.0.1:9000;
    }
}

编辑:更新了第一个服务器{}以从uri中去除初始/ wordpress并将余数作为q param传递

EDIT2:命名位置仅在服务器级别有效

答案 1 :(得分:13)

老兄,这适用于magento根文件夹子目录中的wordpress博客!

server {
listen 80;
server_name my-site.co.uk;
rewrite / $scheme://www.$host$request_uri permanent; ## Forcibly prepend a www
}

server {
listen 80 default;
client_max_body_size 8M;
## SSL directives might go here
server_name www.my-site.co.uk; ## Domain is here twice so server_name_in_redirect will favour the www
root /var/www/my-site/magento;

location / {
    index index.html index.php; ## Allow a static html file to be shown first
   try_files $uri $uri/ @handler; ## If missing pass the URI to Magento's front handler
   expires 30d; ## Assume all files are cachable
}

location  /wordpress {
          index index.php index.html index.htm;
         try_files $uri $uri/ /wordpress/index.php;
         }

## These locations would be hidden by .htaccess normally
location ^~ /app/                { deny all; }
location ^~ /includes/           { deny all; }
location ^~ /lib/                { deny all; }
location ^~ /media/downloadable/ { deny all; }
location ^~ /pkginfo/            { deny all; }
location ^~ /report/config.xml   { deny all; }
location ^~ /var/                { deny all; }

location /var/export/ { ## Allow admins only to view export folder
    auth_basic           "Restricted"; ## Message shown in login window
    auth_basic_user_file htpasswd; ## See /etc/nginx/htpassword
    autoindex            on;
}

location  /. { ## Disable .htaccess and other hidden files
    return 404;
}


location @handler { ## Magento uses a common front handler
    rewrite / /index.php;
}

location ~ .php/ { ## Forward paths like /js/index.php/x.js to relevant handler
    rewrite ^(.*.php)/ $1 last;
}

location ~ .php$ { ## Execute PHP scripts
    if (!-e $request_filename) { rewrite / /index.php last; } ## Catch 404s that try_files miss

    expires        off; ## Do not cache dynamic content
    fastcgi_pass   unix:/var/run/php5-fpm.sock;
    fastcgi_param  HTTPS $fastcgi_https;
    fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
    fastcgi_param  MAGE_RUN_CODE default; ## Store code is defined in administration > Configuration > Manage Stores
    fastcgi_param  MAGE_RUN_TYPE store;
    include        fastcgi_params; ## See /etc/nginx/fastcgi_params
}

}

答案 2 :(得分:2)

我遇到了同样的问题,这就是为我解决的问题:

  1. 打开您网站的NGINX配置文件。在服务器块内部,添加根目录的路径并设置文件的优先级顺序:

    root /mnt/www/www.domainname.com;
    index  index.php index.html index.htm;
    
  2. 在所有其他位置块之前创建一个空的位置块

    location /latest {
    # Nothing in here; this is to avoid redirecting for this location
    }
    
  3. 推荐您的位置/块中的根目录并添加重定向,使其如下所示:

    location / {
    # root   /mnt/www/www.domainname.com;
    index  index.php index.html index.htm;
    rewrite ^/(.*)$ http://www.domainname.com/latest/$1 redirect;
    }
    
  4. 确保您的位置〜.php $ block将其根目录指向

    root /mnt/www/www.domainname.com;
    
  5. 这为我解决了。