Hello there, the module is very interesting I am testing and trying to get my head around it.

As much as i can see the 'layout compositions' configured per node, is it right? Therefore that is the fundamental difference/approach with the panel.module.
If is true 'per node' approach as much as it gives a flexibility of it also increases x-fold the workflow -especially for a a high workflow site -like newspaper/magazine type sites that you & prosepoint specialise.

Instead would not be better to extend the module with a 'zone sets' named & configured on module configuration than made available choose a set by each node type and optionally by each node with a one click?

When i first saw the module name and the image of the prosepoint_demo_screenshot. gave me this kind of 'set's idea as it shows a columned composition of nodes

maybe there are Composite sets options that i am missing because of the lack of documentation or i might just have a tired eye and brain :)

thank you

Comments

bengtan’s picture

bengtan commented

Hi,

... I am testing and trying to get my head around it ...

Well, if I had written sufficient documentation, perhaps it wouldn't be as weird to understand :)

Except that I think I'll wait for the module to stabilise a bit before writing documentation. I've already had a couple of feature suggestions which might change things a bit.

Originally, Composite Layout was called Composite Node (the file was composite_node.module) because I thought of it as a layout composed of multiple nodes. Somewhere along the line, the module evolved into working with more than just nodes.

If is true 'per node' approach as much as it gives a flexibility of it also increases x-fold the workflow -especially for a a high workflow site -like newspaper/magazine type sites that you & prosepoint specialise.

Yes, but the module is written so that if you don't want to use a complex layout, you can just ignore it. No increase in workflow unless you want to.

Instead would not be better to extend the module with a 'zone sets' named & configured on module configuration than made available choose a set by each node type and optionally by each node with a one click?

Possibly. I've already had feature requests to make it possible to have default layout settings by node type. This is similar to what you're suggesting.

I'm open to the idea, but I haven't really thought it through as I have other (non-Composite Layout) priorities at the moment.

maybe there are Composite sets options that i am missing because of the lack of documentation ...

Nope. There isn't.

There might be in a future version, but it'll require some work and some thought on what/how to do it.

ica’s picture

ica commented

Thank you for your reply bengtan, its cleared out my questions
your module is great for a low to none workflow -like an artist or brochure promotion site,

seems like without a solution of compo-sets -and default set(s)- per node is no much of use to achieve a magazine/newspaper website modularly for per node type or/and taxonomy based compositions.
for sites like
cnn.com, iht.com etc.

So major Drupal mag/newspaper sites had to rely on combination of theme coding, Panels, Views rather than a 'global/sitewide' solution

I have to look again to your prosepoint demo how you worked it around.

thanks

bengtan’s picture

bengtan commented

ProsePoint is using the module Node Clone (http://drupal.org/project/node_clone) for templating, sort of. Each time you want to create a new composite node, you can just clone it and then make the changes you want.

ica’s picture

ica commented

Yes, I gathered this after i looked to the prosepoint demo site nodes, that's the way-around solution you made use of.. that essentially a 'composite' is a node (without a body or any fields, so by giving them zones and with cck_reference you assign nodes to it you faciliate a composition for group of nodes/categories -rather than creating zones for each node -as the pompostie site tabs suggests on each node edit...

hmm...
but also because its a 'way-around' solution its difficult for grasp + not sure its viable for a long term lifespan of a cms as more fundamental solution might be built into core or to a better module in future and difficult to convert a site which is already have x-number of content
meanwhile your module is a solution and it works that is important

bengtan thanks for your replies, sharing your work, and providing demo access to prosepoint for a peak -that was useful to understand your approach-

zilla’s picture

zilla commented

@bengtan - cloning a node is obviously a great way for admins to do this, but oddly i was about to submit a feature request for this exact same thing

when i originally set this up, i configured this awesome node layout for a node type 'story' (after setting up for content type) and then saved it, was thrilled, then went to create another test story and realized that the layout was not saved for re-use!

so there are two ideas for this 'sets' thing

1) it is a default 'set' created by admin that is in turn available to any user who may create content (sort of a new approach to content templates if you think about it that way too) - so each 'content type' can have an easy to configure custom layout defined by admin

