Jump to content

Jim M

Invision Community Team
  • Posts

    8,181
  • Joined

  • Last visited

  • Days Won

    38

 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. V3 was the wild, wild west. It was solely on Facebook to go to your website and grab a random image. The image may not even have been related to your topic, it could have been someone's profile photo, an ad, etc... It was pure luck that you were able to get it to be something related to your topic 😉 . V4, we changed this so we are now suggesting a photo to Facebook (and others) via OpenGraph to grab this photo. Typically, it is the first attached image in the topic, otherwise, it will fallback to the default sharer image. There may be third party plugins out there which may allow you to have better control if this is something you desire. However, this is not something which we support.
  2. I have not seen this happen on your community in over 10 minutes now. I will keep my eye on it but it looks like it has been resolved.
  3. I'm assuming you setup this email to receive contact us requests? Thus, this is the system verifying the email before sending you the contact request. This is not the user that sent the request.
  4. Sorry, it is a little confusing as email verification and the Contact Us form are two separate things. Also, the link you provide there has keys present which are specific to an instance of an email verification. It sounds like the user has attempted to register or change their email address and receive the email verification email which is correct and not "spam" as you're stating. To prevent further confusion, could you please share a screenshot of the email?
  5. May be best to reach out to the user and ask their steps of logging in or registering to get to that point.
  6. Anti-Fraud rules would apply to all payment methods.
  7. Are you stating that Commerce is placing the transaction in manual approval status or you stating it is in manual approval status in PayPal? If the former, I would suggest checking your fraud review rules in ACP -> Commerce -> Payments -> Settings -> Anti-Fraud Rules.
  8. I was able to upload when the system redirected on the error. Which is likely what you saw there with the cars. Unfortunately, we do not provide support for BackBlaze so this would be outside our scope of support if you continue to use them.
  9. While ACP is working now, I am not able to connect via FTP provided now.
  10. I'm afraid, the credentials are still invalid for the ACP.
  11. Dear users living in the past, please be made aware of this. Love, Administrators. -------- 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.
  12. 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.
  13. You would disable the third party party application or plugin in ACP -> System -> Applications or ACP -> System -> Plugins.
  14. You will want to disable those third party hooks listed at the bottom there.
  15. were you able to perform the upgrade and are you on PHP 8.0 or PHP 8.1?
  16. Would ask what was done prior to encountering this? You would want to contact your server administrator or hosting provider to pull that 500 Internal Server Error for you.
  17. You would need to contact your hosting provider if this is not available to you in your hosting panel. It may be it is not enabled but you would need to check with them.
  18. PHP 8.2 is not supported. Only PHP 8.0 and 8.1 are at this time.
  19. 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.
  20. You will want to check with your language pack author to ensure it is up to date.
  21. 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.
  22. 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.
  23. You will want to enable Status Updates which encompasses the public message feature on another user's profile.
  24. "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?"
×
×
  • Create New...