{"issue":{"created_at":"2011-12-08T23:55:36Z","state":"closed","updated_at":"2011-12-08T23:55:41Z","comments":0,"user":{"gravatar_id":"5ba9f77b20f8ee7f7bab04ca792a5ea7","id":306256,"url":"https://api.github.com/users/passbe","avatar_url":"https://secure.gravatar.com/avatar/5ba9f77b20f8ee7f7bab04ca792a5ea7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"passbe"},"body":"Back in September when a number of the &quot;eval&quot; calls were removed, and\nsubsequent changes to reduce the number of HTTP requests made from the\nadmin UI to the framework the logging tabs (both the default and\nzombie logs) were broken. Currently those log panels will only pull\ndown 25 entries, the pagination doesn't work and the sorting doesn't\nwork.\n\nOne of the primary issues is that the Ext.PagingToolbar(used for\npagination) component relies on sorting and pagination (limitation of\nrecords) occurring on the server side. This meant that the logging\ntabs did send a number of requests when you changed sorting options or\npaging through entries.\n\nThere is a UX component that can be used called\nExt.ux.data.PagingStore which provides local paging within JS, but it\nmeans using another ExtJS ux class. I'm going to try and spend a bit\nof time seeing if that works, and if there is any negative impact.<br><br><em>Google Code Issue: http://code.google.com/p/beef/issues/detail?id=216</em>","assignee":null,"id":2496455,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[{"name":"GC Imported Issue","color":"ededed","url":"https://api.github.com/repos/passbe/beef-migration-test-3/labels/GC+Imported+Issue"}],"number":242,"title":"Logging defect","html_url":"https://github.com/passbe/beef-migration-test-3/issues/242","closed_at":"2011-12-08T23:55:41Z","url":"https://api.github.com/repos/passbe/beef-migration-test-3/issues/242","milestone":null},"action":"closed"}