Jump to content



Invision Community Team
  • Content Count

  • Joined

  • Days Won


 Content Type 



IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog



Everything posted by Rikki

  1. It's a legend lost to time. We just keep them in case removing them releases a terrible curse.
  2. Unless I'm misunderstanding your report, the email address you see is that of the user that is checking out - i.e., their own email address.
  3. While TestFlight (and Android) allow you to submit feedback, honestly the best way is to submit a ticket in the usual way. Thank you!
  4. CSS is flexible enough to allow you to do that without needing unique classnames. For example: .ipsType_richText a { color: red; }
  5. It's under Customization -> Appearance -> Icons & Logos. As for push notifications, I'm not sure what our plans are on that.
  6. We already have PWA support, though that doesn't include push notifications yet.
  7. We are a way off of offering a white label service still - we plan to get the main app stable and add more functionality first. We'll post an announcement when we're ready to accept some interested sites 🙂
  8. Thanks for the feedback; it sounds like a couple of the issues you noted are bugs, so we'll be able to address those as such. We've been upfront that firstly the app is in its early stages but also that it won't necessarily be ideal for every community. If you have a lot of customization (be it plugins or lots of custom pages) it's probably not going to be the best solution for you. We may devise a solution to that in future but right now it'll be focused on core 'out of the box' functionality. I'll lock this since you have struck out your first post, but I just wanted to address you
  9. In 4.5 we've tried to keep headers consistent, so that buttons are where you expect them to be, there's space for additional buttons as each page/app might require, and so that each page/app can extend the data shown in the header without the whole thing breaking down. In 4.4, this was a problem - sure, on perfect example pages, the follow button worked well in the top right. But using a different app where more buttons need to be shown, or even just having a long topic title, suddenly it wasn't so pretty and usable. The new header is designed to be flexible and extensible according to require
  10. We don't load (many) polyfills ourselves - they are included with libraries that we use. Those libraries will only execute them when needed, but the code is still sent to the browser since we bundle and minify javascript.
  11. None of our own CSS selectors use the .sp prefix - that comes from a third-party library we use. But frankly, the possible overheard for the browser is so negligible that it isn't even worth worrying about,
  12. Apologies again! Update your app to get the latest build and things should be good now. At the time of this post, the app was approved in the Play Store but still pending review in the iOS App Store, but should be available soon. Note that in both stores it's still in the beta process (Beta in the Play Store, TestFlight in the iOS App Store) so you won't see it unless you specifically opt in to the beta.
  13. We have no problem with choices - that's why we have thousands of choices in the AdminCP. But every choice, no matter how small it may seem, has a cost in terms of development time, future maintenance, documentation, UI complexity and so on. And that's not even counting the problems with the feature that we've already outlined, specifically that they aren't the same for all users and therefore cannot be relied upon in the way you want them to be.
  14. The date in every post provides a direct permalink to the post. Incorrect post numbers based on a user's individual permissions would certainly present more of a usability issue for both disabled and able-bodied users. It's absolutely fine that some people would like to have post numbers back - we understand people don't always like change - but please let's not try and justify it as being a legal requirement.
  15. Those files aren't obsolete - they are the foundation of our framework. What your tool is finding is polyfills for old browsers that libraries we use (such as jQuery) include.
  16. Just to note, we did list this change in the deprecation section for 4.5. We always recommend reviewing the release notes, especially for major releases.
  17. Even Microsoft will not support IE11 (or legacy Edge) in any way from next year, including in its own products like Teams. Other major sites like Twitter are starting to drop any support too. It won't be long until you'll struggle to use the web on IE11. Technically we have not supported it for a long time, but because we held back on modern CSS features, it still mostly worked. For 4.5, we decided now was the time to press ahead with improvements and drop support ourselves. By dropping support, we've been able to use newer CSS features that benefit designers (and therefore site owners),
  18. Apologies for the problems. I was finally able to diagnose the cause of the login issues, but unfortunately they cannot be fixed until 4.5.2 (and new app builds). That should be available in the next few days. That will solve both the failed logins and the 'invalid redirection uri' error.
  19. The default font changed in 4.5, so that may explain that difference. It was Roboto in 4.4, but 4.5 just uses the system default (Segoe on Windows, SF on Mac, etc.). You can edit your theme settings and switch back to Roboto if you prefer the previous style.
  20. Are you seeing errors in any modern browser? The variables it is flagging up are valid CSS and don't affect performance.
  21. Thanks for the feedback - it's definitely early stages. We'll be looking to improve performance as time goes on, as well as add functionality. There's only one codebase for both iOS/Android, but that is indeed (currently) separate from the main product. It's very much 'work in progress' right now 🙂
  22. That's the pagination bar - though on the first page pagination doesn't show.
  23. If you're working in templates there's also a {truncate} plugin that'll do it for you. Just do {truncate="$content" length="200"}.
  24. I don't think that'd be feasible because the app stores aren't going to pass on referrer info to the app to know which community you tapped from. Maybe some way of quickly adding a community would be a compromise? A 4 digit code or a QR code maybe?
  • Create New...

Important Information

We use technologies, such as cookies, to customise content and advertising, to provide social media features and to analyse traffic to the site. We also share information about your use of our site with our trusted social media, advertising and analytics partners. See more about cookies and our Privacy Policy