babyewok

@dannycooper thanks for the explanation! I imagined it must be something like that.

Interesting – fixed by changing it to this:

function sydney_dequeue_google_fonts() {
       wp_dequeue_style( 'sydney-fonts' );
}
add_action( 'wp_enqueue_scripts', 'sydney_dequeue_google_fonts', 999 ); 

If anyone could enlighten me as to why this made a difference, I’d appreciate it!

Hmmm, the developer doesn’t seem very helpful here and I seem unable to post on their own website’s support forum.

To the developer… Do you not answer any support questions?

@ultraloveninja I have the same issue – did you resolve this?

• This reply was modified 6 years, 1 month ago by babyewok.

OMG, I have finally figured it out! Turns out is was the stupid theme that was inlining some CSS, I just assumed the only inlined CSS was that which autoptimize added.

<rant>I swear I rue the day I decided using a bought theme would save me time over coding the site myself – it has done nothing but remind me why I hate all these bloated themes and the stupid ‘builders’ used to edit them!! </rant>

Right rant over – thanks for your patience. I know mine has been tested to the limit!

Well I have just checked the database, and the CSS is correct there! It is obviously a caching issue. Strangely this is the ONLY thing I seem to have a caching issue with.

OK, so I checked the critical CSS I have entered in to the back office, and it is correct. I even deleted it, kept the inline critical CSS box checked and then cleared all the caches and the old critical CSS was still showing inline!

I am using Chrome developer tools to debug this and I can see that
#pricing-7e127befd3bc33fb5e5d27189ae2f13b .sh-pricing-content-item has been updated to
border-color: rgba(255,255,255,.3)!important;
in the autoptimize_87750773f7f4376bc25f2b254054e101.css.

However this is overwritten by the inline critical CSS on line 72 which says: border-color:
rgba(158,158,158,0.2)!important;

I have checked and double checked and that is NOT what I have in the critical CSS entered into the autoptimize settings! It is most definitely stuck in the database! Especially since it will not be removed when I disable the inline critical CSS option.

I am not at my computer right now, but the css has been updated in the autoptimize css but not in the inline critical css which I also updated. I will let you know the exact class when I am back at my computer, but it is basically to make the dividing lines in the ￡400 price package white – you can see they are overridden by the critical css inlined on the page but this will not update and as I said, I cannot even remove it!

Is there something I can do directly in the database to clear out the old css and replace it?

https://forevervintagevw.co.uk

Aah, it’s OK. I noticed a stupid mistake in my code! A missing bracket after my else statement!

• This reply was modified 6 years, 1 month ago by babyewok.

No to memcache and redis, but Zend OPcache is enabled on the server

Absolutely nothing! The inline css is still there. It is as though it is stuck – doesn’t update and can’t be removed.

Hi @keligrafik, how did you resolve this? I have the same issue

Well I was able to insert 50 images myself all at once on the post with the child theme, and all showed up in the post. I discoverd the <figure class=”gallery-thumb”> was due to her selecting gallery as the post type.

I think it is more that she did something wrong! But since it is all working for me when I try I have no idea what to tell her not to do!