JorgenScott

I posted an update about that on the Resolutions blog here: https://wpresolutions.co/suspended-from-wp-plugin-directory/. It was suspended because of a licensing issue that was already resolved once in the past. Not sure why it’s come up again but it should be resolved some time today.

Sorry about that. I’ve been frustrated with SVN. :\

Fixed now.

A new release of Resolutions is out (1.0) that integrates the latest version of Adaptive Images (1.4) and should remove the need to configure manually in most cases.

https://www.ads-software.com/extend/plugins/wp-resolutions/

I’m trying to solve this for a project. The Widget Logic plugin has fixed this issue, but it requires users to understand WordPress conditional functions, which is not ideal in my case. Studying their code might offer a solution, or maybe Widget Logic could be extended to add an easier-to-use UI…

I’m sorry that happened. What you need to do is erase the WP Resolutions rewrite block in your .htaccess file. Your .htaccess file will be in the root directory of your WordPress installation, and may be hidden in your FTP client by default.

This sounds like a bug that I resolved earlier today. Can you remember when you downloaded the plugin?

I encourage anyone who needs support to tweet me, @wpResolutions, or post on the plugin homepage. https://wpresolutions.co. ??

Thanks!

For those that are interested, you can grab the plugin at https://wpresolutions.co/. Hopefully it will be available in the WordPress plugin directory by the end of the week.

glovep,

At least you are getting a result. ??

I think from what you described that the path to your adaptive-images.php file, within your .htaccess file, may be incorrect. It should be wp-content/themes/your-theme/adaptive-images.php, including any subdirectories…

If that isn’t it, then also check:

1. The $cache variable within adaptive-images.php: It should be a path to your /ai-cache/ folder, relative to your .htaccess file. ex: wp-content/uploads/ai-cache/
2. Permissions: Make sure that your ai-cache folder has permissions ‘755’ or ‘777’.

I’ll be doing testing in the next week or so and could use another tester! If you’re interested then contact me at jorgen.co/contact

J?rgen

Hey glovep,

I created a second rewrite block within my .htaccess file. I don’t know if this is intelligent from a systems logic point of view, but it’s seems like an efficient solution.

WordPress creates a “WordPress section” within the .htaccess using comments that I didn’t want to mess around with in case my changes ended up getting over written somehow. Instead I created an Adaptive-images section with .htaccess, which makes it easy to automate updates to adaptive-images settings. Here’s my htaccess file:

# Adaptive-Images
<IfModule mod_rewrite.c>
RewriteEngine On

# Instead of defining paths to exclude I opted for the opposite
# I think this makes a bit more sense for WordPress
RewriteCond %{REQUEST_URI} /wp-content/uploads

RewriteRule \.(?:jpe?g|gif|png)$ path/to/adaptive-images.php

</IfModule>
# END Adaptive-Images
# BEGIN WordPress
<IfModule mod_rewrite.c>
# WordPress rewrite rules...
</IfModule>

# END WordPress

Hope that helps.

P.S. I’m working on a plugin for this. Right now there I’m working out a few bugs, but it will be ready mid December.

Update: I was able to get it working with adaptive-images.php nested in the theme files. The solution was that the cache path is relative to the root directory (or perhaps the directory where .htaccess is), even when the script itself is nested in another directory. Ie. even though my adaptive-images.php is nested in wp-content/themes/childtheme/ai, it was necessary to set my cache path to $cache_path = "wp-content/themes/childtheme/ai/cache"; instead of just $cache_path = "cache";

Crisbeee, looking at the github repo, I came across a fork that changed the javascript cookie to factor in devicePixelRatio: https://github.com/fm86/Adaptive-Images/commit/8fc66591f2345224a3ec239042983c6d8732d679.

Correct me if I’m wrong, but I don’t think that having adaptive-images.php and the ai-cache folder in the root of the WordPress install is ideal. Wouldn’t it be much better to have them with your theme files (in my case, which is integrating with a theme framework) or with your plugin files, if you opt to develop a plugin? Otherwise, implementation would always require a manual installation. Unfortunately, I have only been able to get results when adaptive-images.php is in the WordPress root, although nesting the cache folder with the theme files does not seem to be a problem.

I’m working on this as well, trying to integrate it in to PressWork. I haven’t had much success so far. Anyone else?