Jump to content

Jim M

Invision Community Team
  • Posts

    9,611
  • Joined

  • Days Won

    47

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Jim M

  1. 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.
  2. May I ask the reason for the change? Keep in mind that you can only have 1 Test URL.
  3. You would also want to check third party applications and switch to an unmodified theme. It may not be just a plugin.
  4. Thank you for providing a member. I will keep that hidden so that it is not exposed publicly. Your Members group does not have access to Clubs so would not see anything. Their permissions in ACP -> System -> Applications -> expand System -> Clubs is disabled.
  5. Could you please provide an example member's display name or ID who cannot see it? We can then assist you.
  6. This has been done for you now. Please let us know if we can be of further assistance.
  7. Anything security enhanced may be blocking it. I would check your server logs and consult with your server administrator to temporarily disable it or whitelist the subdomain.
  8. This fix still needs to be reviewed by our processes but it is estimated for 4.7.17 so likely the April release.
  9. Invision Community 4.7 will not run on anything less than PHP 8.0 or anything higher than PHP 8.1. I would first ensure that PHP is set to either 8.0 or 8.1 and you have all required extensions/modules:
  10. Please rebuild it and let us know once it is done.
  11. Thank you. I do not see that the search index was rebuilt there. Could you please perform that first before we troubleshoot?
  12. Would recommend reading through our help guides and asking any questions you may have:
  13. The .32 and .142 are still valid.
  14. That would not be something which we can provide.
  15. You can add these to the notes section of the access details are of the Client Area. That way all technicians who need to assist you can access 🙂 .
  16. This would be outside our scope of support, I'm afraid. As manual URLs are handled differently and not associated in the software, it isn't really something the software is set to handle when the URL changes. A third party provider may be able to assist you with this custom update, if you wish.
  17. Glad to hear that they found the issue!
  18. As Randy mentioned, you’ll want to check those images to see if they’re attached. If they aren’t, more than not they were copied/pasted by URL so the system simply wouldn’t know of them.
  19. If you'd like to share the user, topic you're expecting, and search term we can take a closer look for you 🙂 . Otherwise, we're at a stalemate moving forward, I'm afraid.
  20. If you have permissions set correctly so that they can view top -> down each forum category, forum, topic, etc... then I would try rebuild your search index. Maybe something is wrong but if you continue to see a search for the same term available on one account but not another, we would need to review that further with the term, the accounts, and the topic(s) you believe they should see.
  21. I'm a little confused, you stated that they don't have access to read the forum and therefore don't have access to the topic. Could you please clarify?
  22. If they can't read the topic, they can't search for the topic currently. Search would search content and show snippets so may expose information you don't want those who don't have access to see. You can suggest a change to this in our Feedback forum 🙂 .
  23. I have pinged our developer team to get an exact answer here. However, it should be in a coming release. Got an answer. This is indeed in our upcoming here and currently is in 4.7.16 Beta 3.
  24. 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.
  25. Thanks! I have opened a bug report for this internally for our developers to test further and investigate.
×
×
  • Create New...