Closed (won't fix)
Project:
Composite Layout
Version:
6.x-1.0-beta7
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2009 at 14:39 UTC
Updated:
23 Apr 2011 at 04:27 UTC
Jump to comment: Most recent file
Comments
Comment #1
bengtan commentedIt's a decision made to keep the handling of Fields consistent with Blocks and Nodes. For example, automatically including all blocks on the Zones page probably isn't a good idea. Then, when I wrote the Fields functionality, I just kept with the same interface.
Your idea is interesting. At the moment, however, I'm not inclined to make such a change because I don't quite see it as that important.
Your opinion may vary, however, and feel free to persuade me otherwise if you wish.
Comment #2
jesss commentedThanks for listening. For me, this comes down to a usability issue.
It makes complete sense that you would want to limit which blocks appear on the Zones page. Few, if any, may be relevant to the display of any given node.
However, CCK fields explicitly belong to the node, and the bulk of the time should be displayed. In the current workflow the user is required to go through an additional step of checking numerous boxes to get the content that they just added to display. In practice, this is a cumbersome and time-consuming process.
I'm generally a fan of consistency, but not when it gets in the way of productivity and user experience.
Thoughts?
Comment #3
bengtan commentedYour idea has merit.
Unfortunately, I don't have the spare bandwidth to spend on this further right now.
If you have the resources to submit a patch, I'd certainly consider it. I don't suppose I can ask for the patch to include a configuration setting somewhere to toggle this behaviour?
Comment #4
tchopshop commentedYes, I was thinking this was a User Interface problem also-- my users don't know what a "field" is, typically -- so they don't understand why after adding content it doesn't show up on the zone page. I was thinking the Fields tab and the Edit tab should be merged so that each field gets a check box next to it if it will be included on the Zone page.
Just my 2 cents. I love this module. I just wish that I were a developer, so that I could create a patch, instead of merely requesting it respectfully...
thank you!
Comment #5
nmadden commentedI would also like this behaviour. As I understand it, if the type['local task'] flag is FALSE, then there is no way to select which elements of that type to display? If so, then it would make sense to just select all potentials of that type for display.
I attach a patch (against beta8 in my local svn repository) that implements this functionality. In composite_update() it adds references for each potential of types which have no local task (if they are not already present). Updating the fields type to then not include a local task solves the issue.
(Note: patch may need reformatting, my Netbeans is set up for a different coding standard).
Comment #6
tchopshop commentedI just tried this patch. It seems to get rid of all fields on the fields tab, but it doesn't add them to the Zone tab to place into regions. Not sure I'm understanding.
Comment #7
nmadden commentedtchopshop are you trying the patch on existing nodes or newly created ones? The patch only works for newly created nodes (i.e., after the patch is applied). It may also work if you edit/re-save an existing node, but it won't work automatically for existing nodes. This is in line with the current logic in CL that only recognises potential references when a node is created/saved (as I follow the code).
Comment #8
bengtan commentedExpiring this issue as it is old and uncertain whether it is still applicable.