ASIKOO

I have exactly the same thing as you. On my side, it is not up to the forum to generate this special data. Eventually, the PHP code could be replaced by a wget in javascript (if the URL is not sensitive), not yet tested. With the removal of custom PHP, editing of post source code and custom ad placements, I will not be migrating to IPS 5...

Okay, you can start the beta, I'm here now! 😎🤣

The "+" feature isn't just for gmail, but with gmail, a.b.c@gmail.com = abc@gmail.com, ab.c = abc etc...

Maybe this can help you, If you have uBlock Origin, disable it for your website. I have this problem because uBlock Origin considers the area to be an advertisement.

This might help you.

I like this teaser, looking forward to discovering this new modern forum view and the theme editor seems awesome

Hi, I migrated to the new terms because it is much more interesting for me. But, I didn't see it in this thread (or else I'm blind) -> Although the archive to download does contain all the applications mentioned, it's a bit confusing to be able to "repurchase" the applications with the new terms 😅 Just to mention it to you, if this is a small oversight in the customer area 😆

Ooupsi, thx 😅

Hi, @Matt Downloads app isn't included (I have this application in my current license) ?

I confirm, it works better haha

I didn't think to use http_build_query() for this, indeed it works with. Unlike you, I used (as it worked with the other APIs by IPS, I didn't ask myself any questions...) curl_setopt($ch, CURLOPT_POSTFIELDS, $post); Thank you @Nathan Explosion Orignal code $api = "https://domain.example/api/core/messages"; $key = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx'; $post = [ 'from' => 26583, // Bot Account 'to' => [ 17997, 26105, 22505 ], // Staff 'title' => 'title of private message', 'body' => 'send by api', ]; $ch = curl_init(); curl_setopt($ch, CURLOPT_URL, $api); curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); curl_setopt($ch, CURLOPT_USERPWD, $key); curl_setopt($ch, CURLOPT_USERAGENT, 'Core X'); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_POSTFIELDS, $post); $result = curl_exec($ch); $status = curl_getinfo($ch, CURLINFO_HTTP_CODE); $curl = json_decode($result); curl_close($ch); var_dump($result);

Ahah, no problem 🙂 if it helps, to try to understand... \IPS\Request::i()->to is considered as string according to gettype();, so the script fails is_array() check. I forced hard in the code, to test and it works, PM is send (of course I restored the original file) 😄

There are 2 lines for the "to" parameter. I tested with 1 user id then I commented it in the code, I wanted to send a private message to several members during my test. 'to' => [17997,26105,22505], // Staff

Hi, I wanted to test the API to send a private message, I think it doesn't work? I don't understand the error, it seems correct according to the documentation, is it a software problem? No error message in IPS logs. Parameters $post = [ 'from' => 26583, // Bot Account 'to' => [17997,26105,22505], // Staff //'to' => [22505], 'title' => 'title of private message', 'body' => 'send by api', ]; Dump test.php:52:string '{ "errorCode": "1C374\/3", "errorMessage": "INVALID_RECIPIENT" }' (length=72) Sincerly, ASIKOO

Is the software compatible with PHP 8.2?