Stuart Silvester

Thank you for letting us know, a fix for this issue should be included in an upcoming release.

Hello,
If you're talking about the Marketplace, you can only install resources that have been tested and validated for the version of Invision Community you are using.

Thank you for your report, the issue has been identified and should be fixed in an upcoming release.

It will be included in 4.7.1 at the earliest. The issue exists in 4.6.12 and 4.7 betas.

This is an issue with a third party application or plugin. Disabling those should fix the issue.

Hi,
My problems are solved (for PHP errors & repeated actions).
Thanks to the ticket opened by Jim. Support told me not to reproduce the problems. He suspected a possible problem with the server configuration, in particular the PHP modules. With this lead, I was able to investigate enabled modules to disable unnecessary modules that the IPS software does not use. I didn't think a PHP module could be responsible. 😵
 
If anyone has a similar problem, here are my active PHP modules.
Everything is working !
 
For 8 :
 
For 9 :
 

Sincerly,
ASIKOO

Thank you for letting us know, a fix for this issue should be included in an upcoming release.

Hi,
We're seeing an SSL error when trying to connect to your community, this is due to your server not supporting TLS 1.2 (it only supports TLS 1.3). Typically, servers should support a minimum of TLS 1.2 in addition to TLS 1.3 for maximum compatibility (older consumer devices may not be able to access your community either).
Your server administrator should be able to assist with this if you're not quite sure what it means.

This issue has been addressed in 4.7 as part of the subscription improvements that are available in the current betas.

I don't use Python, but it does look like your authentication header may not be formatted correctly. Don't forget basic headers are base64 encoded which your middleware typically does for you, but since you're building it yourself here, it's not the right format.
It looks like you could use auth=HTTPBasicAuth(user, password)
specifying the API key as the user, but I couldn't tell you if that would solve the issue.

The disable_function directive can only be set in the servers master php.ini, it cannot be changed in user/custom configuration files. It would be quite pointless from a security perspective if you could just disable it.
Disabling it for your own user only is also not effective, the problem with these functions being available on the server is that other users on the server may be able to use them to damage your community or breach your data. If this is a shared host, it would suggest that their server security may already be quite lax.

Thank you, this should be fixed in an upcoming release.

It looks like Matt fixed this recently in 4.7

Thank you for your report, this issue has been addressed for an upcoming release.

Thank you for letting us know, a fix for this issue is pending review and should be included in a future release.

Hi Simon,
Fields need to be structured as an array with the field ID as the key (you can find this in the URL when editing a field in the AdminCP).
CURLOPT_POSTFIELDS => [ 'author' => 2, 'fields[1]' => 'teststate', 'fields[2]' => 'testorg', 'fields[3]' => 'NameTest', 'fields[4]' => 'email@test.com' ] Something like this, but change those keys for the proper IDs

Thank you for your report, this issue has been addressed for an upcoming release.

Thank you, this will be fixed in an upcoming release.

It should work if you remove the  DEBUG_TEMPLATES constant from your constants.php file.
We're still working through the deprecation notices and those will be addressed in future (not 4.7.0) releases but they're not a problem for right now.

Thank you for your report, I have committed a potential fix for this issue that should be included in a future release.

Thank you for letting us know, I was able to reproduce the issue. I have created an internal bug report so we can fix this for an future release.
When you only allow a single file to be uploaded, the linked field is disabled however it isn't re-enabling when you delete the uploaded file.

It should work if you remove the  DEBUG_TEMPLATES constant from your constants.php file.
We're still working through the deprecation notices and those will be addressed in future (not 4.7.0) releases but they're not a problem for right now.

That error (and the one you're seeing on the activity stream) is caused by a third party application.
Error: Class "IPS\lyrics\Lyric" not found in /home/dir/public_html/applications/volunteer/sources/Opportunity/Comment.php:51 Stack trace: #0 /home/dir/public_html/system/Content/Content.php(1744): IPS\volunteer\Opportunity\_Comment::searchResultSnippet(Array, Array, Array, Array, Array, NULL, 'expanded') #1 /home/dir/public_html/system/Content/Search/Result/Content.php(94): IPS\_Content::searchResult(Array, Array, Array, Array, Array, NULL, true, 'expanded', false, false, NULL, Array) #2 /home/dir/public_html/system/Theme/Theme.php(880) : eval()'d code(3007): IPS\Content\Search\Result\_Content->html() #3 /home/dir/public_html/system/Theme/SandboxedTemplate.php(61): IPS\Theme\class_core_front_profile->profileActivity(Object(IPS\Member), Array, '\n<form accept-c...') #4 /home/dir/public_html/applications/core/modules/front/members/profile.php(304): IPS\Theme\_SandboxedTemplate->__call('profileActivity', Array) #5 /home/dir/public_html/system/Dispatcher/Controller.php(101): IPS\core\modules\front\members\_profile->manage() #6 /home/dir/public_html/applications/core/modules/front/members/profile.php(73): IPS\Dispatcher\_Controller->execute() #7 /home/dir/public_html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\members\_profile->execute() #8 /home/dir/public_html/index.php(13): IPS\_Dispatcher->run() #9 {main} You'll need to contact the author for the Volunteer app for assistance.

You would need to contact the author of your theme to update your theme to be compatible with the latest release of the platform.
If you use the filter on the theme templates page, you can filter for templates that have been modified. It will also tell you this on the upgrade warning. Note its not stopping you from upgrading, its simply warning you that they are modified and will be out of date when you upgrade, so you would need to update those manually.
There is a general guide on how to upgrade themes, which you can find in the following location, if you are doing this yourself
 

It sounds like you have sent an invoice for a new subscription, rather than selecting to renew. You need to be selecting "general renewal", or when creating a new invoice manually, you should be selecting the renewal option, and not the subscriptions option