Stuart Silvester

Hi and welcome to the wonderful world of Webhooks:)
Yes, this can be done with Zapier.
 
Yes, you'll need a Zapier Account.
 
Yes, you can use filters to set only specific forums, BUT this will require a Zapier Feature called "Filters", which is only available on paid Zapier plans.
we have a section with 3rd party service providers which can be hired for all kind of tasks 
https://invisioncommunity.com/third-party/providers/
 

We currently have a ticket for this issue reported by another customer. We're currently looking into it.

Hi,
We're aware of the issue and we're currently working on correcting it.

Hi Paweł,
We are in the process of migrating to a minimum PHP version of PHP8, and this means that one or more 3rd party add ons contain code that can break on PHP8. For more info see our August Developer Blog.
Cheers!

The problem is that you're using a forward slash as a table prefix and as such it's part of the table name. 
I would recommend renaming the tables to remove the / and then edit conf_global.php and change 
'sql_tbl_prefix' => '/', to
'sql_tbl_prefix' => '', Then go back to <url>/admin/upgrade to finish the upgrade.

Thanks for letting us know, these issues should be fixed now.

Thanks for letting us know, these issues should be fixed now.

The problem is that you're using a forward slash as a table prefix and as such it's part of the table name. 
I would recommend renaming the tables to remove the / and then edit conf_global.php and change 
'sql_tbl_prefix' => '/', to
'sql_tbl_prefix' => '', Then go back to <url>/admin/upgrade to finish the upgrade.

Forcing passwords to expire is generally considered a bad security practise now. Enforcing it may actually reduce the security of your member accounts instead of increasing it.
Here are two useful resources, but you can find many more online.
https://www.ncsc.gov.uk/blog-post/problems-forcing-regular-password-expiry https://pages.nist.gov/800-63-3/sp800-63b.html#memsecretver
"Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator."  

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

I have created an internal bug report so we'll review it.

I have created an internal bug report so we'll review it.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

We've been looking further into this today, it appears that a bug "fix" in PHP 8.0.22 & 8.1.9 has caused some issues - https://bugs.php.net/bug.php?id=80047 
I suspect this unannounced breaking change may cause issues in other software packages. The bug report suggests this change was actually intended for PHP 8.2 but was committed to 8.0/8.1 anyway.
We're working on a solution. I do not know at this time whether PHP might roll it back in the next release or not so we'll do something to work with either situation.

This is not an IPS bug. It’s a bug within PHP itself. Meaning you could have had a perfectly working installation and then upgraded your version of PHP and it magically broke without you doing any update. 

Even outside of that however ANY complex piece of software will have issues. There are literally hundreds of thousands of interdependencies and it is impossible to test them all without doing releases only every few years. Even then you’ll miss stuff. Look at major operating systems for example. 
This is one of the reasons to use software that is well supported and maintained. 

It looks like you may have an issue with your JS loading. Try going to AdminCP > Support > click clear caches.
Hopefully everything should start working after that.

We've been looking further into this today, it appears that a bug "fix" in PHP 8.0.22 & 8.1.9 has caused some issues - https://bugs.php.net/bug.php?id=80047 
I suspect this unannounced breaking change may cause issues in other software packages. The bug report suggests this change was actually intended for PHP 8.2 but was committed to 8.0/8.1 anyway.
We're working on a solution. I do not know at this time whether PHP might roll it back in the next release or not so we'll do something to work with either situation.

Hey @D-Trox
This is an issue specific to PHP 8.1 and we've got a fix coming for it in an upcoming release.

We've been looking further into this today, it appears that a bug "fix" in PHP 8.0.22 & 8.1.9 has caused some issues - https://bugs.php.net/bug.php?id=80047 
I suspect this unannounced breaking change may cause issues in other software packages. The bug report suggests this change was actually intended for PHP 8.2 but was committed to 8.0/8.1 anyway.
We're working on a solution. I do not know at this time whether PHP might roll it back in the next release or not so we'll do something to work with either situation.

Hey @D-Trox
This is an issue specific to PHP 8.1 and we've got a fix coming for it in an upcoming release.