First, let me say hello and thanks for this forum. I'm a newby to Directadmin. I am, however, no newby to Nginx.
My WordPress permalinks aren't working for posts and pages. This obviously came as quite a surprise to me, as I've been doing this on Nginx for years.
I have some favorite Nginx coonfiguration entries such as:
location / {
try_files $uri $uri/ /index.php?$args;
}
and
location ~* ^.+\.(jpg|jpeg|png|gif|ico|css|js)$ {
access_log off; # Disable logging
log_not_found off;
expires max;
}
I'd like those entries to be global, as most of my clients do in fact use WordPress. I'd really prefer *not* to have to do this w/every user I set up, but I'm pretty confused about how to do that. I've read about httpd custom templates, but I'm not sure what the template token location_blocks means. I've also read about custom httpd configurations, but I am just really uncertain about how to do this globally as opposed to per user. I'm unsure of the order, as in, how can I include a configuration so it won't be overwritten by items taking precedence over it.
I don't mean this as a criticism, but although you've got a lot of documentation, it just feels kind of scattered and hard to put the pieces together. And, as with all documentation, some has become depricated over time but remains for historical purposes or those using older versions, which adds further to the muddying of the waters.
So, if anyone can provide some insight as to how to go about this, I'd be appreciative. Thanks in advance for any assistance, and have a great rest of your day.
Jackie
My WordPress permalinks aren't working for posts and pages. This obviously came as quite a surprise to me, as I've been doing this on Nginx for years.
I have some favorite Nginx coonfiguration entries such as:
location / {
try_files $uri $uri/ /index.php?$args;
}
and
location ~* ^.+\.(jpg|jpeg|png|gif|ico|css|js)$ {
access_log off; # Disable logging
log_not_found off;
expires max;
}
I'd like those entries to be global, as most of my clients do in fact use WordPress. I'd really prefer *not* to have to do this w/every user I set up, but I'm pretty confused about how to do that. I've read about httpd custom templates, but I'm not sure what the template token location_blocks means. I've also read about custom httpd configurations, but I am just really uncertain about how to do this globally as opposed to per user. I'm unsure of the order, as in, how can I include a configuration so it won't be overwritten by items taking precedence over it.
I don't mean this as a criticism, but although you've got a lot of documentation, it just feels kind of scattered and hard to put the pieces together. And, as with all documentation, some has become depricated over time but remains for historical purposes or those using older versions, which adds further to the muddying of the waters.
So, if anyone can provide some insight as to how to go about this, I'd be appreciative. Thanks in advance for any assistance, and have a great rest of your day.
Jackie