Hi Ashley & Rob,
Thanks for the report, and the example
>> I no longer have the navigation buttons for that browse in version 7.13.
fixed.
>> This browse has a title that is not being displayed.
fixed.
>> Click on the "Closed Audit" button. You can see that the browse title does not change.
fixed.
>> Even though 7.13 fixed some bugs, new bugs have been introduced.
yes, although the scope of the bugs introduced is quite narrow, whereas the items being fixed through the 7.11 through 7.13 builds are much wider in scope - in order to do some things sometimes big changes are required. Alas sometimes the big changes can lead to some refinements being necessary.
>> We need a break. Can we get new releases that just fixes bugs and does not introduce any new refactoring for while?
depends on your definition of a "while", but yes I'm trying to keep the builds coming fast, and the fixes as low-impact as possible for this week. that said I've got an enormous amount of things to get done before Devcon, so there will likely be some "big" tweaks coming in the relatively new future.
I know it's painful, but the end result is worth it. There are two basic strategies though which I recommend; Either
a) try builds as quickly as possible after the release. It's a lot easier to make small tweaks and update a fresh build than it is to do a build at an arbitrary time.
Or
b) hold back and get a release say a week after it's up. That way you ship all the "obviously broken" stuff. That said, this approach can work less well if you have a lot of custom code - the more "custom" the app the more likely it's not in my testing patterns.
cheers
Bruce
Topic: Second Browse on a page does not show Nav Buttons in NT7.13 (Read 3692 times)