Jump to content

Charles

Management
  • Posts

    20,490
  • Joined

  • Last visited

  • Days Won

    436

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by Charles

  1. Note that this feature was added in 4.6.0 - we just enabled it here.
  2. I believe everything should be back to stable now. We found a bug in AWS Aurora that ended up requiring engineers to hot-patch our clusters.
  3. There is no hard limit on this but it can start to get difficult from a UI perspective. That is true both from you managing all those forums/clubs and for your users trying to navigate it.
  4. He literally gives every single hump day topic a different title 🙂
  5. Sorry - that was my fault. I was doing backend server upgrades that host this site and our various backend functions like building zips for download. But things should be faster and more secure now so there's that!
  6. We released a patch to resolve the theme upgrade warnings. There really were not tons of theme changes but our release build routine had issues and incorrectly flagged the changes.
  7. I am curious why you would be concerned about someone who is not logged in viewing your site. At that point it is publicly viewable and everyone and everything (like search bots) can see it by design.
  8. We actually do it on-login for the users by design as a cron would create unnecessary overhead since it has to scan users who are not active. Is the user in the wrong group causing problems? Of course the system corrects itself the next time the user visits so they would not be able to do anything.
  9. We plan to add this feature but wanted to implement base Achievements first to see how people used them. But it will for sure be coming 🙂
  10. We have not added such a feature because it does not really come up as a common problem. I would say this is a moderation task more than a software issue to solve.
  11. Only if you have betas enabled. Check your constants.php file for use dev builds constant.
  12. That is a cache bust key unique to you. Normal browsing would not see that but since you are doing something "odd" it is putting that in to ensure you are not seeing a cached page.
  13. That's a genius approach. When your spouse is good you can be like "I recognize your achievement." I'm sure that will go over well for all!
  14. All depends on feedback from beta testers.
  15. Apparently photos add congeniality to me.
  16. He had an actual Polaroid camera for reasons I still do not understand.
  17. The old ranks and such were merged into the new Reputation system. If you want to maintain the ability for people to put some text below their name on the post bit, you can use custom profile fields to do the same thing.
  18. You are responding to a 2+ year old topic 🙂 We have had auto-save in the editor for a long time now. If I type this and accidentally hit back on browser, when I return to the editor it will have kept my content and shown me a message telling me.
  19. I'm not sure what you mean about mobile viewing. Achievements should also show on mobile. Are you not seeing things?
  20. We always have a long internal list. Right now we want to review our new cache rules. They will greatly improve performance but, if not done right, could cause lots of odd behaviors. There is also going to be a bulletin going out to all AdminCPs soon to remind people about features deprecated in 4.5 that will actually be removed in 4.6. We announced those over a year ago but just need to remind people. But right now the big thing is refining Achievements. Since this is only the second site that has any real content using it, we are working on both bug fixes and general improvements. That is coming together nicely now.
  21. Thanks... we support our beta releases so please do use them as you can submit support requests with issues. Just be sure to have backups and a willingness to work around issues as they are still betas!
  22. The process will be the same this time other than we did not do an alpha site and instead are doing the alpha on this site. We release several betas until we are no longer receiving any bug reports then do the full release. It is perfectly normal that the full release is quickly followed by maintenance updates. I cannot think of a single bit of software I use that is not followed by maintenance releases soon after the full release. I encourage you to participate in the beta releases.
  23. We always release betas for big releases. Have been doing so for years 🙂
×
×
  • Create New...