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. I understand the feature request there, and there are technical reasons its not that way at present. I would ask however, if they are for applications, wouldnt you be best to just rename the field to "Full name" or something similar?
  2. You are showing localhost on your screenshots, and have stated you wont provide other details. If you can provide information, we can certainly look
  3. No problem, and good luck with the upgrade
  4. Thank you. I have attached that here, hidden, so my colleagues can see the issue in action. To be honest, personally I cant see how we could affect that, however of course Im not one of the developers
  5. Unfortunately, the only thing I can suggest at present is upgrading. There has simply been too much change to be trying to manually change items with code from today's release. There will have been thousands of bug fixes since that point in time, and quite a few major changes to the way things work
  6. I think you have probably answered your own question there. They need to upgrade to the latest release of the platform. The reality is, they are using a version that was released in 2019
  7. 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.
  8. I have created a ticket on this, as if its not even showing the new locations, something isnt correct. Someone will be in contact as soon as possible
  9. Could you please let us know the next time you have one of these, and take note of the details there, then let us know. We would need this in order to proceed
  10. 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.
  11. Sorry, it appears this may have been missed for some reason. I have gone ahead and got a bug report created on this for you.
  12. I have created a ticket on this, so we can take a closer look. Someone will be in contact as soon as possible
  13. Unfortunately, its difficult to know what could be causing the issue without being able to see it. What you mention above, would actually also point to it being an issue with permissions, as the logs folder would generally contain the error
  14. Ive created a ticket so we can take a look at this for you
  15. As mentioned, the second item you would add as a suggestion. The latter you have stated you won't go into detail on, so I'm not sure what we can do to assist you unfortunately.
  16. 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.
  17. Glad to hear you got that resolved 🙂
  18. The likelihood is, something isnt able to be written somewhere, so check permissions on folders. You may also find errors logged in uploads/logs that will give you a better understanding. Clearing the datastore folder is another thing you could try
  19. 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.
  20. The update is already available. If you upgrade, you shouldnt ned to change anything if you already have authy in place. It should just work.
  21. Sorry, we would need more information. We need to know when it was scheduled for, when it actually showed, and an example user it was showing to before published (along with where it was actually showing).
  22. Now you have done, go to support in the admin CP and see if there are any issues showing under the mysql section. If there are, I would advise on resolving those to prevent issues in the future
  23. Try running clear cache in the admin CP and see if that corrects the issue.
  24. Please respond via the ticket, rather than here in a topic, as the person dealing with your ticket may not immediately see this
×
×
  • Create New...