Cannot use object of type WP_Error

Hi Paul,

You shouldn’t be getting this error on a standard install with no other plugins active. On line 1237 of that file is $truncate = substr($truncate, 0, $spacepos);, which doesn’t even indicate WP_Error is being used at all.

Are you on a localhost install, or a live server? What type of server is it?

Evan

This is on a live server, not local. Here is a link to phpinfo

https://grammardoktor.com/ptb.php

I upgraded to 4.1, same issue here on the “new announcement” page.

I have a multisite.

Hi Paul,

If you want to reach out to me via the contact form on my site I would be more than willing to take a look at what the issue may be, and get things patched up for you.

I am unable to reproduce the issue on my end, so I’m unsure of how to repair it.

You can reach me via the contact form on my site:
https://www.evan-herman.com/contact

Once I hear from you I’ll respond with what steps we can take to get things patched up for you.

Thanks,
Evan

You are not handling the WP_Error case that wp_get_remote() can return instead an array.

$response = wp_remote_get( 'https://netdna.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.css' );
$split_dat_response = explode( 'icons */' , $response['body'] );

And somehow a WP_Error object is returned and explode gets issues.

Thank you for the input dc5ala,

I’ll need to build in a way to handle WP_Error if an error is returned.

Thanks for that catch.

Evan

i dont understand why you mark the error as resolved

I set up just now a complete new instance, fresh 4.1 install on my server, https://www.bplaced.net and I get the exact same issue.

Gotwig,

First, this thread was started by Paul. Secondly, a few other users have reported the issue and I am actively working with them to get it resolved. Third, You left a fairly negative review without reaching out for support. Why are you seeking support now?

Evan

Because I had a bad experience, it didnt work in my instance. I upgraded my project for the plugin, it didnt work, you closed the bug report aka saying this issue is resolved when it fact its not, and also i tried to setup a fresh wordpress and it still doesnt run. it made me a bit frustrated, so i think it deserves a bad rating, speaking for my own experience with the plugin.

When the plugin works again, or you keep a bug report open to follow progress or something like this, my experience may change and I change my rating or make a new and better rating.

Please try to think from my side of things.

Alright, valid explanation.

To respond to that, I personally don’t like to provide support to users who give us a bad rating before reaching out with some form of explanation or request for support. I am very active and provide some of the best support on these forums.

From within Timeline Express itself there are multiple avenues to receive support. Seeing as you just decided it was best to leave the review then reach out for support leaves little room for sympathy.

Not only does this hurt the entire plugin review system that currently in place, it also shows that you aren’t willing to work with the developer to come to a reasonable solution and would rather leave a negative review on a plugin that is actively being developed and supported, for free mind you.

Best,
Evan

My experience is my experience, and I had a bad experience thats a fact ok… what else should I say? when it doesnt work, thats something very critical, I know that its free, all plugins from the wordpress plugin directory are GPL (and free as in beer afaik)
I also develop free software.

I still wonder where the problem is tracked, because this report has been marked as resolved.

What do you need to debug the issue, my php info?