mr_spock

I could really use this too

I eventually tested removing the cache control setting, and there’s still no last-modified.

I don’t really care about it except some of the speed testing tools think it’s important so I’m concerned about search rank.

I’ll try the cache-control later…

Sorry, but that’s not happening. Check it out at https://www.abiquo.com – the htaccess rules (which I just forced the plugin to rewrite) are below. I’ve tried changing the expires header, that works fine. Any other ideas?

# BEGIN WebP Express
<IfModule mod_rewrite.c>
  RewriteEngine On

  # Redirect to existing converted image in cache-dir (if browser supports webp)
  RewriteCond %{HTTP_ACCEPT} image/webp
  RewriteCond %{REQUEST_FILENAME} -f
  RewriteCond %{DOCUMENT_ROOT}/wp-content/webp-express/webp-images/doc-root/wp-content/$1.$2.webp -f
  RewriteRule ^/?(.+)\.(jpe?g|png)$ /wp-content/webp-express/webp-images/doc-root/wp-content/$1.$2.webp [NC,T=image/webp,E=EXISTING:1,L]

  # Set Cache-Control header so these direct redirections also get the header set
  # (and also webp-realizer.php)
  <IfModule mod_headers.c>
    <FilesMatch "\.webp$">
      Header set Cache-Control "public, max-age=31536000"
    </FilesMatch>
  </IfModule>

  # Fall back to mod_expires if mod_headers is unavailable
  <IfModule !mod_headers.c>
    <IfModule mod_expires.c>
      ExpiresActive On
      ExpiresByType image/webp "access plus 1 years"
    </IfModule>
  </IfModule>

  # WebP Realizer: Redirect non-existing webp images to webp-realizer.php, which will locate corresponding jpg/png, convert it, and deliver the webp (if possible) 
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteRule ^/?(.+)\.(webp)$ /wp-content/plugins/webp-express/wod/webp-realizer.php?xdestination-rel=xwp-content/$1.$2&wp-content=wp-content [NC,L]

  # Redirect images to webp-on-demand.php (if browser supports webp)
  RewriteCond %{HTTP_ACCEPT} image/webp
  RewriteCond %{REQUEST_FILENAME} -f
  RewriteCond %{QUERY_STRING} (.*)
  RewriteRule ^/?(.+)\.(jpe?g|png)$ /wp-content/plugins/webp-express/wod/webp-on-demand.php?xsource-rel=xwp-content/$1.$2&wp-content=wp-content&%1 [NC,L]

  <IfModule mod_headers.c>
    <IfModule mod_setenvif.c>
      # Set Vary:Accept header for the image types handled by WebP Express.
      # The purpose is to make proxies and CDNs aware that the response varies with the Accept header. 
      SetEnvIf Request_URI "\.(jpe?g|png)" ADDVARY
      Header append "Vary" "Accept" env=ADDVARY

      # Set X-WebP-Express header for diagnose purposes
      # Apache appends "REDIRECT_" in front of the environment variables defined in mod_rewrite, but LiteSpeed does not.
      # So, the next line is for Apache, in order to set environment variables without "REDIRECT_"
      SetEnvIf REDIRECT_EXISTING 1 EXISTING=1
      Header set "X-WebP-Express" "Redirected directly to existing webp" env=EXISTING
    </IfModule>
  </IfModule>

</IfModule>
<IfModule mod_mime.c>
  AddType image/webp .webp
</IfModule>

Hi, I must be dumb – where is this set?

Thanks, but no it doesn’t. On your page https://wpjobmanager.com/document/fixing-structured-data-issues/ it says “All future jobs, however, should include the baseSalary data, provided a salary is actually entered during job submission.”

But they don’t. I have added salary data but there’s no baseSalary data in the structured data.

Hi – I followed the guide and get the salary field. However, it’s not creating the baseSalary structured data. I’m not sure where to start on that one!

Well that’s odd. Somehow that page got changed to a template we don’t use… switched template, and it works (of course). Thanks so much for your help!

Worth mentioning that the youtube video on the home page works fine, it seems to be just images.

I found the “search keyword statistics” plugin added the lines. Possibly due to a php version upgrade, I can’t really see why…

Now on the features page, the popups appear in the middle of the content, not the viewport. Still broken, but getting better!

Thanks – I’ve disabled a bunch of plugins on that /features page, so no blank lines now. The fancybox still has the same problem. Any more ideas? I’ve removed w3tc as well as that seems to break lots of things…

And it works in Edge! Broken in Safari, Chrome, Firefox (even in safe mode).

For anyone that finds this with search:

Divi doesn’t use YouTube URLs. It uses <video> tags so easy-fancybox isn’t triggered. Using a URL works.

Just went from 1.6 to 1.7 – it’s worse now as it tries to auto-center and the top: value just keeps increasing as I scroll.

In the Google help text for the API key it says you should add a referrer restriction, something like *<domain>/*

If you did that, delete it. The referrer restriction should be blank.

Then, I had to:

Delete my Wordfence cache
Delete my mod_pagespeed cache
Delete my local cache