Hi Christian, Thanks a lot for the nice screencast - I have disabled cache for my Chrome.
Harry On Tue, Jun 12, 2012 at 2:01 PM, Christian Vuerings < [email protected]> wrote: > Hey Harry, > > Great to hear that. > > When you're developing with Chrome, the JavaScript will be heavily cached. > This is actually a good thing in production & we don't have issues there > since we're hashing the URLs. > > For development this can be a pain though. > The way I currently fix this is by disabling caching in the developer > tools [1]. > We have to keep in mind though to keep those the developer tools open, > otherwise it won't be enforced. > > Christian > > [1] Screencast: http://screencast.com/t/GY9ArkRzkpP > > On Jun 12, 2012, at 1:34 PM, Harry Wang wrote: > > Hi Christian, > > I just tried using Firefox and it worked without changing anything - I got > that error when using Chrome. I then cleared all history data including > cache in Chrome and it worked after that. > > Thanks for your help. > > Harry > > > > On Tue, Jun 12, 2012 at 1:25 PM, Christian Vuerings < > [email protected]> wrote: > >> Hey Harry, >> >> Would it be possible to look at the console/network tab in Firebug and >> look for any 404/500 responses? >> Another thing that would be good to look at is the sling log. >> >> Regards, >> Christian >> >> On Jun 12, 2012, at 1:13 PM, Harry Wang wrote: >> >> > Hi, >> > >> > I use OAE-builder to run OAE at localhost:8080 and am able to register >> new users. However, when I try to access dashboard I get an empty page as >> shown in the attached screenshot. Any help please? >> > >> > Thanks, >> > >> > Harry >> > <Screen Shot 2012-06-12 at 1.11.13 >> PM.png>_______________________________________________ >> > oae-dev mailing list >> > [email protected] >> > http://collab.sakaiproject.org/mailman/listinfo/oae-dev >> >> > >
_______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
