Stuart Silvester

Yes, more than two.

Hi Christian, 
`login()` is analogous to HTTP Basic Auth.
public function login( string $username, string $password ): static { curl_setopt_array( $this->curl, array( CURLOPT_HTTPAUTH => CURLAUTH_BASIC, CURLOPT_USERPWD => "{$username}:{$password}" ) ); return $this; } We'll update the documentation to have a non-framework example.

PHP recently pushed out some updates (8.0.17 and 8.1.4) that are causing issues in several PHP projects when zlib compression is enabled in php.ini. The best work around at the moment is to disable zlib compression on your server, or ask your host to if you cannot.
Further discussion is here: https://invisioncommunity.com/forums/topic/466401-my-community-is-offline-again-nothing-renders-onscreen-err_content_decoding_failed/
 

Hi,
I wanted to clarify the process for any critical updates you may need to make that may potentially need a higher priority when it comes to a review. A critical issue would be something that causes a large impacting issue to your resource, such as a fatal error that prevents it from working.
Submit the new version of your resource with only the fix for the issue, no other bug fixes or enhancements. Specify in the change log what the fix is for (so it's obvious to us what you are fixing). Submit a support ticket asking for an expedited review. Asking for an expedited review doesn't guarantee we'll be able to do it, but we'll try our best where possible.
Thank you!
Stuart

I was always convinced internet @Charles was an AI bot.

There's no bug here, changing the data that the Gateway/API references is going to cause problems. That goes for any gateway if you're changing something material such as the data source or account IDs.

This issue was being caused by the payment gateway trying to use customer data from Stripe's test mode on the live gateway.
It's always a good idea remove the gateway that was used for the Stripe test mode during set up and create a new one for live transactions.

This issue was being caused by the payment gateway trying to use customer data from Stripe's test mode on the live gateway.
It's always a good idea remove the gateway that was used for the Stripe test mode during set up and create a new one for live transactions.

It's not separate at all, The apps are the same regardless whether they're self hosted or not.
This warning is most certainly for classic self-hosted and not our platform too, it's telling you that the server you're using is potentially insecure. Not just from your account on the server, but potentially other accounts on the server may be able to use these functions to access your data. It's something that needs securing properly to protect your data.

It's not separate at all, The apps are the same regardless whether they're self hosted or not.
This warning is most certainly for classic self-hosted and not our platform too, it's telling you that the server you're using is potentially insecure. Not just from your account on the server, but potentially other accounts on the server may be able to use these functions to access your data. It's something that needs securing properly to protect your data.

I'm going to move this to a ticket so we can investigate further. Please keep an eye on your email for further updates.

Sure you can go ahead and do it, but sit on releasing it until you have something meaningful to include. Whether that be bug fixes or enhancements. Releasing only this change is a waste of time for our reviewers and for customers.

Sure you can go ahead and do it, but sit on releasing it until you have something meaningful to include. Whether that be bug fixes or enhancements. Releasing only this change is a waste of time for our reviewers and for customers.

Thanks. The warning is gone in my account here.

We made a patch available earlier today that fixes this issue. If you are using an affected version of 4.7.9, it can be obtained from the AdminCP > System > Support page (top left box will tell you if there is a patch or update available)

We made a patch available earlier today that fixes this issue. If you are using an affected version of 4.7.9, it can be obtained from the AdminCP > System > Support page (top left box will tell you if there is a patch or update available)

We're looking into it!

We made a patch available earlier today that fixes this issue. If you are using an affected version of 4.7.9, it can be obtained from the AdminCP > System > Support page (top left box will tell you if there is a patch or update available)

We made a patch available earlier today that fixes this issue. If you are using an affected version of 4.7.9, it can be obtained from the AdminCP > System > Support page (top left box will tell you if there is a patch or update available)

We made a patch available earlier today that fixes this issue. If you are using an affected version of 4.7.9, it can be obtained from the AdminCP > System > Support page (top left box will tell you if there is a patch or update available)

We do not have support for the Badging API at this time, likely to be something we add in a future version though.

I would recommend emailing the accounts department about billing queries: https://invisioncommunity.com/contact-us

I would recommend emailing the accounts department about billing queries: https://invisioncommunity.com/contact-us

No, I would recommend finding a new host that doesn't have arbitrary limits on database size. (it has never made sense to me)

I have created a bug report, I'll look into this.