Japh

Hey again Andy,

While this is fixed and working on my production server, I’m still getting the issue in dev… seems weird.

May be a slightly different issue even, actually…

This is the output I’m getting:

Warning: file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /vagrant/content/plugins/leadin/admin/leadin-admin.php on line 272

Warning: file_get_contents(https://dev.local/content/plugins/leadin/images/leadin-svg-icon.svg): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /vagrant/content/plugins/leadin/admin/leadin-admin.php on line 272

Warning: file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known in /vagrant/content/plugins/leadin/inc/class-leadin.php on line 79

Warning: file_get_contents(https://dev.local/content/plugins/leadin/images/leadin-svg-icon.svg): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /vagrant/content/plugins/leadin/inc/class-leadin.php on line 79

Any ideas? (Should I have opened a separate thread?)

Hi Andy,

That appears to have fixed it for me too! Thanks heaps ??

Cheers,
Japh

Thanks so much for the update, Andy! Great to know there’s a fix on the way, and all your hard work is definitely appreciated ??

I’m getting these same errors too. I’m not sure if it’s relevant or not, but at least in my case, there’s a symlink involved. My wp-content directory is symlinked.

None of my other plugins throw errors with this setup though.

It makes the wp-admin unusably slow, and considering it’s just for an icon, that’s pretty annoying ??

I wanted to find a fix before posting this, but it wasn’t immediately obvious as I don’t get the same error on my local dev setup.

btw, it didn’t used to fail. I’m wondering if it’s a compatibility issue with the current WP version.

I’m getting the same issue. It happens regardless of what the URLs are.

I’ve tried loads of combinations, including:

Source: /temporary
Target: /permanent

Source: /temporary
Target: https://wordpress.com

Source: https://japh.com.au/temporary
Target: https://wordpress.com

All fail with the error posted by the OP.

Hi @russellkhan,

As far as I’m aware, this plugin has been built specifically to work only with bbPress.

I wish I could help more, but really I have only contributed to this plugin in terms of minor bug fixes to get it working in my own context, which I submitted back to the plugin itself.

If you manage to troubleshoot more specifically, you’re welcome to send through a patch and I’ll look at committing it.

Hi @russellkhan,

I did, I made a few small changes to the plugin, which should now be available in the latest version.

If you can elaborate on what the problem you’re having is, what your setup is, and how to reproduce the problem, we can look at helping you fix it ??

Best of luck!

Hi Duckdany,

Can you please tell us what version of Stream you have installed (the latest is 1.4.6), and what version of PHP?

Thank you!
Japh

Hi Bart,

Thanks for reporting this! Would you mind telling us what other plugins you have installed and active?

Also, if possible, it’d be useful to see the HTML source code of the Dashboard page when this is happening. If you’re able to share that, it’d be best to paste it either into a Gist on GitHub or a site like pastie.org (rather than just pasting a huge chunk of HTML here in the forum).

Thanks again, and hopefully with your help we’ll have a fix soon!

Cheers,
Japh

Hi @phatjay,

If you need to get in touch with us, you can do so via the contact form on the Stream website: https://wp-stream.com/

Cheers,
Japh

Hi @apessoa,

Just coming back around to check on the status of this again for you.

Are you still having this problem with the latest update?

Thanks!
Japh

Thanks so much for your kind words, Tiago! We’re very pleased to hear that. We certainly do our best to ensure people get the support they need for Stream ??

For your reference: https://github.com/x-team/wp-stream/issues/518

Thanks for reporting this, John. I’ve logged an issue on the plugin’s GitHub repository, and we’ll get that fixed for the next version release.