Luke Carbis

Hi Circlecube,

With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration.

It would be great if you could test it out, and let me know how you go. If you like it, please consider changing your review.

Also, we do have a roadmap now: https://github.com/xwp/stream-roadmap/

Thanks,
Luke

Hi Barneskr,

With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration. That means you won’t get any “can’t connect to Stream” errors anymore.

It would be great if you could test it out, and let me know how you go. If you like it, please consider changing your review.

Thanks,
Luke

Hi Correiar,

I’m sorry that you experienced those problems with your upgrade. We’ve come a long way since then.

With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration.

It would be great if you could test it out, and let me know how you go. If you like it, please consider changing your review.

Thanks,
Luke

Hi sylviabass,

Thanks for your feedback. With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration. I believe it should be fully HIPAA compliant.

It would be great if you could test it out, and let me know how you go. If you like it, please consider changing your review.

Thanks,
Luke

Hi fox7,

With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration. I believe it should be fully HIPAA compliant.

It would be great if you could test it out, and let me know how you go. If you like it, please consider changing your review.

Thanks,
Luke

Hey eirlymeyer,

Thanks for your feedback. I’m sorry that Stream 2 made you so angry. With Stream 3.0, we’ve rethought the way we’re handling the records. Everything’s local now, nothing stored in the cloud and no registration.

It would be great if you could test it out, and let me know it’s acceptable to you. If you’re less disgusted with our plugin this time around, please consider changing your review.

Thanks,
Luke

Thanks for reporting the issue. Let’s continue the discussion on Github so that we don’t have to keep following up in multiple places.

Great! Thanks for sharing.

That’s very helpful, John – thanks. I’ll look into this also.

@thisismyway Who are you hosted with? I experienced a similar issue once during testing which turned out to be a problem with object caching. The install was on WP Engine, but many WordPress hosts use object caching.

Please try logging into your host and turning object caching off (if you have that option) before doing the migration, and see if that helps.

The other thing to try is this:

The migration is AJAX based, so in your browser inspector, try to find the XHR requests as they happen. Click on the request and see if there’s an error. I can give you more detailed instructions on how to do this if needed.

Could be. Once you figure it out, would you mind posting it as an issue here?
https://github.com/xwp/stream/issues/new

I’d love to get a fix out with 3.0.1.

I believe there is too. It’s going to be one of two focuses for Stream in the coming month (specifically ElasticSearch, though).

That’s really odd. I wonder if it’s related to this: https://github.com/xwp/stream/issues/729 (unlikely).

Can you try with all your other plugins temporarily disabled? See if that helps?

Was it a 500 internal server error on your site, or in the migration window (which would be connecting to the Stream cloud)?

Hi Jason,

That’s really strange. A 500 Internal Server error is indicative of the Stream servers experiencing some downtime.

Could you try again now, and let me know how you go?