Jump to content

Jim M

Invision Community Team
  • Posts

    8,398
  • Joined

  • Last visited

  • Days Won

    39

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Jim M

  1. PHP 8.2 is not supported. Only PHP 8.0 and 8.1 are at this time.
  2. ElasticSearch errors are still populating your system log as of now. Yes, you would need to make your database compatible prior to providing further support or this may cause other issues, including the performance issues you're seeing.
  3. You will want to check with your language pack author to ensure it is up to date.
  4. Facebook is continuing to make changes which are making it harder and harder for regular communities to continue this. If you cannot meet Facebook's requirement, I'm afraid, you have no other choice but to convert your users to the standard login which are using it and disable the Facebook login provider.
  5. CSP is available in the aforementioned place. Specific CORs headers would need to be reviewed by our Cloud team to be implemented on a custom basis. Once you purchase, you can submit a ticket and our Cloud team will evaluate your need.
  6. You will want to enable Status Updates which encompasses the public message feature on another user's profile.
  7. "Read Topics" permission will allow that group to read the topic so if that isn't what you want you would want to disable that permission. Then inside the forum that you want the groups that do not have "Read Topics" permission to be able to view a list of topics inside the forum but not read the topics, you would edit the forum and enable "Users without read permission can open forum?"
  8. You have non-InnoDB tables so I would advise first changing your database to InnoDB and then test again. You also have a significant number of errors getting generated from your ElasticSearch instance so I would ensure that it is running properly and not on the same server as that can cause performance issues.
  9. If it is a 500 Internal Server Error coming from your server, then it is not reaching the software. The error would be logged in your server error log unless your server configuration is not allowing it or incorrect log location. Otherwise, if there is an error in our software but the ACP is inaccessible, it will be logged in /uploads/logs.
  10. Please ensure that you have all patches applied in ACP -> Support. Then please ensure that you have provided us accurate ACP access and we can further investigate: We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you. Please also ensure you're not running PHP 8.2 or higher
  11. This wouldn't allow Guests to post, they would still have to register 😉
  12. Logos for your theme can be found in ACP -> Customization -> Themes -> edit theme -> Logos. For more information about our software, I would recommend reading our Help Guides: https://invisioncommunity.com/4guides/
  13. As mentioned in our reply to your ticket, it has been escalated to our advanced support team. Due to the advanced nature of your request, please note that it may take longer than usual to fully address your concern. Please also note that advanced support is only available Monday through Friday. I apologize in advance for this delay.
  14. That is in ACP > Members > Spam Prevention.
  15. Seems to be working fine for myself but you disabled CAPTCHA. However, you have a ton of ads on the page, if you're still running into issues, I would recommend disabling those.
  16. Would need to see on your own, as the URLs in your example are indeed present there 🙂
  17. I've tagged a developer to this to shed light on why Google is marking this as such. It is indeed valid schema.
  18. 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.
  19. 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.
  20. If this is the case, you would need to work with your theme's author to see why this is.
  21. As mentioned there, you would simply customize the "Send email when purchase will expire soon?" email as that email will replace the automatic one.
  22. Excellent. Glad to hear you found the issue. If it is one widely available, I'd recommend posting it here so others can be aware.
  23. Are you getting this with any post made to this endpoint or specifically with a certain request?
  24. If you go to /admin/upgrade and there are no upgrades available for you to run, you are all set.
×
×
  • Create New...