WorldWideWebb

Oh – duh! I had completely forgot that those were all separate widgets. Thanks!

It’s the main plugin file: wp-document-revisions/wp-document-revisions.php

Do a Ctrl-F for “serve_file”, then scroll to the closing curly brace of that method. Add the lines directly before the “read_file( $file);” line.

I think it may have something to do with role scoper (or a capabilities issue). When I’m logged in as an admin, search works normally in the popup. When I log in as a user with reduced capabilities (like a contributor), I get no results when running a search (the thumbnails come up normally to select from, but all searches return nothing). Any ideas?

Resolved, but would still greatly appreciate clarification on my last question (regarding how the breakpoints are coded for).

Appears to be. I did some more testing on a non-retina device and it appears to be working as expected. Just so I’m clear, am I understanding the breakpoint functionality & size generation properly? This is my assumption:

For each breakpoint specified in the Hammy options, an image size is generated matching the width of that breakpoint. That size is then used if the container size is greater than or equal to the size of the breakpoint.

I tried installing the imagemagick (and php-imagick) packages, and now the different sizes are being generated (so we at least now know that it’s not a directory permissions issue). However, not all of the sizes are being added, and the sizes are not being swapped out on the page (big a** image at the bottom):

https://mor.gd/2013/05/sample-content/

The original uploaded image is 1175 wide, and here are screenshots of my hammy settings and WP media settings:

https://cl.ly/PJIB
https://cl.ly/PJFD

Thoughts?

Thanks in advance

No – was hoping for an answer to the last questions I posted.

Thx

Looks like I don’t have the cache directory. And if you’re referring to the plugin WPThumb, I don’t. Is it required? If it is, does it create that cache directory?

Thanks!

Nope. All I hear is the chirping of crickets here.

Found a solution!

I did some more searching and came across this great snippet:

https://bradt.ca/blog/image-crop-position-in-wordpress/

I then modified the bt_image_resize_dimensions function so that it will either always use WordPress’s version of “hard-crop” (meaning it will resize the image down first, then crop the remaining), or it will actually hard-crop the image (meaning it will crop down, to the specified dimensions, using the full-size image). The new function in its entirety can be found here:

https://snipt.org/vQic8

Nevermind! Found the answer. Just drop this at the bottom of your theme’s functions.php file:

add_action('init', 'docs_add_default_boxes');

function docs_add_default_boxes() {
    register_taxonomy_for_object_type('category', 'document');
    register_taxonomy_for_object_type('post_tag', 'document');
}