Code Parrots

Hi @projectmuzzle,

This plugin will work just fine with Polylang. As long as you have a language switcher on your site the timeline should update to the proper language. There is polylang support built into the plugin so the built-in cache clears and the languages update when users switch languages on the site.

Hi @koukoo,

We can do some testing with the private option checked to see if we are also encountering similar issues. This may be something built into the webpagetest API or a bug.

As for retrieving data, all of the data is stored inside of a serialized option site_speed_monitor_options.

$option = get_option( 'site_speed_monitor_options' );

$option['completed_tests'];

The completed test option should contain all of the test data that you need. What sort of data are you looking to retrieve out of there?

Sorry about that – I just noticed your follow up reply. You are right – it would be nice if we could get those results, package them up and send them out directly from your site. I’ve found that a number of plugins or themes (or customizations) may interfere with wp_mail, and thus breaks the email system built into WordPress. When this happens, no emails get sent from any plugin. So to prevent that from occurring, we went ahead and chose to have the emails sent out from the webpagetest.org api site, as to offload some of the overhead in the plugin (and this was already a feature of the API so we figured why not leverage it).

We can certainly take a look at what it might take to include that feature in a future release.

Hi @koukoo,

It sounds like something may not be right. The emails are actually sent out from the WebPageTest.org API and not from your WordPress site – so regardless of how your site handles mail, it should still be sent. We can do some testing to confirm that things haven’t changed with their API since the release of this plugin.

Thank you so much for taking the time to leave a thoughtful review @koukoo. We’re so glad that you find the plugin useful. Have a wonderful week!

Hi @edqtwolfi,

That’s correct – there is a new field generated when the date-time add-on is installed. Take a look at the example screenshots of the plugin at the bottom of the page here:
https://www.ads-software.com/plugins/timeline-express-date-time-add-on/

You’ll see a new ‘Announcement Date & Time’ field with a date picker and a time picker.

Are you running a request to example.com? We shouldn’t be referencing example.com in our plugin.

What I would suggest is checking the output of that remote get request in the code linked above. If you open the plugin file and add:

wp_die( print_r( $response ) );

just above

/* If the response body is empty, abort */

You should, at the very least, see what the response of the request is and why it’s failing.

Hi @babbefjes,

Does the error go away if you add the following to your themes functions.php file:

define( 'TIMELINE_EXPRESS_FONT_AWESOME_LOCAL', true )

Digging through some of the code, it looks like things are failing on the wp_remote_get request. Without access to the site, or adding some debugging into the code, it’s hard to tell what’s going on under the hood.

What version of the plugin do you have installed? This should not be an issue any longer as WP_Error is no longer being referenced as an array.

Hi @papsuev,

That’s correct. He free version and pro version are laid out differently. You’ll see different CSS styles with the pro version.

It’s possible, but you generally wouldn’t see a php warnings like that. It seems like something else may be at play. Have you tried temporarily switching themes to something like TwentySeventeen, and only having Timeline Express active? I can’t download Pxlz since it’s a premium theme from theme forest.

Are you using any of our add-ons alongside Timeline Express? Have you tried disabling other plugins to confirm that it is our plugin causing the issue? Is this the free or the pro version? I’m guessing this is the free version downloaded through your WordPress dashboard or from www.ads-software.com directly.

I’m not seeing that same error at the top of the page where the timeline is output. Do you have a link to that page?

We will do some quick testing to see if we can also reproduce the issue. If so, we will certainly push out an update fairly quickly to get the issue resolved.

We will post back here shortly with some findings!