As far as I know, WordPress does not require a q= parameter set to the original request (the pretty permalink). So in the second option, the q= parameter will be silently ignored. According to the Nginx wiki page for WordPress, the query parameters (?$args or $is_args$args) are included: … so non-default permalinks doesn’t break when … Read more
What you’re looking for is to set a variable that determines whether a user is logged in (and other circumstances where you don’t want caching), then pass that variable to fastcgi_cache_bypass and fastcgi_no_cache: So in your server{} block you want something like this: set $skip_cache 0; # POST requests and urls with a query string … Read more
This has been solved, please note I am using WordPress 3.8 at the time of writing this, if you are from the future these plugins may not work with your current version, please check compatibility first. The plugin WP Multi Network provides this functionality. It basically allows you to create nested multi-site networks. I have … Read more
If your virtual host looks like this: try_files $uri $uri/ /index.php$args; change it to this: try_files $uri $uri/ /index.php$is_args$args; Adding $is_args (which will print a ? character if query arguments are found) will allow WordPress to properly receive and interpret the query parameters
A few things to check on: Review wp_salt. Make sure all of the web servers are running on the same set of salts in the wp-config.php file. Ideally, these should be mirrored from a single location. Review is_ssl() and make sure this function is properly detecting SSL across all of your web servers. I’ve seen … Read more
The problem resolved, I just need to add a location entry as follow: location /new { try_files $uri $uri/ /new/index.php?$args /new/index.php?q=$uri&$args; }
The correct Nginx rewrite rules for WordPress are: location / { try_files $uri $uri/ /index.php?q=$uri&$args; } This sends everything through index.php and keeps the appended query string intact. If your running PHP-FPM you should also add this before your fastcgi_params as a security measure: location ~ \.php { try_files $uri =404; // fastcgi_param …. // … Read more
So any suggestions are welcomed. Suggestion #1 – Whenever Memcache is available in the server, I prefer Memcached Object Cache and Batcache, unless I have a specific reason to use W3 Total Cache. Whatever, W3 Total Cache offers, can be achieved without it too. For example, for minify, we have Better WP Minify, For Varnish, … Read more
SELinux was the problem. Its enforcement was, for lack of a better term, overriding the file permissions and keeping WordPress from writing to any of the files. To solve the issue, I did the following: Check if SELinux is enabled: # getenforce If the response is “Enforcing”, then SELinux is enabled and it is probably … Read more
add this line to functions.php remove_filter(‘template_redirect’, ‘redirect_canonical’); and don’t forget clear cache or test on clean browser