Jump to content

Ryan Ashbrook

Invision Community Team
  • Posts

    12,731
  • Joined

  • Last visited

  • Days Won

    13

Ryan Ashbrook last won the day on August 16 2023

Ryan Ashbrook had the most liked content!

About Ryan Ashbrook

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    Cincinnati, Ohio
  • Interests
    Forums and Music. That's basically it.

Recent Profile Visitors

67,806 profile views

Ryan Ashbrook's Achievements

  1. 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.
  2. This should be fixed now.
  3. It was definitely a while ago, because mine is long again lol
  4. Sorry about that! This has been fixed.
  5. Computer, mobile phone, etc. Whatever the user is using to browse the site.
  6. 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.
  7. This should be fixed for you now.
  8. Yes, but this only controls cookies IPS4 itself sets (so anything prefixed with ips4_, or your prefix if you've changed it previously). Cookies from external sources will follow their own rules. If you do this, make sure you use two dots as that's what allows the cookies to be read by subdomains: define( 'COOKIE_DOMAIN', '.brfcs.com' );
  9. Are you using OAuth Tokens or just a REST API key? If you are using OAuth, then yes you still need to submit HTML with the request, however it will be parsed and sanitized according to the users permissions to remove anything malicious (excluding those with HTML posting permission - which should be no one other than groups like Administrators). This is ideal for applications that end users submit to directly, like a Desktop app in your case. OAuth also limits requests based on a users permission, so even if they can submit files to the API, they can still only submit to categories they have permission to post to. If you're just using a REST API key, then it's assumed that the request is coming from a trusted source. This is for things only an administrator has complete control over (typically automated tasks).
×
×
  • Create New...