Daniel F

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

It's save to ignore it!

Looking at my sites, it seems like spammers are already using it. I get more and more replies to old topics which somehow are on topic but still somehow make so little sense that I can’t believe a human registered to post it. 
I’m not afraid of AI and use it myself, but only like a brainstorming partner, where I judge which replies are actually useful and correct. I can’t imagine having AI (auto) reply/publish anything on my sites at the moment. And I think it would only dilute the value of a community. Because the AI answers will soon be available directly within search engines and other apps and services. I rather run the place where answers can be different and better than that. 

I'm using https://www.boxfactura.com/pulltorefresh.js/ on one of my sites and really like it.

There’s a great way to utilize the cloudflare workers for the guest page counts, so that the page count is increased even if the guest gets only the cached page and the original request never makes it to your own server. 
It’s going to take some time, but I’ll share the instructions ( or app) in few weeks 

We'll have a blog entry about some exciting news soon, until then I can confirm that this was implemented as part of a bigger project for an upcoming release 🙂

I have created a ticket to investigate this further.

I understood that and took that into account. I am still saying it is usually useful to create a custom version of the core block first and then call it with the custom key. That’s also gives easy access to the settings that these core blocks might have. You could even add small customizations easily without touching the original widgets. 

It changed my email flow.. LESS EMAILS in my mailbox! :D

Thanks, I guess that's why the first ticket and also my direct email in february failed.
Anyway,, I have created a ticket which I'll work on today and hopefully you'll also get a reply later today.
 

It changed my email flow.. LESS EMAILS in my mailbox! :D

Some strings are intentionally empty!
Our framework expects that some strings exist for e.g. tables and permission columns and if it doesn't make sense to have any text shown there, we'll just leave it empty.
 

Some strings are intentionally empty!
Our framework expects that some strings exist for e.g. tables and permission columns and if it doesn't make sense to have any text shown there, we'll just leave it empty.
 

You can change it in your ACP while editing the record there.

Could you clarify what you mean by the credentials in the ACP?
There's nothing to do in your ACP except to "enable it" and to copy the URL and REST API Key into Zapier. Is this the step that failed?

We hope to provide a preview pretty soon. For our first release we are going to keep this pretty simple and then get feedback from clients on how you want it to evolve.

The error means that the post content is missing.

This was just the first quick implementation after they finally implemented it into iOS 16.4
There‘s a lot on our list for the next release(s).
I also hope that Apple will fix their bugs sooner than later here 😂

You can use Zapier conditions https://help.zapier.com/hc/en-us/articles/8496276332557-Add-conditions-to-Zaps-with-filters to control this.

Sounds like a member with an invalid/not existing member group.
i have logged a bug report for this because even if it’s not a bug per se, it shouldn’t break the api output. 

The amount of available member groups is causing the issue. I have logged a bug for this. 

Just for reference since this question came up again by somebody linking to this topic:
This is the custom redirect rule which you need for nginx for the API folder URL redirect:
location /api/ { if (!-e $request_filename){ rewrite ^/api/(.*)$ /api/index.php; } } Thanks to @Chris027 for sharing this a while ago.
 

@Stuart Silvester found this this in the webkit bugtracker https://bugs.webkit.org/show_bug.cgi?id=252544#c18

This seems to be a bug in iOS.