about the upcoming autoptimize 2.0

I’m testing the latest code from github and I’m seeing a couple of warning empty needle messages on the autoptimize settings page.

Warning: strpos(): Empty needle in wp-content/plugins/autoptimize/classes/autoptimizeCache.php on line 81

Warning: strpos(): Empty needle in wp-content/plugins/autoptimize/classes/autoptimizeCache.php on line 150

I did not see these messages on my local machine, which doesn’t have CDN configured but I see them on my AWS host. FYI I’ve tried clearning WP cache and the “Save changes and empty cache” option.

first of all; thanks, I need people to test! ??

regarding the error; the warnings are not related to CDN, needle is the constant AUTOPTIMIZE_CACHEFILE_PREFIX which is (or should be) set in https://github.com/futtta/autoptimize/blob/ced6564db4d97764f6c76b01cd08f16ddb34d554/autoptimize.php#L31-L32 … so I don’t (yet) understand why this could be happening really …

frank

Hi,

I am using your plugin for a long time.

Right now I miss option which I think would be useful for some people, so hope to see it on next releases.

Inline the content only for anonymous users, so for example if I had some forum or commerce with users on it, inlining add extra performance cost, which could be eliminated.

Personally I do little hack in the plugin, just to get the behavior.

!is_user_logged_in() && $conf->get('autoptimize_css_inline'),

Hi dimotrov.adrian;
There’s a huge amount of possible options and I’m trying to keep the settings-screen as simple as possible, so you’ll understand I can’t add all options in there.

Autoptimize does, however, come with an extensive API (filters, mainly) which allow you to tailor it perfectly to your needs.

In you case you could hook into autoptimize_css_include_inline filter (there’s one for JS as well), returning false if is_user_logged_in() and true otherwise.

Hope this helps,
frank

I just pushed the first beta to wordpress SVN trunk. I’ll provide an overview of the major changes tomorrow, but in the mean time You can download here, testing & bug-reporting, on GitHub is very welcome (and a pre-condition for this ever to go live)!

I’ll also contact all translators for them to create updated mo/po-files.

I hope to be able to push AO 2.0 out before the end of the year, but you know the drill; it’ll be released when it’s ready ??

frank