Plugin / Autoptimize criticalcss.com power-up

Changelog

Changelog

1.17.1

  • Urgent fix for Uncaught Error: Call to undefined function is_user_logged_in() as reported by Matthew Rode.

1.17.0

  • Probably the last version before the merge into Autoptimize proper!
  • improvement: also save CCSS if validation was not succesfull due to blank screenshot (SCREENSHOT_WARN_BLANK)
  • improvement: jQuery deferring should also happen when “aggregate inlne JS” is on but should not happen for logged on users when AO CCSS is not returne for logged on users either.
  • bugfix: export didn’t work + usability improvements (requires ZipArchive class to be available in PHP)
  • bugfix: creation of AO CCSS cache directory failed in multisite context
  • misc. smaller improveent

1.16.0

  • new: allow “bound domain” to be changed (advanced option)
  • improvement: improved default settings logic
  • improvement: checks to prevent some PHP notices
  • bugfix: prevent files with CCSS being removed even when still referenced in a rule
  • bugfix: make sure rules and queue objects are global variables, thanks for the fix Marius!
  • bugfix: fix defer-wrapping of non-javascript script tags (ld/json for example), thanks for reporting Kyla!

1.15.2

  • bugfix to stop P (pending) jobs from being overwritten by N (new) ones, leading to rules being generated later or (in rare cases) not at all.

1.15.1

  • tell class_exists not to autoload classes to avoid queue processing breaking down (thanks to Markus for reporting and helping identify the issue)

1.15.0

  • bugfix for blacklist false positive
  • improvement: extra logic to ensure manual rules don’t get overwritten
  • improvement: ensure old rules don’t break site when API key is not valid and rules are not updated any more
  • logfile now queuelog.html instead of queue.log

1.14.0

  • better first time user experience
  • by default limit requests to criticalcss.com to 5 per cron run
  • bugfix: retry failed jobs icon
  • bugfix: ignore http vs https for domain binding
  • documentation: add tips to FAQ regarding how to improve start render/ first paint time

1.13.0

  • improvement: make sure the front-page only gets critical CSS from the is_front_page and not e.g. is_page
  • improvement: automatically bind plugin activity to a domain to avoid site clones start making requests
  • bugfix: if the default CCSS contained double quotes it broke both the CCSS when injected and the settings page, thanks to Baris for identifying the problem!
  • copy improvement for path-based rules.

1.12.0

  • new: advanced option (default off) to defer non-autoptimized JS (linked and inline).
  • improvement: in maintenance job check if ao_ccss_queue is scheduled and schedule if not.
  • improvement: added filter (ao_ccss_queue_schedule) to allow (power-)users to change the scheduling of the queue processing job.

1.11.0

  • keep API key and some other key (non-transient) settings when plugin is deactivated
  • improve “force include” copy + set max-size on that input field
  • add extra info (wp_error) to debug log if key check does not succeed

1.10.1

  • remove a line of debug code

1.10.0

  • improvement: create path-based rules for pages by default for new installs (change the setting manually when upgrading from 1.9.0)
  • bugfix: recheck invalid API key during the daily maintenance to avoid it getting stuck
  • bugfix: don’t strip slashes in generated CCSS
  • update to latest version of the “persist admin notice dismissal” framework library

1.9.0

  • improvement: make some notices dismissable
  • improvement: job queue cleanup logic improved
  • improvement: there now is a different error-message for “bad API key” vs “could not check your API key”
  • improvement: logic added to be able to warn if criticalcss.com would be down
  • bugfix for subfolder installations of WordPress resulting in wrong URL’s to be sent to criticalcss.com
  • bugfix: some EDD conditionals were empty in the dropdown
  • bugfix for notice “Argument #2 is not an array /wp-content/plugins/autoptimize-criticalcss/inc/core.php: 243”

1.8.0

  • improvement (efficiency): don’t submit request to criticalcss.com if the same one (same type and same hash) has been submitted already in the current queue processing run
  • improvement (UI): job queue panel is collapsable and only shown if no AUTO rule is available yet
  • improvement (debugging): add rule info in comment in Critical CSS if “debug” is on
  • improvement (conditional rules): added is_attachement as additional core conditional tag
  • new: handle (future) resultStatus (HTML_404) from criticalcss.com

1.7.0

  • new: (advanced) option to allow PATH-based rules to be auto-created for pages allowing different CCSS for each page.
  • improvement: workaround a quirk in WordPress core’s is_front_page which also returns true for e.g. /page/12
  • improvement: ensure path-based rules with non-ascii characters can match the path

1.6.0

  • new: (advanced) option to disable CCSS injection for logged on users (as the CCSS is always geneated from an anonymous visitor context, the CCSS might not apply for logged in users).
  • improvement: warn when the job queue processing task is not getting triggered (due to WordPress cron issues).
  • improvement: also submit a request to criticalcss.com if a rule exists but the file containing the CCSS does not exist or is empty.
  • added info about cron issues to the FAQ.

1.5.0

  • bugfix: when deactivating make sure lockfile is removed before removing cache directory.
  • bugfix: make sure Autoptimize’s “inline & defer above the fold CSS” is not removed when submitting criticalcss API key.
  • bugfix: ensure order of rules does not depend on when they were added, but is custom post types first, template 2nd, plugins (Woo, EDD, BuddyPress & BBPress) conditional tags and lastly the WordPress core conditionals.
  • bugfix: make sure non-core conditionals are checked against.

1.4.0

  • move cache to wp-content/uploads/ao_ccss/ (to prevent files from being deleted by a sometimes overzealous WP Super Cache purge)
  • warn if DISABLE_WP_CRON is true
  • update default viewport size in advanced settings

1.3.0

  • New: you can now create manual rules to make sure no Critical CSS is injected by entering none as critical CSS.
  • Improvement: make sure “advanced options” are visible when “activate inline & defer” warning is shown
  • Further copy changes in description (thanks for the great feedback Paul!)

1.2.0

  • New advanced option: “Fetch Original CSS”
  • Minor copy changes in Key settings panel and FAQ.

1.1.0

  • Changes to queue processing to cater for hosts with hard limits on PHP processes duration

1.0.1

  • Extra info on the API key entry page

1.0.0

  • Initial release

Ratings

4.8
18 reviews

Rating breakdown

Details Information

Version

1.17.1

First Released

06 May, 2018

Total Downloads

119,220

Wordpress Version

4.9 or higher

Tested up to:

5.2.4

Require PHP Version:

-

Tags

Contributors

Languages

The plugin hasn't been transalated in any language other than English.

DIRECTORY DISCLAIMER

The information provided in this THEME/PLUGIN DIRECTORY is made available for information purposes only, and intended to serve as a resource to enable visitors to select a relevant theme or plugin. wpSocket gives no warranty of any kind, express or implied with regard to the information, including without limitation any warranty that the particular theme or plugin that you select is qualified on your situation.

The information in the individual theme or plugin displayed in the Directory is provided by the owners and contributors themselves. wpSocket gives no warranty as to the accuracy of the information and will not be liable to you for any loss or damage suffered by you as a consequence of your reliance on the information.

Links to respective sites are offered to assist in accessing additional information. The links may be outdated or broken. Connect to outside sites at your own risk. The Theme/Plugin Directory does not endorse the content or accuracy of any listing or external website.

While information is made available, no guarantee is given that the details provided are correct, complete or up-to-date.

wpSocket is not related to the theme or plugin, and also not responsible and expressly disclaims all liability for, damages of any kind, arising out of the use, reference to, or reliance on, any information or business listed throughout our site.

Keep Leading Your Followers!
Share it for them.