2) it is an option during node creation for users with permission to access the module's utility and to 're-use' a named set if one has been created for the content type -or alternatively, override the existing set with a new one, revert to default etc...

it could be both of those things...so imagine this workflow:

install module, set it up, configure content types etc and then go to create (for example) a "Blog" entry
-when a "composite layout" is set up for the node type "Blog" for the first time, the module simply says, "would you like to save this composite layout to use again for content type "blog"?
---2 choices are given:
-------yes, but do not set as default layout for all content of type 'blog'
-------yes, and also set this layout as default layout for all new 'blog' content created

that opens the door to a simple tab in the module to view a list of these 'layouts' and see which content type is using what - makes an admin job way easier if there's lots of content types being handled and tweaked...

at any rate, that's the dream - the ability to either recycle layouts (use endlessly for a content type) and/or set as default layout for all content of that type

just a thought, sounds like i'm already in kahootz with the dude who started this thread too...this could become like a "simplepanels" module if this were the functionality (even if it doesn't present end-product to panels module, but you know what i mean)

strangeluck’s picture

strangeluck commented

really enjoying this module so far and i must say that zilla has an excellent suggestion regarding creating a default set for users to access. don't have anything constructive to add here beyond saying that i too desire such a feature.

zilla’s picture

zilla commented

hello folks, just wondering if there was any more thought to my idea above about reusing layouts - honestly, i'd really like to use this module instead of panels for most of site layout for standard content types (and maybe just panels for organic groups, or perhaps this for OG instead?)

as an admin, this is awesome for admin-generated pages, like a custom home page or about or whatever, but if it were extended to all users as a default layout configuration for content types, it could create some very nice utility for site design and consistency....just a thought ;)

bengtan’s picture

bengtan commented

Hi,

I have been thinking about it on and off over the last few days, but didn't have anything concrete to add.

I would like to implement this 'Composite Layout Sets' feature, but I just haven't had time to work on it.

bengtan’s picture

bengtan commented
Status: Active » Fixed

Hi,

Have a look at 6.x-1.0beta4. There is a "layout sets" feature, whereby existing layouts can be saved and then retrieved.

To find this feature, you need to be on the Zones tab of an existing node. Then look at the update Tasks at the bottom of the form.

Didn't quite implement 'default layout sets' in the way suggested, but perhaps the functionality in this release is close enough?

Anyway, let me know how it goes, and if you do have further comments, feel free to set this issue back to active.

zilla’s picture

zilla commented

excellent - could this same implementation be used to set the layout as a default for all nodes of such a type via admin controls? (e.g. admin creates the set, then users have to use it no matter what and do not see any such options to change or override)

bengtan’s picture

bengtan commented
Version: 6.x-1.0-beta1 » 6.x-1.0-beta4
Status: Fixed » Active

> a default for all nodes

Well, I started to add something like this into Composite Layout, but then postponed it because I needed to clarify and review what people have actually requested.

> (e.g. admin creates the set, then users have to use it no matter what and do not see any such options to change or override)

If you have a default layout set for all nodes of a content type, then you can't turn composite layout off for an individual node ie. in the node edit form, you select 'No composite layout' but then the default layout set functionality would kick in and actually populate a layout set for you. This would not be according to the user's instructions.

zilla’s picture

zilla commented

@bengtan, i think the 'default for all nodes of content type X' is the general request, though certainly worth confirming - and then the ability to turn off for individual nodes (or set to off with ability to turn 'on' which is basically what IS there in the beta)...and of course, as admin the ability to not present these layout options to users by role (standard permissions, like 'can access sets or use sets')

this could open up a very interesting road for networking sites where admins want to give users some choice,but restrict certain things - so instead of just letting users choose (for example) a theme for their blog, they could also choose a predefined layout (like '2 column blog' or 3 column blog), but the admin actually decides where in those layouts the content will actually be going (meaning admin has blocks for ads in fixed positions and so on) - that is something that panels can *not* do!!

