Graphiq

@bowen111 It’s most likely an issue with the script enqueue-ing system. wp_enqueue_script has an $in_footer parameter that defaults to false. In all our testing/implementations the script always loads in the footer anyway, so we’ve never experienced the issue you’re describing, but we should probably set this parameter to true anyway. We just released version 3.2.5 of the plugin which sets this parameter to true, want to test it out and see if that fixes your issue?

If that doesn’t work, it would help if you could provide the following pieces of information:
a) What themes and plugins are you using in your installation?
b) Are there any other differences between the posts where things are loading / not loading.
c) If you are able to include links to example pages, that would be useful as well (if not, no worries)

• This reply was modified 8 years, 4 months ago by Graphiq.

We appreciate you reaching out and reporting this issue! In particular the issue of widgets.js being loaded in the footer vs. header sounds interesting, our developers will take a look and let you know what we find.

I believe we reach a resolution for the redirects issue through our on-site customer support tool, so I’m going to resolve this thread here. But if you have any other issues or questions, please let us know!

It appears that the URL you analyzed on Pingdom includes an iframe to findthehome.com, as shown in this image.

FindTheHome is a Graphiq website, however we do not support embedding this page into an iframe, and our wordpress plugin would not be the cause of this. My guess is that this iframe is being manually included outside of the plugin by one of your developers.

The plugin itself will only create iframes to graphiq.com, which do not contain any ads/redirects and are optimized for performance. The iframes on this page are a good example.

Any reason you’re including an iframe to findthehome.com? As far as we can tell it’s not actually visible on the page.

Eddison,

We just released version 3.2.3 of our plugin which should resolve the AMP violation. We really appreciate you reporting this issue, please let us know if you run into any other problems.

Best,
David

Eddison,

Thanks for reporting this issue–someone from our team will take a look and see if we can push out a fix.

– David

Hi chill87336,

Sorry for the delay in responding to you. You’d have to add a little bit of custom html around our shortcodes in order to get two visualizations side-by-side.

Something like the following:

<div style="display:inline-block;">
[graphiq ...]
</div>
<div style="display:inline-block;">
[graphiq ...]
</div>

We’ll think about making this a native feature of the plugin in the future. Thanks for the input!

We just released version 3.2.2 of the plugin, which should resolve this issue.

Our plugin is deployed to both WordPress VIP and www.remarpro.com, and we generally need to make a couple code changes to work with both environments–this was a case where we missed one change for www.remarpro.com, and it caused a fatal error when AMP is enabled. We’ll invest further into automated tests for both environments to ensure this does not happen again.

Thanks for reporting the issue! As a token of our appreciation, we’ll reach out and try to send some Graphiq gear your way.

Thanks for the heads up Stanko–we’ll start working on a fix.