Jump to content

Alex

Clients
  • Posts

    9,357
  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Alex

  1. And Matt has also been keeping people up to date on his Twitter about Beta 2 :)
  2. We are pleased to announce that the first stable release of IP.Tracker 1.3, the compatibility release of IP.Board 3.0.0, is now available from IPS Resources. About IP.Tracker IP.Tracker is a bug/issue tracking system, it allows members and staff to track certain issues, for examples, bugs within a project you are working on, or even building a house! IP.Tracker supports statuses, severities, and much much more to bring you an extensible Tracker to use however you wish to. IP.Tracker is provided free of charge to current IPS customers with an active support service. As an IP.Board module, it is offered under the IP.Board License agreement and by downloading this file you acknowledge and agree to this clause. Please note that this free module is not included in your IPS support, is only provided as an extra convenience service, and is not guaranteed in any way. Expanding upon what was already there When we originally started 1.3.0, we specifically said that there would not new features, and it was simply a compatibility release to work with IP.Board 3. However, there are several new features which you will find in 1.3.0, some of which are outlined below. Several areas have been changed to fit in with the look and feel of IP.Board 3.0. IP.Tracker now supports the option to return to the issue listing the issue was originally in when replying to an issue. Each status can now have a 'canned message'. If you update a report to a status with a canned message, but do not provide a reply yourself, IP.Tracker will automatically insert this canned message for you. Statuses can now be marked as 'fixed statuses'. If you change the status of a report to a 'fixed status' but forget to fill in the Fixed In version, IP.Tracker will automatically scan the versions for that particular project and mark the fixed in version as the latest version available Each issue now contains its own timeline view. As the name suggests, this view will provide a brief history of the issue. It will outline important changes in the issues history such as status, severity, and version changes. We implemented a change in IP.Tracker 1.2 in preparation of this new view, so that the timeline view has a lot of data to already work from! We spent an extra few weeks testing and fixing bugs found in IP.Tracker to make sure that the end product is as stable as it can possibly be at this stage, we thank you for your support during the beta process. Moving on from 1.3.0 As said above, this is the first stable release, and as such there are bound to be bugs. When software leaves testing phases, more people are prepared to use it. The more people that use it in different situations, the more chance bugs will surface. As such, we are aiming to get 1.3.1 out within a few weeks of 1.3.0. 1.3.1 should sort the majority of the issues reported. From here, IP.Tracker is splitting into two development paths, of which we will post more about nearer the time. It is our intention that later this year, we will expect to release IP.Tracker 1.4.0. There are a few areas in 1.3 which are not integrated fully with IP.Board 3.0.0, for example Tracker still has its own search engine, and still has a few legacy functions coded in. 1.4.0 will be all about removing these particular areas, and utilizing what IP.Board 3 has to offer. Half of the IP.Tracker team will be developing 1.4. Also starting development at the same time, the other half of the team will start IP.Tracker 2.0, 2.0 promises to be an extremely powerful system and highly configurable. We are hoping to branch out into more of a project management system, providing you with everything you need to completely manage your projects: timelines, discussions, tickets, file management etc. More information will come later this year, and a release is expected next year. We hope you enjoy the 1.3 series, and of our plans for the future. To read a more detailed change log for IP.Tracker 1.3.0 from RC 2, please read this topic, or to visit the download please click here.
  3. It's this topic, if you look at the URL there is some unicode after the word issued to display that symbol, thats probably what is causing it.
  4. I too would eventually like to see the white skin released, its very nice :)
  5. Alex

    New IPS Web Site

    The forums are under the Support tab :)
  6. Alex

    New IPS Web Site

    It is the same website just completely redone :) The content and layout has changed to give it a fresh look with the launch of IP.Board 3. The current site is very outdated :)
  7. I don't know about hosting particularly, but I know there are staff that sometimes work over the weekend to sort out emergency issues.
  8. Security patches generally have a manual difference report posted, so you can apply the changes yourself.
  9. I spoke to Brandon about it when I made that hook, hooks should support adding CSS files in a future version (3.x) for example. It's just one of those annoyances that'll you'll have to upload it to every CSS folder on your site.
  10. Thanks for the kind comments :) From my personal experience I have to say that whereas hooks might be easier for the end-user (no file edits and all that), it does take some getting used to. I can create the hooks fine but it takes a lot of brainstorming on how to overcome certain issues :P For example the reputation hooks I released yesterday, I needed access to the post data ID without having to perform the same query every time (would make 2x as many queries per page load). Had to experiment and come up with some nice javascript to get around that :P I think the reason more and more mods are coming out every day is the actual IP.Board3 code being so easy to follow, not just the hooks system ;)
  11. It *appears* to have more bugs because of how the RC is reaching a wider audience. Those bugs have probably been in there since beta, but because not everyone is comfortable with beta releases, not everyone finds and tests them. A hell of a lot more people will use the RC over the Betas, so more bugs are found as more users use it :)
  12. Alex

    RC1 Release

    It is very much worth the wait though ;) You better all be thanking IPS :P
  13. I would say its a bug actually. We noticed it in Shoutbox when developing a while back, the editor javascript automatically focuses on the editor, which can be a pain in the arse :P
  14. That would be a dream come true for me if they decide to do it.
  15. Most likely yes, it's a good selling point for IP.Board, so yes.
  16. The encoding is not an issue as we use unencoded builds of IPB anyway (thats how Shoutbox and Tracker are being ported). I know its a big feature, but I am kind of glad we do not have it as a community project yet, we have enough on our plates :P
  17. Alex

    Group Search-ability

    http://forums.invisionpower.com/index.php?app=members&section=view&module=list I can search groups via that, unless I am missing something here? (If this is IP.Board 2, they won't be releasing bug fixes for that unless it is a security issue, which in this case is not)
  18. IP.Converge is designed to be an open platform allowing any application to share a common authentication method. This allows sites on different servers, and using different products, to let users access it with a 'global' login. Unfortunately due to limitations within IP.Converge, only a handful of IPS applications utilised it. However, with the recent introduction of IP.Converge 1.1, functionality has been added to allow 3rd-party applications which use a different password hashing system, to integrate with Converge itself. Being able to integrate popular products seamlessly was an opportunity we simply could not miss! We have noticed that modifications integrating products such as Joomla and Wordpress with IP.Board were so commonly requested, that we had to do something about it. Introducing IP.Converge Modules As many of you will be aware of, we have a team of Community Developers who actively develop and maintain our community-projects; IP.Tracker and IP.Shoutbox. We now have a new project that has been in development for some time, IP.Converge Modules. We are starting off with modules for integrating Joomla, WordPress and WordPress MU with IP.Converge and further modules will follow in the near future. You may have read our community developers talking about the development of these on the forums already. This new range of community projects should prove a popular addition. Available for beta testing, we currently have IPC.Joomla and IPC.WordPress, a separate module is available for WordPress MU users (IPC.WordPress MU). These Converge-ready applications will integrate your existing Converge applications with these popular products. If you wanted to, you could link up multiple Joomla/WordPress installations with your IP.Board, as Converge supports this very well. For the first release, the modules will offer simple integration compatible with IP.Converge, however in the near future more extension sets will be available for download. These extension sets will each offer a different level of integration for the products, but for now we are simply focusing on integrating these popular products. To avoid confusion surrounding the products named 'JIB' and 'WIB' developed by Brandon D, IPC.Joomla, IPC.WordPress and IPC.WordPress MU are in fact the new 'JIB' and 'WIB'. Brandon D has been leading this new community project, and therefore work on his two old projects has been carried over to this community project. You can download the beta releases of these Converge modules here, and the new forums have now been revealed, please feel free to ask any questions there! The Resource site's community project page has also been updated to reflect this new addition! Finally, a new bug tracker project has been set up to allow you to report bugs in these modules. These converge modules require the PHP version that the product requires, for example to install IPC.Joomla, you will need a PHP version which is compatible with Joomla itself. IP.Converge 1.1.0 RC 2 To go alongside this release, the second release-candidate of IP.Converge is now available for download for those with an active IP.Board license. Please continue to report any bugs you find in the IP.Converge bug tracker. In order to install the Converge modules, you must be using at least IP.Converge 1.1 RC 2. We hope that these new two projects will go a long way and prove to be a very popular addition.
  19. You might want to submit it to the resource website, it would be a great addition :) Very impressive work
  20. Seems I was wrong :P There was talk back in July last year about this, but to my knowledge I thought it was all happening on the resources website, not the main one itself :)
  21. It won't happen on invisionpower.com, thats the whole point of resources.invisionpower.com :)
  22. I doubt this will be in IP.Board3 unless its already in it now, as it is feature-locked. Might need to be a suggestion for 3.1
  23. According to Matts blog entry about IP.Board not trying to be a social-networking script, but a forum means I don't think this is in IP.Board 3
×
×
  • Create New...