chrysonline’s picture

chrysonline commented

very good module !

layout set is great for many pages !

bye

bengtan’s picture

bengtan commented

@zilla and others: 6.x-1.0-beta5 has been released with default sets functionality. Please have a look and test.

@ica: With latest functionality, you might be able to do "creating zones for each node". If you have a complex node type with many CCK fields, you can arrange these fields into a layout, save the layout as a set, and then specify that set as the default layout for all new nodes of that content type.

fabius’s picture

fabius commented

Hi,
I had to read the above to find the "layout set" functionality. You tucked it away. But the idea is great. Many of us create sites for small companies. They want to display their products with a pic and some basic fields on price, shipping, size, etc. If I create a new content type and call it "New Product" I can set permissions so that authorised users use only this (and not the alternatives). Then adding a new product to the catalogue is foolproof (or so I hope). Virtually no IT skills required and little damage can be done.

The same thing applies to any site that has a series of nodes with the same layout and fields.

I know nothing about panels but I think your module fills an obvious need.

Perhaps I can write a few extra lines for the project page?

fabius

bengtan’s picture

bengtan commented

> You tucked it away.

Yes, I didn't want to create another set of pages (and yet another draggable blocks form) just for layout sets (and I though placing it under Content Types was clunky as well). Not sure if this is the best interface in the long run, but hopefully it will suffice for now.

> Perhaps I can write a few extra lines for the project page?

That would be very welcome. I think the handbook documentation page http://drupal.org/node/320864 is a better choice than the project page though. Perhaps create a separate book subpage if you want to add your information as a separate section?

Thank you.

dddave’s picture

dddave commented

Well, you tucked it away pretty good at least for a noob like me.

Where can I enable the default sets functionality? I might be missing something completly or I might have completly misunderstood the commentaries above but as far as I understand it this functionality does exist, doesn't it? Or do I have to downgrade to beta 5?

Such an feature would be awesome and solve much of my problems (fantastic module even without it, by the way).

So could somebody enlighten me please? I might be a bit slow today but nevertheless I would be very thankful for any guidance.

dddave’s picture

dddave commented

Ok, my bad.
I figured it out now.

I explain it briefly for slowthinkers like me.

1. Enable Composite Layout for the content type.
2. Create content and configure the zones.
3. Tick the boxes behind each zone and make use of this nice "tasks"-menu. -> choose "Save as new lay out set"
4. Save complete lay out.
5. Go back to admin/content/types and "edit" the content type you chose in step 1.
6. Under "Composite layout" anew field was added "Default layout set".

After figuring out how to do it I felt really slowthinking but also very glad because this option really is gold!

Good work!

fabius’s picture

fabius commented

Fabius
I'm back. And I think I have a new issue.

I created a new Content Type. I installed Composite Layout and it works just fine (up to here). Then I added ImageCache because I want the server to resize a photo after it is uploaded. I created a preset and it appears under ZONES (foto640 linked to node). I saved the layout set.

However, when I create a new instance of the Content Type (specifying the Layout Set) the photo appears full size. Refresh has no effect. I go to ZONES and find the foto field has changed to "image linked to node". I change it back, select the layout set and save the ZONES. I click Edit and find the menu setting has changed and the Layout Set radio button is deselected. I fix that and save. The page and photo display perfectly.

But I need to make this much more automatic. The owner of this site has limited experience with PCs.

Summary:
CCK + Composite Layout + ImageCache
- ImageCache preset for image field is ignored and switched by the layout set on first attempt to upload node.
- other spooky things

This module serves a great purpose. Please tell how to fix it.

fabius

bengtan’s picture

bengtan commented
Status: Active » Fixed

Marking as fixed since the discussion of the original topic has concluded.

@19: Please file a new feature request if this is still important, although I don't think I will have the time to do it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.