Page 1 of 1

WordPress: Supplied resource is not a valid Stream resource

PostPosted: December 31st, 2013, 9:07 pm
by JCKödel
When updating (or installing) the latest version of WordPress (and compiling it), some pages throws the following warnings (after a huge amount of time), specially plugins and update pages:

Warning: stream_set_timeout(): Supplied resource is not a valid Stream resource.

Warning: Supplied resource is not a valid Stream resource.

Warning: feof(): Supplied resource is not a valid Stream resource.

Warning: fread(): Supplied resource is not a valid Stream resource.

Warning: feof(): Supplied resource is not a valid Stream resource.

Warning: fread(): Supplied resource is not a valid Stream resource.

... thousands of above


Some help? =)

Re: WordPress: Supplied resource is not a valid Stream resou

PostPosted: January 2nd, 2014, 5:00 pm
by Jakub Misek
Yes, there is some missing functionality about streams, and new WordPress started to make use of them...

Re: WordPress: Supplied resource is not a valid Stream resou

PostPosted: January 2nd, 2014, 5:27 pm
by JCKödel
There is a milestone for those functionalities?
We´re currently implementing a C# service on top of a wordpress site on Azure for a brazilian Bank and we´re checking some CMSes systems to do so.
As our customer already have wp, phalanger would be a nice fit.

Re: WordPress: Supplied resource is not a valid Stream resou

PostPosted: January 6th, 2014, 5:59 pm
by Jakub Misek
There is no ETA for now. We have this as a low priority feature, as we don't need it so far. Older WP works fine since it does not use streams.

We can take better look and let you know what exactly has to be implemented.

Thanks,

Re: WordPress: Supplied resource is not a valid Stream resou

PostPosted: January 30th, 2014, 4:00 am
by htpc2good4u
It's been about a month...is there an ETA yet? I upgraded WordPress on my site, and now I can't access ANY of the admin pages because they all utilize streams.

While I love the speed increase of running this on the .NET Framework...if I have to cross my fingers every time I upgrade WordPress and hope it won't crash like this...I'll go back to the standard PHP interpreter.