Transition Technology: Ticket #251: Changes to Project profile

priority, summary changed

ed — Fri, 17 Jun 2011 10:50:34 GMT

priority changed from major to critical
summary changed from Remove some fields from Project profile to Changes to Project profile

include a field enabling users to add a link to a youtube/vimeo video which is then embedded (see https://tech.transitionnetwork.org/trac/ticket/259)
'concertina' the lower sections: Resources, People,
Make massive big arrows or something like that indicate the 'concertina-ed' sections with some text saying: "To add information about [section name], click this arrow" (or whatever the thing is)
Remove the 'explano-blurb' under every editor saying what they can and can't enter
halve the length of the editors
Bundle 'inspiration', 'outcomes so far', unexpected outcomes, obstacles, lessons learned into one concertina-ed section called "Outcomes and Lessons learned" and handle as per 6 above.
apart from the 'project aim' and 'project description' either make all the editors proper WYSIWYG editors or all the editors simple text entry - what's best?
Remove 'revision information' for normal users
Add "Transition stage" with multi-choice options which relate to the stages in the ingredients (as per the resources) just below the project description
normal users can't see the themes (!) re-add them in a grid style below 'Transition stage' (and the last thing before the concertina-ed section)

description changed; cc set

ed — Fri, 17 Jun 2011 18:27:47 GMT

cc laura added
description modified (diff)

status changed

jim — Fri, 17 Jun 2011 18:35:52 GMT

status changed from new to accepted

1, 2 and 3 (multiple entries) this is Drupal's behaviour and needs hacks to CCK to override: see http://drupal.org/node/320313 and http://drupal.org/node/196421... We should come back to these at the end.

4: See #259

jim — Fri, 17 Jun 2011 18:42:21 GMT

5 - Collapsed by default now.

6 - This needs a little thought... Could move the whole form into a panel or we could override this at theme level - or just with CSS.

7 - explano-blurb removed BUT THIS IS SITE WIDE for ALL rich text boxes... OK?

ed — Fri, 17 Jun 2011 19:03:37 GMT

good
discuss with laura?
confirmed - remove from all rich text boxes

ed — Fri, 17 Jun 2011 19:05:58 GMT

can you add some blurb above the concertina-ed bits for now saying 'click on the titles below to add more detail'?

jim — Fri, 17 Jun 2011 19:15:42 GMT

8 - another site-wide WYSIWYG issue...... Will need its own research.

9 - Done with caveats from 6: Panels & CSS needed. Chat with L in the pipeline...

10 - I reckon simple text (non wysi) is best for everything except those two fields. No point guilding the lilly (!)

jim — Fri, 17 Jun 2011 19:31:06 GMT

Re 6: Not without moving to a panel or editing the theme...

11 - will need to add this to the module - code here: http://drupal.org/node/117148#comment-4525608

12 - need to do other pattern/tool/ingredient stuff first really.

13 - Done.

ed — Fri, 17 Jun 2011 19:38:40 GMT

re: 6: OK re: 8: worth it though - they're massive 10: agreed 12: yes 13: groovy, baby

jim — Sat, 18 Jun 2011 18:15:51 GMT

Recapping so far:

Todo:

1, 2 and 3: (remove second field from varions mulit input fields) is a CCK core hack and not recommended... Back burner for now. 4: needs module update #263 6 & 9: Need a chat with Laura, and probably the node edit form -> panels 8: will be site-wide shrinkage of WYSIWYG... They could be dropped from 400 to 300px everywhere? Ed? 10: remove rich-text from all these fields... 11: Add code http://drupal.org/node/117148#comment-4525608 to our module - site wide again but worth it since the revision system is fully automated on nodes that need it. Depends on #263 12: Transition stage depends on #246 and #265

So a couple of decisions, Ed, and I need a chat with Laura, but then this ticket ticks over until the blockers are done.

ed — Mon, 20 Jun 2011 10:12:10 GMT

1,2,3: OK - I note there's some ordering function on them now? 8: The WYSIWYG is good for news and events, but a PITA everywhere else, so shrink the WYSIWYG sitewide. Is it possible to *not* shrink it on news? 10: is that an instruction for me, or just a note to self?

jim — Mon, 20 Jun 2011 10:52:54 GMT

1,2,3: Have ordering because they're multiple entry fields... We could try making them singles but there would be a risk of losing data... But, since there are so few projects (for now) we could maybe bite this bullet? 8: AFAICT it'll be site-wide, nothing in the function that changes this has knowledge of the node type. 10: Note to self... BUT also a concern that we might need to strip HTML out of these fields manually. As first item, might be worth doing this cut/paste-athon now rather than later.

ed — Mon, 20 Jun 2011 11:27:47 GMT

1,2,3, I'd bite the bullet and risk removing the second ones; can handle the frontline support side of it

Hmm. Would make long article entry a PITA. Is there a dinky theme/style thing or editor that lets us re-size the WYSIWYG like Wordpress lets you?

Hmm. Can you do a report on those fields that have text in them? I can do cut and paste; you're too expensive...

owner, status changed

jim — Wed, 22 Jun 2011 14:54:27 GMT

owner changed from jim to ed
status changed from accepted to assigned

1, 2, 3 - Those fields are now single- rather than multi-entry... I've been through every project and manually combined these fields because every entry past the first would have been lost. Only about 1 in 10 were affected.

8 - WYSIWYG editor is now 320px high, down from 400px. This is in SVN and can be seen in DEV. Waiting on #263 still...

10 - Removing editor from fields... I reckon this is a bad idea having seen the project directory... Ed? My vote is to keep it, and indeed extend it to fields in 1,2,3 because multi entries in a single box need bullets or newlines that are stripped currently.

11 - Revision information: Have added that code to SVN and DEV so the revision section is now shown ONLY to those with 'Administer Nodes' permission (editors, admins)

Sooo....

Module & code updates/installs #263 for last bits
Plus a chat with Laura after the above hits.
Anything else?

Reassigning for answers..

owner changed

ed — Wed, 22 Jun 2011 18:30:33 GMT

owner changed from ed to jim

1,2,3: outstanding! 10: agreed. make 1,2,3 WYSIWYG 11: stunning

looking forward to hearing from Jim/laura chat

ed — Fri, 24 Jun 2011 10:28:37 GMT

possibility of CK editor in future (5?), stay with fck for now. jim looking into auto-length code bug.

jim — Mon, 27 Jun 2011 15:46:26 GMT

Video links now in place as per #259
& 6. Will now convert edit page to Panels, then that opens up space for notes and arrows above collapsed sections etc.
"Related Transition Stage" Stage reference added, added to panel...

Just panels stuff left, then send to Laura.

jim — Mon, 27 Jun 2011 15:49:42 GMT

that last "6" should have been "12".

owner changed

jim — Mon, 27 Jun 2011 16:30:31 GMT

owner changed from jim to laura

OK points 5 & 6 are hard because Panel's ability to override these forms sucks wang.

In other words, this is something Laura will have to do via CSS...

Handing it to the L!

ed — Tue, 28 Jun 2011 09:48:22 GMT

please add stages into chronologicalo order instead of alphabetical order: ie:

starting out deepening connecting building daring to dream

laura — Wed, 27 Jul 2011 09:52:27 GMT

= done

status changed; resolution set

ed — Thu, 11 Aug 2011 10:28:27 GMT

status changed from assigned to closed
resolution set to fixed

closing