Phil Johnston

Hey there! Sorry to hear it didn’t work for you. If you’d like us to take a look at your specific situation and see what might be causing this for you, please let us know and we’d be happy to make sure it gets working for you.

We definitely do our best to make sure it works with all scenarios, but sometimes there can be 3rd party plugin conflicts that cause problems. When we learn about those, we love to figure out how to make it more compatible so it works for more people.

It’s working for about 400 other sites right now, and we’d love to work with you to make sure it works for yours as well. You can reach out anytime at [email protected] and we’d love to help you!

@bethinmaine2020 The update with TikTok has been released in version 3.1.1

@devrap When you say the images have broken, are you saying they are not loading at all? Or have they changed shape/position? Also, is there a specific block you are using where this is happening?

Thanks for the report and for following up! It looks like this was resolved and fixed in PostX – Gutenberg Post Grid Blocks ??

Hey there,

Thanks for the detailed report on this. This is something we are aware of, and would like to find a fix for. Like you mentioned it’s a limitation in the size allowed on the JSON endpoint. Perhaps we could consider chunking that JSON response if it’s over a certain size and doing multiple hits to the endpoint.

At this point I can’t make any promises about if/when we’d be able to make that happen, but we’ll put it onto our list for the next release to see if a fix is feasible.

Hey there,

Just to check, are you starting the URL with https://?

Hey there,

The file you are referring to (svgxuse.js) is expected to be in this plugin. You can see it as part of our GitHub repository here:
https://github.com/studiopress/simple-social-icons/blob/4cd95e1c46ba24bf1d6c4894833e08ebc873e631/svgxuse.js

When doing a search for “JS:Agent-EIY” and “svgxuse” together, the only result I find is your post here on the www.ads-software.com forums.

While not definitive, the lack of search results indicates these 2 things may not likely be linked in any form of attack.
https://duckduckgo.com/?q=%22JS%3AAgent-EIY%22+%22svgxuse%22&atb=v312-7__&ia=web

That being said, if you are seeing JS:Agent-EIY somewhere on your site, it would seem likely that you were infected with a trojan. See: https://www.fortiguard.com/encyclopedia/virus/7002682

But I do not see any specific evidence that the cause of this was this plugin, nor svgxuse.js

However, if you have any evidence to the contrary, please reach out to us by emailing (nathan.rice at wpengine.com) and we will be happy to work with you on resolving it.

• This reply was modified 2 years, 8 months ago by Phil Johnston.

That would break things. I would advise just picking one way or the other and sticking with it.

Hey @antoinet,

Just to help make sure I am understanding your issue correctly, can you share the portion of the HTML that is invalid in your postgrid setup?

There is actually an active community fork of WordPress from just before Gutenberg was introduced. It’s called ClassicPress. Doing a google search for “ClassicPress” should bring it up.

If nothing has changed on the “Appearance” > “Widgets” page for you, I would assume another plugin/theme has built-in the code from this plugin into their plugin, so that it’s off by default, without requiring this plugin.

The Genesis Framework theme did this, for example.

@wordsofawriter I totally sympathize with your struggle here. But the cold hard truth is that the core team at Automattic has decided (a long time ago now) that blocks are taking over all of WordPress, and nobody has as much power as Automattic in WordPress. There’s really no stopping the train now.

For anything that is not a block (widgets, themes, shortcodes, any-other-non-block-thing-in-wordpress) people will ultimately have to rely on plugins like this one.

• This reply was modified 3 years, 4 months ago by Phil Johnston.

@drunkfox My apologies, I should have explained more clearly what has happened. While Font Awesome was removed, the icons were all replaced with SVGs, so the Profile Box block and Social Sharing block will continue to show icons, even though Font Awesome was removed.

This makes it so that your page scores higher on Core Web Vitals / Lighthouse (Google’s page speed checker).

But the icons will definitely keep working without needing font awesome. The only reason you’d need Font Awesome (like I recommended above) is if you manually coded up some icons to show outside of blocks.

Hey there,

I checked out your page and the SVG icons are loading inside your Profile Box block. I wonder if it might be a browser caching issue. Are you able to try on another device or browser to rule that out?

• This reply was modified 3 years, 4 months ago by Phil Johnston.

Hey Rich,

I’m not totally sure if I understand, as when I press enter, I always get a new paragraph block.

Are you seeing this behavior within a certain block? If so, do you happen to know which one?