polyfade

Nevermind. There’s a tick box to not use plugin’s styles. That’s good enough for me.

@anmari thanks again. Here I was looking for some cryptic PHP function, but it’s that obvious. Yes, it seems the Calendar support was not rolled into their PHP build.

I can clearly see it on my personal, local and remote sites/servers.

Hmm, I wonder why the PHP team decided to make this optional? They include it automatically on the Windows version of PHP according to the docs.

• This reply was modified 4 years, 11 months ago by polyfade.

Hey @anmari, thanks so much for your response. Yep, I’m working on behalf of someone else’s hosting provider, and this has been yet another obstacle. They’re running PHP v7.4, to which I thought, “This hosting might not be so bad.”

• This reply was modified 4 years, 11 months ago by polyfade.

Exactly, thanks. I was getting confused by this: https://htaccess-for-nginx.com/

• This reply was modified 4 years, 11 months ago by polyfade.

Entire nginx config for the site. Much of this stuff is what Valet adds in for SSL, etc.

server {
    location ~ /wp-content/(?<path>.+)\.(?<ext>jpe?g|png|gif)$ {
        if ($http_accept !~* "image/webp") {
            break;
        }
        add_header Vary Accept;
        expires 365d;
        try_files /wp-content/uploads-webpc/$path.$ext.webp $uri =404;
    }
}

server {
    listen 127.0.0.1:80;
    #listen 127.0.0.1:80; # valet loopback
    server_name mysite.test www.mysite.test *.mysite.test;
    return 301 https://$host$request_uri;
}

server {
    listen 127.0.0.1:443 ssl http2;
    #listen 127.0.0.1:443 ssl http2; # valet loopback
    server_name mysite.test www.mysite.test *.mysite.test;
    root /;
    charset utf-8;
    client_max_body_size 512M;
    http2_push_preload on;

    location /41c270e4-5535-4daa-b23e-c269744c2f45/ {
        internal;
        alias /;
        try_files $uri $uri/;
    }

    ssl_certificate "/Users/me/.config/valet/Certificates/mysite.test.crt";
    ssl_certificate_key "/Users/me/.config/valet/Certificates/mysite.test.key";

    location / {
        rewrite ^ "/Users/me/.composer/vendor/laravel/valet/server.php" last;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log "/Users/me/.config/valet/Log/nginx-error.log";

    error_page 404 "/Users/me/.composer/vendor/laravel/valet/server.php";

    location ~ [^/]\.php(/|$) {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass "unix:/Users/me/.config/valet/valet.sock";
        fastcgi_index "/Users/me/.composer/vendor/laravel/valet/server.php";
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME "/Users/me/.composer/vendor/laravel/valet/server.php";
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }

    location ~ /\.ht {
        deny all;
    }
}

server {
    listen 127.0.0.1:60;
    #listen 127.0.0.1:60; # valet loopback
    server_name mysite.test www.mysite.test *.mysite.test;
    root /;
    charset utf-8;
    client_max_body_size 128M;

    add_header X-Robots-Tag 'noindex, nofollow, nosnippet, noarchive';

    location /41c270e4-5535-4daa-b23e-c269744c2f45/ {
        internal;
        alias /;
        try_files $uri $uri/;
    }

    location / {
        rewrite ^ "/Users/me/.composer/vendor/laravel/valet/server.php" last;
    }

    location = /favicon.ico { access_log off; log_not_found off; }
    location = /robots.txt  { access_log off; log_not_found off; }

    access_log off;
    error_log "/Users/me/.config/valet/Log/nginx-error.log";

    error_page 404 "/Users/me/.composer/vendor/laravel/valet/server.php";

    location ~ [^/]\.php(/|$) {
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass "unix:/Users/me/.config/valet/valet.sock";
        fastcgi_index "/Users/me/.composer/vendor/laravel/valet/server.php";
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME "/Users/me/.composer/vendor/laravel/valet/server.php";
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }

    location ~ /\.ht {
        deny all;
    }
}

Regarding my nginx setup, on some images I now see https://mysite.test/wp-content/webpc-passthru.php?src=https://gateway.test/wp-content/uploads/eva-400x400.png&nocache=1

So it must be this configuration:

server {
location ~ /wp-content/(?<path>.+)\.(?<ext>jpe?g|png|gif)$ {
        if ($http_accept !~* "image/webp") {
            break;
        }
        add_header Vary Accept;
        expires 365d;
        try_files /wp-content/uploads-webpc/uploads/$path.$ext.webp $uri =404;
    }

}

In the FAQs, the try_files /wp-content/uploads-webpc/$path.$ext.webp $uri =404; is specified differently. Should it be try_files /wp-content/uploads-webpc/uploads/$path.$ext.webp $uri =404; instead? Or maybe this is specific to my setup?

• This reply was modified 4 years, 11 months ago by polyfade.

Also, to return the slug, add 'slug' => $post->post_name.