MindCreatesMeaning

Thank you, I see the capability now!

Hello @daanvandenbergh ,

Thank you for providing me with two methods for testing for errors.

Neither method produced any errors that presented themselves visually in console or at the top of OMGF v4 settings page.

I’m open to further guidance.

Currently I have resorted to using the ‘Block Specific Plugin Updates’ Plugin to protect OMGF v3.7 from updating. I do hope to get past this though as I would much prefer to employ the latest versions of your software releases.

I’ll certainly be keeping an eye on this progress, thank you.

Please have a look and inform me as to what you believe I am doing incorrectly.

Here is the url:
https://abmonetize.com/haunt/

You’ll find two galleries half way down the page.

Gallery 1 is a native wp gallery.
Gallery 2 is a Simply Gallery Block (stuck on spinning)

Please have a look and inform me as to what you believe I am doing incorrectly.

Here is the url:
https://abmonetize.com/haunt/

OK, thank you for that answer. I can live with that!

Including wp-content/js and wp-includes/js didn’t work and created additional errors so I rolled back that change.

I revisited excluding wp-content/plugins while turning off ‘Aggregate Inline JS’ and it seems to work.

So…

I systematically added the exclusion of wp-content/each-of-my-plugins-individually but this did not work. It resulted in the same error we’ve been wrestling with.

I created a second testing site and I tracked down that I can create the error we’ve been seeing when the plugin Webp-Express is activated. So… I added the autoptimize exclusion of wp-content/plugins/webp-express and voila! The second testing site works. So…

Back on my main staging site, I deleted the exclusion of wp-content/plugins and added wp-content/plugins/webp-express … it doesn’t help. Back to square one.

I’m still seeing the ‘Uncaught SyntaxError: Unexpected token < in JSON at position …” error even after making the exclusions of:

wp-content/plugins, wp-content/themes, wp-content/js

I did think that I experienced one working iteration in the beginning which had be believing that these exclusions were working. However, they didn’t continue to work. I’ve since tried several times to clear autoptimize caching and see if it would work for me (even if only for one itereation), but I haven’t been able to reproduce that success…

It is ‘weird stuff’!!. The fact that json was involved at all was one of the things that was completely throwing me for a loop.

I’m going to attempt your suggestions now and I’ll report back.

I am using Oxygen builder so I have no ‘proper theme’ as it were.

Brb.

I appreciate your snippet, thank you for taking time to provide it as a potential solution.

This snippet allows for the first filtering task to work, but clicking ‘Reset filters’ or attempting to use the woocommerce built in ‘sorting order’ still won’t work after this.

Basically, you get one shot at using facetWP filter and your filtering days are over lol. It benches woocommerce sorting completely.

Screenshot:

View post on imgur.com

1. Error #1 Clicking ‘Reset filters’
2. Attempting to use woocommerce sorting order

The Staging URL is:

https://abmonetize.com/staging/shop/

Hi Matt,

Great insights, but still no success. Could your plugin be domain specific in terms of requiring font-awesome to come from ‘use.font-awesome.com’?

Here is what I have observed:

I followed your intuition in which you stated the placement of the <link> code could be the culprit.

I used view source to copy the exact link code that your plugin generates:
<link rel='stylesheet' id='font-awesome-css' href='https://use.fontawesome.com/releases/v5.13.0/css/all.css?ver=5.3.3' type='text/css' media='all' />

I turned off your plugin’s enqueue functionality for each of my icons.

I manually inserted the <link> code in different places in my page structure (header, body, footer). Each instance loaded the fonts perfectly.

It is only when I do not use the ‘use.fontawesome.com’ file that my issue arrises.

When I use my own file I copy and paste the exact contents of:
https://use.fontawesome.com/releases/v5.13.0/css/all.css?ver=5.3.3 into a new locally hosted css file.

I then confirm a successful ‘200’ message using DevTools.

This has me stumped.

Are there any other factors aside from placement that you can think of?

My setup is as follows:
I have ACF icons on a page.
Each icon has ‘enqueuing’ set to off.
I load a local exact copy of the font-awesome all.css file.
I check for a successful ‘200’ message that the local css file is loaded.
Positioning doesn’t seem to be the problem.

Could your plugin only be accepting all.css from a specific domain (use.font-awesome, in this case) and be ignoring all other possible sources for all.css?

Hi Matt,

I’ve just tried the following two methods:

1.) I copy and pasted the very css contents of the file that your plugin links to. When your plugin links externally – the css contents of all.css spring into action. When I host the exact same file locally – I don’t get icons.

I am placing this code in the footer of my website:

<link rel='stylesheet' id='font-awesome-css' href='https://mywebsite.com/staging/wp-content/external/all.css' type='text/css' media='all' />

2.) Operating on your suggestion that I needed to load different font awesome css. I used the same method above to load all of the individual css files from font awesome (brands, font-awesome, regular, solid, etc.) Still didn’t work for me.

I have all caching off.

I’ve tried placed the stylesheet links in footer, header, and body. Still no luck on my end.

Is something wrong with my code above?

I’m not affiliated with the plugin, but I found a solution several months ago. Try using this as a code snippet:

function rocket_lazyload_custom_threshold( $threshold ) {
	return 0;
}
add_filter( 'rocket_lazyload_threshold', 'rocket_lazyload_custom_threshold' );

Wonderful, thank you. I didn’t see any directions pointing toward the extension so I was unaware of it. I’ll check it out.