ctotogo

I finally had a chance to test this.

Unfortunately, now the form doesn’t render at all, so I reverted to 3.2.1.

The form in question which was an application for Federal COVID grant funding has closed, so it’s not essential that I solve it for this form. I will try your version 4.x whenever our next form need arises.

That said, I’m happy to help you test this further. Was thinking of creating a new form for testing purpose to see if the problem exists on forms built *with* 4.x in the first place. If you think that will help that is. LMK

=== Carlos

Sure, I’ll do that this evening and let you know. Thanks.

Oh, and let me add that I checked the JavaScript console in Chrome while on the page and there aren’t any errors.

Hi —

Thanks for the reply. Yes, it’s enabled, but the issue persists.

Thanks for the reply.

As a suggestion, maybe it would be worthwhile for you to add hooks for developers to inject posts into the mix and/or modifying other aspects of the plugin’s behavior without having to provide for every custom request yourselves.

Thanks again.

Thanks for he reply.

I’ve both settings on the CSS (internal and external) and both settings on the preloading style, and cleared caching, none of it changing the results. Most of the blocks work fine, but the example I mention isn’t.

I have a test page (with the example above) at https://coppercourier.com/test-page with a password of ‘test’ — it’s just a test page we’re experimenting with.

Thanks for your help.

Hi —

Thanks for the great plugin. I’m wondering if there’s any news on this matter. We’re using AMP for WP and it’s definitely not working with it. As a result we’re only able to experiment with it and not deploy it. Happy to pay for a pro version if/when that becomes available.

Regards,
Carlos

I finally gave up on Stream. It went from those infuriating timeouts to just returning no results, then it said there was an error connecting to my account and to remove the connection and connect again, but when I tried that it came back with “There was a problem verifying your site with Stream. Please try again later.” I was able to delete my subscription, but it won’t let me delete my site — when I type in the site URL in your delete confirmation dialog box, it says the site doesn’t exist, but it does, and I’m typing it in correctly. So I just threw my hands up and cursed for 2-1/2 minutes in Spanish. Keep the $2.

With all due respect, Frankie, since you moved it to the cloud it doesn’t work properly. I can live with log data from most sites I work on living in the cloud, but the timeout errors make it infuriating to use. On Twitter yesterday you address the problem with: “Looks like some small Amazon teething issues. Should be back to normal shortly.” Clearly that’s *not* the case.

I overrid the silly 5 second WordPress default to http_request_timeout with:

function op_http_request_timeout($time) {
return 10;
}
add_filter(‘http_request_timeout’, ‘op_http_request_timeout’);

… and that helped yesterday. Today it’s not. I set it up to 30 seconds and it still generates the “Stream API Timeout” error (“30001” as a result of my tweak. So I set it to 60 seconds, and the script actually terminates unceremoniously because PHP/Apache max_execution_time is also 60 seconds. So I set them both to 5 minutes and it’s *still failing* — it doesn’t appear your servers are responding at all.

Regards,
Carlos