Jump to content

Marc

Invision Community Team
  • Posts

    14,983
  • Joined

  • Last visited

  • Days Won

    263

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Forums

Events

Store

Gallery

Everything posted by Marc

  1. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  2. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  3. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  4. Any requirements are shown on our requirement checker here. What you should do is switch to 8.0 and run the requirement checker file. This will then inform you of anyhting in which is required that is missing https://invisioncommunity.com/files/file/7046-invision-community-requirements-checker/
  5. It will depend on the browser in which you are looking at it on. With it being a MOV file, I would assume you are looking on an iPhone, as it's an apple format
  6. 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.
  7. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  8. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  9. Are you still seeing issues on this @Ocean West ? This should actually now be resolved, so will need to open a separate report if you are still seeing problems. From what you described there, it doesnt actually sound like the same problem
  10. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  11. Could I ask if you have tested this with cloudflare taken out of the equation? Also, are you seeing any other messages on stripe? I ask as I note there was at least one that failed there
  12. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  13. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  14. 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.
  15. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  16. This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
  17. This topic was from 5 months ago 🙂 Just pointing out in case you hadnt noticed
  18. You had an empty string on your conf_global that was causing this on the following constant. This was resolved by my colleague in the ticket to get your site online. $_INFO['board_start']
  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. Thank you very much for your feedback there. Its very much appreciated, and Im sure some will find this helpful. We do indeed have on our list to sort out some documentation on how to get this set up with GA4. With the items you wish to see in the future, please post these up within the suggestions area of our community, which is where we would pick these up.
  21. As mentioned by my colleague, at present this is a known limitation rather than a bug. There is no resolution for this at the present time.
  22. You would need to review the html, as something in there is breaking the layout of the page unfortunately. Usually this is the result of a stray tag or similar
  23. I have tagged our developers on this to see if they can advise
  24. I have created a ticket on this for you, so we can get it looked into further.
×
×
  • Create New...