Jump to content

Dll

Clients
  • Joined

  1.    Dll reacted to a post in a topic: Invision Community 5.0.5 Releases
  2.    Jim M reacted to a post in a topic: Invision Community 5.0.5 Releases
  3.    Ody Mandrell reacted to a post in a topic: Invision Community 5.0.5 Releases
  4.    Matt reacted to a post in a topic: Invision Community 5.0.5 Releases
  5.    PanSevence reacted to a post in a topic: Invision Community 5.0.5 Releases
  6. I'm not sure whether to laugh or cry, but for now I'll settle for this.
  7.    My Sharona reacted to a post in a topic: Topic Summaries issue
  8. Dll posted a post in a topic in Technical Problems
    The summaries are an invision cloud only feature....
  9.    Dll reacted to a post in a topic: Staging server pricing feedback
  10.    BankFodder reacted to a post in a topic: Staging server pricing feedback
  11. Dll posted a post in a topic in Feedback
    Just wanted to feedback on the pricing we were quoted yesterday for a staging server on the cloud platform - $249 per month. That's more expensive than the 2nd most expensive non-enterprise hosting package for a (virtually) zero-traffic staging server. I've seen some strange pricing of things in my time, but I don't think I've seen anything so obviously priced in the 'we don't want you to buy this' bracket as that. Obviously, the price is the price and Invision can set it where they like, but just wanted to put it out there that we're a paying customer (already on the business package for what it's worth) who wanted to spend more money with you, but definitely won't be at that price!
  12.    Dll reacted to a post in a topic: Broken images on invision website
  13. Surprised no-one at Invision has picked up on this, but there are broken images across a lot of the pages on the website currently.
  14. This option isn't available on Gmail any more: https://support.google.com/accounts/answer/6010255?hl=en
  15. I'd not worry about those - they're just a cloudflare thing, not related to your community itself.
  16. @David N. In webmaster tools, if you go to settings and then crawl stats, there's a crawl error report in there. You should be able to get some error reasons and URLs from that.
  17. Dll posted a post in a topic in Feedback
    Are there any plans to make the trending topics available through the API in the near future?
  18. Dll posted a post in a topic in Feedback
    Can I suggest you look into ses in the meantime, as it's cheaper and just as simple to use.
  19.    Dll reacted to a post in a topic: Ignore topics and forums
  20. Dll posted a post in a topic in Feedback
    Put some extra information in the failed login messaging perhaps? Or just on the login page. Make your contact options very visible and so on. If someone has been a member of a community a long time and come back after a while, you can assume they'll be fairly motivated to get logged in, so I don't suppose an extra step of sending an email will put too many off? Alternatively, (as we've found at times on our community), people will start a fresh account if they can't login and will probably then use that to ask about their old one. The change really isn't the end of the world, although we did spend 12 months notifying people in varying ways before making the change.
  21. Dll posted a post in a topic in Feedback
    I think with the amount of time you've wasted on this community over the last couple of years moaning about the change of login, you could have probably written a hand written letter to every one of your members advising them of the change.
  22.    Dll reacted to a post in a topic: Please stop removing features
  23.    Dll reacted to a post in a topic: Custom PHP block support in V5
  24. Does this means that using pages for things like ads.txt no longer works?
  25. Dll posted a post in a topic in General Questions
    They maybe need to look again then, as it looks a bit ridiculous at monitor widths above 1800px (which isn’t that wide).
  26. @Adlago, you appear to be misunderstanding how the caching works. It's not a local cache on a users machine, it's caching the html for the block server side, so the backend isn't generating it each visit. If you cache it for 1 hour, it'll retrieve the html from that cache for 1 hour, and then check again for an update the first load after that. Once it's done that, it'll cache it again for an hour. So, setting it for one hour will make it faster across the hour than setting it for 5 minutes.
  27. Nice to see Invision finally get over their apparent pathological dislike of all things cloudflare and embrace its obvious advantages