Please don′t remove CDN!

I will, one way or another, provide some support for a smooth transition to another solution.

Big thumbs up!

I use the CDN option to serve static content from a cookieless domain (such as example.com vs. static.example.net).

In reality it’s a poor man’s CDN since it is an alias to example.com, but like the ability to do domain sharding across 2 domains.

Not that I will despair if you pull this feature off.

CDN is one of the BEST feature of this plugin. Why do you have to remove it?

Just to clarify: I also use a CDN setting in WP Super Cache together w7 Autoptimize, so this will be my fallback in case futtta pulls it off.

WP Super Cache uses .htaccess. No thanks!

If you are on a shared hosting plan then understandable but it you are hosted on VPS or better there’s just no excuse to have the web server reloading .htaccess on EVERY page request.

CDN is one of the BEST feature of this plugin. Why do you have to remove it?

I’ve started working on 1.7.0 (goal is to have a beta version in October and a final release in November) and there is good and bad news for you guys ??

CDN will remain in there (the good), albeit in a slightly restricted and simplified implementation (the bad).

Specifically;

• CDN will only be supported for autoptimized CSS & JS-files (i.e. not for images or css/js excluded from autoptimization)
• There will be only one CDN-related form element (instead of 6) in the admin, “CDN base url” which, if not empty, will be used to build the CDN-URL for both JS and CSS Autoptimized-files.

frank

Why don′t you just leave it as it is? It works perfectly fine now!
Anyway. Anyone who wants to serve images via subdomain just go to:

https://www.yourdomain.com/wp-admin/options.php

Go to: upload_url_path

Type in the subdomain of your images eg: images.yourdomain.com/

Hit save.

Go to -> Settings -> Media and check it is in there. ACTUALLY all images should now be served from your subdomain, but obviously make sure your subdomain points to your site root, it′s easier that way than having it point directly to the uploads folder and the performance is the same so just make it as simple as possible.

@ Frank: Please provide a current version download somewhere in case we want to go back and opt out from further updates, would you?

CDN will only be supported for autoptimized CSS & JS-files

I exactly wanted it. I don’t want to host my images on external servers but i think saving js and CSS files on external servers is a good option and loved by any webmaster. I am waiting for the coming version.

Why don′t you just leave it as it is?

Well, I want to focus on the core functionality of Autoptimize to ensure maintainability & supportability. I consider this core functionality being the minimizing of HTML and of aggregated JS/ CSS. Based on that, it ultimately made (some) sense to support CDN for Autoptimized JS/ CSS-files, but not for excluded JS/CSS-files or images.

Anyone who wants to serve images via subdomain just go to: […]

Great, I’ll refer to this in the FAQ!

Please provide a current version download somewhere in case we want to go back

Older versions can always be downloaded from the “developers”-page under “other versions”.

Looks like we′re all gonna find a way to make it work then, great! ??

Sorry, of course put in the upload_url_path field:

https://images.yourdomain.com/wp-content/uploads

Sorry for the glitch.

You can stick to older versions here:
https://www.ads-software.com/plugins/autoptimize/developers/

or here:
https://downloads.www.ads-software.com/plugin/autoptimize.1.6.4.zip

Also I’ve copied to here:
https://www.dropbox.com/s/jj3tx0pwu34edul/autoptimize.1.6.4.zip

The original developer want this plugin to continue. I’m looking into this as well:
https://www.ads-software.com/support/topic/wanted-developer-to-carry-on-with-autoptimize?replies=9

@hydn; I indeed took over development from turl (the original developer) the beginning of this year. If you’re interested to help out (providing support, testing, translations or development), I just posted a topic on help for the upcoming 1.7.0-release.

If any of you guys aren’t aware yet; there’s a test-version of 1.7.0 for which i’m eager to get feedback. In this version the old CDN-functionality has been removed (as mentioned before), but there’s new fuctionality in (which is more straightfoward and closer to AO’s “core business”).

Looking forward to your feedback!