Daniel F

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

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.

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

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.

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.

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

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

Do you have any examples? 3rd party apps and plugins should really clean up their data while their deletion.

You could use an additional editor field where you’ll post only the related content links.

What are you missing most?

It’s not that simple because we’re using here a tree element and not a table for the output.

The "Member Edited" trigger is fired when literally anything except when one of these values changes ( 'last_visit','last_activity', 'profilesync_lastsync' ) So yea, your observation is correct. It is also fired when somebody replies because his "total posts" count, last post timestamp, and probably also his achievement points value changed. We thought that people would use Zapier Conditions once they need more control over the data, that said, we may improve this in the future and include a few filters into the "Member Edited" trigger. Also, something to keep in mind, is that the webhooks aren't fired immediately. We have a webhook queue, which collects the data and which is then fired via a separate request ( https://zapier.com/engineering/webhook-design/ leaving this link here for people who are interested in this) Since you're on a demo that has probably not really that many visitors, the queue is also not running as often as it would on a live board!

There was a bug in the edit action which was fixed yesterday. The new version is rolled out slowly, so to avoid waiting, I would suggest to delete the zap and create a new one , which will ensure that you’ll use the newest version.

Make sure that the datastore directory is writable and verify the paths in the conf_global & constants.php are correct

This one https://apps.apple.com/us/app/api-tester-rest-http-client/id1575521212 ? Just want to test it myself.

There’s also an app in the marketplace which sounds like it could accomplish what you need.

It's really up to you and the way how your client works. E.g. a CLI application/script will probably not be able to use the first 2 options, so you'll want one of the latter two. What exactly is being blocked? Do you see any errors in the API log? Is the Token expiring? Are you trying to refresh it?

Just to clarify, this is the default member group, the one which is in the conf_global.php file.

There's no way to hide them! The group setting controls only if the group name will be exposed in the public, but it doesn't control if the members are shown or not. Edit: I think I misunderstood your question. Is this a 3rd party widget? Our widget doesn't include the groups

Yes, it's working. Here's my php version of a quick test: // LEt's do it step by step to make it easier for others to see what's going on $img = __DIR__.'/applications/core/interface/giphy/logo.png'; // get the contents of the image $content = file_get_contents( $img); // encode it $content = base64_encode( $content); var_dump( \IPS\Http\Url::external( $communityUrl . "api/index.php?gallery/images" )->request()->login( $key, "" )->post( array( 'category' => 1, 'author' => 1, 'caption' => '<p>Testing API</p>', 'filename' => "my_img.png", 'image' => $content ) )->decodeJson() ); You could upload it to your community root directory after adjusting the URL,API Key and category variable to test it on your installation.

Thx, I thought you were trying to access our admin directory 🤨 Sorry for this. It should be resolved now.

403 is a no permission error, which is correct because you have no permission to access our admin directory.

Thanks, I have fixed this for an upcoming release.

This would be the code but I'm not sure what you mean with postID. There's no separate page with a post, only topics, so I assumed you mean the topic id which I used in my code. {{if !isset( \IPS\Output::i()->metaTags['og:image'] )}} {{$shareLogos = \IPS\Settings::i()->icons_sharer_logo ? json_decode( \IPS\Settings::i()->icons_sharer_logo, true ) : array();}} {{foreach $shareLogos as $logo}} <meta property="og:image" content="{file="$logo" extension="core_Icons" scheme="full"}"> {{endforeach}} {{elseif \IPS\Request::i()->app == 'forums' AND \IPS\Request::i()->controller == 'topic'}} {{$id = \IPS\Request::i()->id;}} <meta property='og:image' content='https://www.domain.tld/img/{$id}.jpg'/> {{else}} <meta property='og:image' content='https://www.domain.tld/standardimage.jpg'/> {{endif}} That said, I'm also not sure if it will work at all, the condition looks weird and will probably always return the first part for topics.