I was using digrotate 3.2.0 on one site when I noticed that under some circumstances two cookie with names LastRotateXXX are created and sent to server, resulting in server to use the second as currentpage and rotate script to crash.

I have concluded that digrotate3 is not URLFriendly . so it will generate a cookie for xxx.com and a cookie for xxx.com/tabid/yyy/default.aspx, although both are the same.

So i changed digrotate3.js rotate function just to tell if it the required page can not be found, fall back to page 0;

I hope this has been fixed in rotate4.