Jump to content

Marc

Invision Community Team
  • Posts

    15,921
  • Joined

  • Last visited

  • Days Won

    277

 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 Marc

  1. It seems you blocked everyone there. The * is a wildcard character. So essentially an "Anything here". So for example, if you added 10.1.*.100 it would block 10.1.10.100, and 10.1.5446521551.100, but would not block 5.1.5.1. In your case, you added *, so said to block anything where the IP matches anything
  2. Could you please clarify, did you want me to go ahead with that?
  3. I would highly advise on following this up with our developer in your ticket and not touching anything beforehand.
  4. The software can only show locales it reads from your server environment. So if they are showing, they are indeed present. The same goes fr the locale not being accepted when being manually typed.
  5. If you create a ticket on this, I'll see what we can sort for you there 🙂
  6. In reality, if this is being an issue with multiple sites on multiple servers but all within your infrastructure, you need to speak to the person who controls that infrastructure. The reality is, if the licensing was down, we would know very very quickly from many many clients.
  7. For clarification here. 4.7.3 will break on PHP 7.4. If you have it running at present, this is actually very lucky, but there will be things on your site which are broken. Some of the code simply isnt compatible with anything less than php 8
  8. 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.
  9. I would assume it would run each rule against the relevant items. So if there are no rules to be run against them, they would just complete. I have however tagged devs to confirm this
  10. I have created a ticket for you on this, so we can look closer at the issue
  11. I would need an example of the items they cannot see, and the name of the users, so we can take a look for you.
  12. I have created a ticket on this for you, and someone will be in contact
  13. 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.
  14. No problem. Glad to hear you appear to have located the issue
  15. Could you provide a link to that item so I can take a look? (feel free to PM this if needed)
  16. System->Datalayer is what you would be looking for here, and indeed as mentioned, you would need to create one to suite your own needs with google tag manager
  17. This is not something I have seen happen on anyones site. I know that doesnt help you much, but it does point to the fact its very likely 3rd party
  18. The issue with your emails there, is that you appear to be emailing support, so they will automatically be rejected without a valid license. You would post here as you just have for support 🙂 In terms of the issue you are having, please PM me both your IP and the displayname on your trial site, and I can get that looked at for you no problem
  19. If you can provide me with an example, I can take a look for you to see if I can see why this is the case
  20. This is in the support section of commerce, for outgoing emails. I would advise checking there to ensure your configuration is correct
  21. Yes, you can keep the ranks and icons, and just import rules and badges
  22. Im not sure what that would achieve over them simply following the item?
  23. Any updates relating to version 5 will be announced within our blogs 🙂
  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. I have created a ticket for you on this, and someone will be in contact as soon as possible
×
×
  • Create New...