Some future events are not showing up in Timeline when there are a lot of events

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add about 545 events to Simile-Timeline
2.
3.

What is the expected output? All events that fit the timeline query showing in 
the swimlanes.

What do you see instead? Only events two weeks out from the current date and 
within previous year.

What version of the product are you using? How do I find out?

On what browser and what operating system? IE9, Windows 7 Enterprise


Please provide any additional information below.
If I remove some events it shows more events in the future, so a workaround 
would be to remove older events so events more than two weeks out can be shown, 
but we want all events shown that should be shown. 
Every day I see one or more new events two weeks out and the ones older than a 
year drop off. It looks like SPServices in only putting ~545 events in 
json.events. 

Original issue reported on code.google.com by [email protected] on 25 Mar 2014 at 2:29

[ckoeppel1]

I working in Simile Timeline 2.3.1 and future events are not showing up only on Chrome. I read that adding the paramenter CAMLRowLimit with a high value will show all future events, but what is the code for this and where do I put on the HTML page?

[karger]

When posting a problem to the list, please post a link to the example
exhibiting the problem. It makes it much easier to assess!

On 7/11/2016 5:36 PM, ckoeppel1 wrote:

I working in Simile Timeline 2.3.1 and future events are not showing
up only on Chrome. I read that adding the paramenter CAMLRowLimit with
a high value will show all future events, but what is the code for
this and where do I put on the HTML page?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#505 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABFpXpdZ_CpR5CTnShQSj27ekVOk3qrzks5qUrdpgaJpZM4JJzps.

[ckoeppel1]

I discovered that it is a Chrome glitch with clearing the cache. It is an annoying glitch that you need to take care of manually, but they are working on it.

Thank you for responding.

Cindy