“week.three” should be named “Three Weeks” sounds like the default spark_i18n.propies is missing the keys.
Maybe i should put an info box to the elements to explain their function.
It should list the messages, grouped in a time period of three weeks per page, for example “Week 1 to 3 of 2011 on one page, week 4 to 6 of 2011 on the next” and so on. Works fine with my transcript.
The “month.one” option will group all messages that where send at the same month and the “week.one” all that where send at the same week.
Strange that your messages are shown one per page… do you use test data or a real transcript?
I use real transcript with 4 years history. One week looksok. Three weeks as i said separates every message on a different page. One month setting has only 4 pages… Well probably i have talked with that contact only once per year But one of that 4 pages shows more months.
Tim, Walter, any update on this patch? Maybe we can have a simple patch reversing the 5000 messages limit to show latest messages, not the first ones, until the whole patch is complete? We are going to test a few clients to replace our old client. The main complaint about the old client was about not saving the history, so with current bug it would be hard to sell Spark to my bosses
Hate to whine, but i suppose i won’t be able to get updated build for tomorrow pilot project start? Any new when can i have my hands on the updated build in Bamboo?
Once again bumping this We are deploying Spark company wide this and next week. We probably won’t hist the 5000 messages limit anytime soon, but would want to have new history gui soon, so users won;t have to re-learn using it. Btw, check the comment on history orientation on the ticket. It is opposite to the way history is displaying in the chat window itself (and from the old behavior). Would be more logical to have old messages on top, or at least to have a sorting switch.
Thanks Wr00t, got it installed to test out before deployment.
I thought this was coming out with 2.7.0 like it’s stated in the ticket (SPARK-1407) not implemented in the current version. Not that I’m complaining, this is much better.
Well, this is coming for 2.7.0. You see 2.6.3 here, because version number is still not changed in the source code, but it will be before the official release. So you are using 2.7.0 actually. The current version of 2.7.0, which can still change a few times. Not sure when the release be. I stopped caring about this and just use those nightly builds if i need some new featture or fix and name them as 2.6.3.598 (598 build) and deploy them for my users. E.g. now all my users are on 2.6.3.596 and today i start deploying 598 No point waiting for 2.7.0.