Daniel F

Does this happen only on specific pages or literally on every page?

1 hour ago, The Old Man said:

I tried out Zapeir a few weeks ago and gave up, it just wouldn't accept the provided credentials in the AdminCP. My free trial has since ended, but I wanted to see what was possible using their free service. In particular, I wanted simply to create an email, topic or PM message for when a member had a birthday or registration anniversary.

Hope you get it sorted.

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?

On 4/1/2023 at 11:09 PM, Afrodude said:

@Daniel F what is the best option to do that because I have been trying to do it, and I didn't succeed yet. 

I tried by forum ID etc and other available options, and still posting from everywhere.

Could you share a picture of your zap and the configuration?

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

You'll also need either a hook or a MemberACPProfileTabs extension to register the new block/tell the system where to show the block.

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 😂

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

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.

This seems to be a bug in iOS.

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

Sounds like there’s no free space left on your server. 

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. 

Yes, it is possible 

Sounds like an issue with the country flag 3rd party app.

Are you sure that the cron is set up correctly? We had many clients which were still linking to the old PHP binary instead of the new php8 binary.

This are the oAuth Scopes https://www.techlearnings.org/single-post/oauth-2-0-scopes-roles-grant-types

The form is quite confusing, I've filled a bug report to improve it. There's no need for all the whitespace between the left fields.

20 minutes ago, GazzaGarratt said:

does the notification automatically remove itself from the tray once clicked on, like all other push notifications for other stuff on mobiles? Reason I ask is because I notice the Android ones always stay on devices but not sure if thats down to software here or maybe browser specific e.g. Chrome?

Once the user added the community to his home screen and gave permissions for push notifications, it's treated like a real app and notifications are treated like any other IOS notification. They disappear once clicked and you can use all the OS features like Focus to control what appears when, and configure everything under the IOS Settings > Notifications

https://support.apple.com/en-us/HT201925

10 minutes ago, Adriano Faria said:

I thought there was a specific method in the extension for Push and I didn't want to waste time in the time I updated my resources so I disabled push.

Thanks.

Sorry, you're right, this requires the parse_mobile_..... method to work!

I'll see if we can simplify this, I don't think that we really need it for simple PWA notifications.

3 minutes ago, Randy Calvert said:

oooooOOOOOOooooo!  I'm excited to see this! 

That's the actual footage of me after the first successful push notification. And Stu was such a party crasher with his "welcome to 2018... I have them already working for years" comment:D 

1 minute ago, Adriano Faria said:

Push notifications should be supported in 3rd-party resources to make notifications from these resources to be available, right?

It's just a new "way" to deliver the notification.

As long as the Notification extension doesn't explicitly disallow Push via the config (that's the 'disabled' bit in the config array) and their browser supports it, they can use it.

This was probably a bug on your site then which was somehow resolved with the recent upgrade.

2 hours ago, media said:

Sorry, yes embedded content opens a new tab... 

How do you change that does not open new tab?

Are you sure that the links inside the embedded content were opening in the same tab for you?

I've checked our code and the file which modifies that the link opens in a new tab wasn't changed since 2019 and the part which adds the target was added back in 2017