OK, feel free to re-enable the speedupper-disabling filter and then (if you’re still up for it) can you now rollback the change in autoptimize.php, so
@include(AUTOPTIMIZE_PLUGIN_DIR.'classes/external/php/yui-php-cssmin-2.4.8-4_fgo.php');
back into
@include(AUTOPTIMIZE_PLUGIN_DIR.'classes/external/php/yui-php-cssmin-2.4.8-p10/cssmin.php');
that way we know if it was only the speedupper or speedupper + minifying component ..
Re-enabled speedupper-disabling filter. Changed code in autoptimize.php. Site is working fine now.
OK, thanks for confirming @rockstaremperor. I’ll use the CSS I “harvested” from your site to try to improve the speedupper for a next release, in the meantime you can continue with the speedupper disabled 🙂
@rockstaremperor; can you check which of your individual CSS-files has
/* This theme contains intellectual property owned by Restored 316 LLC,including trademarks,copyrights,proprietary information,and other intellectual property. You may not modify,publish,transmit,participate in the transfer or sale of,create derivative works from,distribute,reproduce or perform,or in any way exploit in any format whatsoever any of this theme or intellectual property,in whole or in part,without our prior written consent.
and
.easyazon-popover-link-wrapper{position:relative}.easyazon-popover{background-clip:padding-box;background:#fff;border-radius:15px;border:1px solid #666;box-sizing:border-box;display:none;padding:15px;position:absolute;right:0;top:0;width:450px;z-index:9999999}.easyazon-popover-link-wrapper-hovered .easyazon-popover{display:block}
in it. might be one and the same file .. seems like this is where the speedupper stumbles, so seeing the original CSS might help me find the reason of the breakage.
Found the upper code in child theme’s style.css and lower code in popovers.css of easyazon plugin.
ok, could you provide me with links to those (here or in a mail to futtta-at-gmail-dot-com) so I can look at the source code. something in one of those two files is causing AO’s speedupper to break 🙂
update for those following here; the root cause was a non-terminated comment in the child theme’s CSS.
/* comment
.selector{color:black;}
instead of
/* comment */
.selector{color:black;}
I’ll have a good think about if/ how we can detect/ fix this in AO’s code .. 🙂
@jef3000 I didn’t receive info about your custom CSS?