Changes between Version 15 and Version 18 of Ticket #590
- Timestamp:
- 09/07/13 15:19:12 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #590
- Property Add Hours to Ticket changed from 0.75 to 0.35
- Property Total Hours changed from 5.45 to 6.4
-
Ticket #590 – Description
v15 v18 7 7 = Proposed fixes = 8 8 9 === Agreed to do by Ed === 10 '''B) Try a Taxonomy Cleanup''': 3 hours, Medium risk, medium reward -- style module to try to merge terms with the same names and clean up the link tables back to nodes. Further, we can remove any taxonomies or relations to certain CTs that don't really add value. 11 9 === To Do: Agreed by Ed === 12 10 '''D) Review Views caching''' 1-2 hours, low risk, high reward -- this was done a while back but I think 13 11 … … 15 13 16 14 17 === To do once above done ifspare time (JK to monitor, EM to confirm) ===15 === To do: depeding on spare time (JK to monitor, EM to confirm) === 18 16 '''C) Find Variable table writes and kill them''' -- 3-8 hours, medium reward, low risk -- Per item 9 below, I see plenty of SELECT * FROM variable calls, which imply a cache clear due to a variable being set. In normal use variables shouldn't be set (admin screens tend to do this), so I'd like to try to see what module it causing this and patch/remove it. 19 17 … … 24 22 '''A) Remove spam taxonomy entries''' 1/2 hour, Low risk, low reward -- See item 8 below. A simple delete from taxo term table where length > 50 is worth doing IMHO, and nothing I saw that would be clobbered is not spam. 25 23 24 '''B) Try a Taxonomy Cleanup''': 3 hours, Medium risk, medium reward -- style module to try to merge terms with the same names and clean up the link tables back to nodes. Further, we can remove any taxonomies or relations to certain CTs that don't really add value. 25 26 26 '''H) Remove CustomError module all together''' ~~1/2 hour, low risk, low reward -- We should take out the PHP code from the 403 section of CustomError and put it into a simple page entry. See comment 6 below as this has happened for 404s (which need no PHP). We can then remove the CustomError module all together, saving lots of sessions. I would go ahead and do this but since the 403 page has various displays depending on user type, I wanted to raise it here as it *may* have side effects. Or not...~~ 27 27 28 28 29 29 === On hold for now === 30 '''B.2) More Taxonomy cleanup''': 2 hours, Low risk, low reward -- try to merge terms with the same names. 31 30 32 '''E) Review site features, kill what we don't really need''' Low risk, '''game changer''', care needed, medium reward -- Let's start reviewing the site and make a short-list of things that have had their day. Ed, do you want to drive this on your return. 31 33 * '''E.1) Remove 'Geographic region' and related taxonomy and Hierarchical Select modules''' 1 hour, low reward, low risk -- never really been used and is effectively a duplicate of the location field. let's kill it!