pindiespace

Sorry, I wasn’t clear. I understand it is a problem with my installation – I did the same thin with a default WordPress copy. I’m trying to track it down – must be something an old plugin did to the site (up since 2011). I tried disabling all plugins – same thing.

I’ll let you know if I figure out the problem in my media library.

——————————————————————–
My other point is UX/UI, specifically the labels ShortPixel is using for the filters it adds to the Media Library…

Let’s say you have ShortPixel installed. You currently, go to the Media Library and select the “Optimized” filter put there by ShortPixel. Right now, it just hide unoptimized files and shows optimized ones.

But in the future, the Media Library might automatically show .webp and .avif files by default, as they become standard formats.

In that case, selecting the “optimized” filter put in by ShortPixel filter would hide .webp and .avif files.

And, if you applied the “not optimized” filter in the future, it would show all the .webp and .avif files, along with un-optimized jpg, gif, png files.

Users would ask “is the .webp optimized itself?”

The change is that ShortPixel isn’t just creating optimized versions of the same files – it is creating completely new files.

In other words, my broken Media Library’s behavior might be the standard in the future, if WordPress starts allowing .webp and .avif files to be uploaded by default.

It’s a interface issue. There may be a better way to name the filters that ShortPixel adds to the Media Library, or indicate what’s optimized.

The other issue – if you have ShortPixel, and select “optimized” as your filter in the Media Library, the .webp and .avif files disappear. A user might misunderstand that as ShortPixel failing to create these files.

OK, will check. I did the same test with my barebones localhost wordpress, and got the same result. Must be subtle, since I don’t have any obvious media library plugins. Will report back when I find the offending plugin.

There is a use case for adding a filter “filter out next-gen” files. In some cases, users will want to upload their own webp and avif files, while others may want to hide them and only show the file type they typically upload (e.g. jpg, gif). You can do that with the filter “show optimized” with ShortPixel – it excludes visible .webp and .avif now, but the name of the filter could be clearer.

OK, we figured it out, Here’s the result in case someone else encounters this…

It was in WordPress settings:

WP Dashboard -> Settings -> General

WordPress Address was: https://novyunlimited.com
Site Address was: https://www.novyunlimited.com

making both https://novyunlimited.com fixed the .htaccess problem and allow permalinks, etc to be written correctly!

This might be a useful warning in WP-Security. If the plugin registers a ‘0’ permission, it is probably due to mismatch between WordPress address and site address.

Yes, the install was /home/novy/public_html/

However, the location of the .htaccess file is listed by all-in-one as /.htaccess, rather than /home/novy/public_html/.htaccess.

There is a perfectly normal 644 permission .htaccess at
/home/novy/public_html/.htaccess

…with permissions 644

…but WP seems to think it should be at /.htaccess

What would cause the htaccess path to be:

/.htaccess

instead of root_directory/home/user/public_html ?

How is the location of .htaccess set?

Is it correct that the path for .htaccess should be:

.htaccess /.htaccess

when the root directory is:

root directory /home/novy/public_html/