Sparanoid

Some updates for latest Mailgun for WordPress v1.7.1:

With this version it seems the Mailgun options page will be set to hidden totally from dashboard if you define your credentials in wp-config.php. This somehow fix the original issue I mentioned above, but introduced a new issue. There’s no way to view the credentials or send test emails in dashboard. I still hope this issue could be fixed in a different way, just show the credentials and make them uneditable, or at least there should be a test connection button.

Hi, this workaround works smooth for me. Thanks!

Hi, it seems www.remarpro.com forum escapes code I entered, here’s a gist:

https://gist.github.com/sparanoid/a59b07b4958f7709c5236dc3934f6896

Hi beechws,

It seems your Home URL from the navigation bar was not replaced correctly. Maybe that URL is hardcoded into the theme? Could you share your theme or the PHP code snippet of your navigation part to me via [email protected] so I can look into this issue.

Thanks!

Hi beechws,

If I understand you correctly, in order to have rievtech.co.uk as a “second” domain of your site, you need to set an A record for rievtech.co.uk from your domain provider.

There’s nothing more you need to do, your links would be just transformed to relative URLs after activating this plugin.

Ok, I got the root cause of it: Jetpack Custom CSS: https://jetpack.com/support/custom-css/

After disabling Jetpack completely, Additional CSS generates “static” CSS so AO can work on it. If Jetpack is activated, Additional CSS will generate “dynamic” CSS because Jetpack adds CSS preprocessors support for it that need some dynamic processing for Sass and Less to get the plain CSS that browser can parse.

After some further investigation, you can disable the Custom CSS feature by Jetpack by using debug mode. It’s hard to find in the latest version of Jetpack.

I think you can add some notice for users willing to aggregate custom CSS like me.

And thank you so much for helping me debug this tricky problem, thanks!

• This reply was modified 5 years, 11 months ago by Sparanoid.

BTW what plugin are you using for the “additional CSS” feature that works with AO? Thanks

Well I’m tired of WordPress editor, here’s the gist https://gist.github.com/sparanoid/cbec49bcbab1f424a4895bdff4a6c022#gistcomment-2780349

I’m using a child theme of Twenty Twelve, with only some CSS tweaks.

After disabling AO totally, I got the answer:

If Additional CSS I use is smaller than n length (the exact length is not sure at the moment), WordPress just outputs the CSS inline itself:

`
<style type=”text/css” id=”wp-custom-css”>@font-face {
font-family: ‘Futura Std’;
src: url(data:application/font-woff2;charset=utf-8;base64,09GMgABAAAAAAUoAA4AAAAACjQAAATWAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGhYbIBwqBmAAPBEICoNsgxALFAABNgIkAxwEIAWKcwc0w) format(‘woff2’);
font-weight: bold;
font-style: italic;
}

:root {
–font-size: 15px;
–fontstack-heading: ‘futura-std’, var(–fontstack-prefix) var(–fontstack-sans-serif);
}

.entry-header .entry-title,
article.format-link .entry-content p:last-child {
font-style: italic;
line-height: 1.2;
letter-spacing: -.025em;
}

.searchform > div input[type=text] {
border-radius: 4px;
width: 100%;
}

#searchsubmit {
display: none;
}</style>
`

If it’s larger than n, it will be ?custom-css=xyz123.

So actually AO does not support aggregating Additional CSS?

More tests on different length with fake base64: https://www.useloom.com/share/d8c2662b3967444196c2b14c556bc30c

So weird… I recorded a video to reproduce this issue: https://www.useloom.com/share/28be9e9bbfee458aa39c266a18885edf

Yeah, it’s this one.

There’s only one Additional CSS for me to add CSS. I believe it’s powered by Jetpack because it’s gone when the Jetpack is disabled.

See https://gist.github.com/sparanoid/cbec49bcbab1f424a4895bdff4a6c022

Valid smaller embed webfont – still unaggregated.

I also tried a valid but lengthy embeded background image (larger than 64 KB which cannot be post here), also not aggregated.