nasca

JS minification doesn’t bode well with a lot of JS libraries. Since the gains from JS minification are minimal it’s better to leave it off.

This is the first time I have used CouldFront with this site so I haven’t invalidated anything yet.

I am curious though… when you view page source which distribution is serving content?

I was/am having the same issue … sort of. I am getting the same error message when testing the configuration.

I have tided to ‘validate’ the configuration 2 ways.
(1) AWS>Sect Creds> CloudFront > Access and Secret
(2) Create User / Group / Permissions via IAM with the AWS Policy Generator.

However, even though the plugin does not validate the Access Key and Secret Key… CloudFront is serving content for my domain / site. I know this because when viewing the page source in the browser the CNAME configured in Route53 is visible. If you don’t have Route 53 configured with a sub domain for CloudFront you will just see something like #######.cloudfront.com

My guess is that the plugin validation needs to be updated and I wouldn’t worry about the “Empty Access Key’ error if in fact CloudFront is serving content.

I am having the same blank screen of death problem. Very hard to replicate consistently.

Version 0.9.2.11, Apache, AWS CDN

The following seem to show no effect and I tested them extensively with countless combinations.

• Compatibility Mode
• Enhanced / Basic Disk Cache

My guess is that if in fact a bug does exist it occurs with a combination of minify settings, htaccess, url-rewrite, using a child theme and if the user is logged in. I spent 3 of 4 hours trying to resolve this particular problem and in the past have not found this plugin to be cumbersome at all.

@sdaponte
thanks for the snip…. is is possible that you used a conditional tag?

https://codex.www.ads-software.com/Conditional_Tags

Go to php my admin (database). Click on the options table. It might be wp_options or whatever table prefix you use. Click on the SQL tab at the top of the page.

Run this query:
SELECT * FROM wp_options WHERE option_name = 'active_plugins';

Delete contents form the row returned by the query(all your doing is deactivating all your plugins).

Click GO.

Refresh your site. Log in. Enable the plugins one by one to see which one was causing the problem.