Jump to content

Ryan Ashbrook

Invision Community Team
  • Joined

  • Last visited

Everything posted by Ryan Ashbrook

  1. Ryan Ashbrook posted a post in a topic in Technical Problems
    This should be fixed now.
  2. To prevent abuse, Free Trials are limited to 10 emails per month. It seems you've hit that limit. Once the purchase is converted to a full package, that limit is removed.
  3. You need to either wait for the update check task to run, or manually check for updates under ACP > Applications.
  4. Yes, this is normal. FileZilla first tries to move into the directory and if it doesn't exist, automatically creates it, then tries to move into it again.
  5. I'll add clarification, but that's referring to after the initial upgrade to 5. Once the initial upgrade to 5 is done, you can then upgrade via the ACP as normal as new versions of 5 are released.
  6. Ryan Ashbrook posted a post in a topic in General Questions
    Admin CP > System > Advertisements > Advertisement Settings > Set custom ads.txt
  7. Existing trials created before today will not be updated, however new trials moving forward will use 5.0.0.
  8. For version 5, these will now be available in the download dialog.
  9. This has been fixed now.
  10. The error codes are mostly for our reference. If, for instance, there is a bug causing an error to show inadvertently (such as a user not allowed to view a topic, however all of their permissions say that they can), then it gives us an easy and direct starting point for debugging. This is why we recommend contacting support if a user is experiencing an error and you’re not sure how to resolve it - we can either instruct on what to do, determine if there is a bug, or sometimes even determine the experience resolving the issue can be improved in the software itself. For day to day cases, the error message that is displayed should suffice. As Marc said, in your specific example, that is a generic 404 page indicating a page does not exist in the software at all. The previous error code database really only contained the codes and the same message that was displayed or something generic like “user did not fill in all required fields”, with a few exceptions. In many cases, this is already handled within the software itself - if you encounter an error as an admin, it will sometimes give you instructions on what to check to resolve, if it’s relatively simple to do so (such as if there are no payment gateways set up). If a specific field is required, the form will not submit and tell the user, etc.
  11. It was changed to BIGINT.
  12. This should be fixed now. A couple days ago, Google Tag Manager was enabled, however the the GTM Body Snippet simply had <noscript> in it, which was causing the issue. I've adjusted that to <noscript></noscript>, which resolved the issue. Note, this isn't likely correct - if you are using Google Tag Manager, then there is additional code that needs to be added there. Unfortunately, that code is unique, so I cannot add it myself. Only the administrator of the site, with access to GTM, can do that.
  13. This should be fixed now.
  14. It was definitely a while ago, because mine is long again lol
  15. Sorry about that! This has been fixed.
  16. Computer, mobile phone, etc. Whatever the user is using to browse the site.
  17. I am not seeing this issue, currently - and wouldn't be related to the maintenance earlier. This appears to be newer emoji that are not supported on that device. Emoji are not static files (which is what the maintenance was pertaining to) but are actual characters.