Changes between Version 27 and Version 30 of Ticket #590


Ignore:
Timestamp:
09/08/13 18:11:10 (3 years ago)
Author:
jim
Comment:

I've now gone through and set block caching and timeouts where appropriate on all blocks (just did ones assigned normally before, now covers ones from Context too).

Also added Views Lite Pager (Proposal K), which should on a big site like ours saves a heavy node count just to work out what pager numbers to display. Instead of the normal next, prev, last, first, 1-9 options, it now just has 'next' and 'previous'.

Am now working though major views and adding the new litepager at the sme time I check/tweak the caching.

Added to our makefile recipe. Updated summary.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #590

    • Property Add Hours to Ticket changed from 1.75 to 0.75
    • Property Total Hours changed from 10.7 to 11.7

  • Ticket #590 – Description

    v27 v30  
    3030'''I) Re-enable block caching.''' ~~2-6 hours, high risk, high reward -- Per comment 24, a module (probably Content Access) is stopping Drupal caching blocks, which for some of them means a fair amount of pointless overhead. We need to somehow get around this and get blocks cached if possible. R&D mainly, perhaps with some hacking/patching - but I'd stop short of doing this if so.~~ 
    3131 
     32'''K) Add & enable Views Lite Pager on big views.''' ~~1 hour, low risk, low reward -- Using this module stops a heavy count query on views with pagers -- recommended for large sites.~~ 
     33 
    3234=== On hold for now === 
    3335'''B.2) More Taxonomy cleanup''':  2 hours, Low risk, low reward -- try to merge terms with the same names.