This request overlaps with some of the existing feature requests.

I suggest adding a new attribute (or attributes) to each flexinode content type that defines the HTML used to render that type, in its list, individual-node, and data-entry formats. I could be wrong (if I am, I'd appreciate a pointer), but I don't think that all the things one might like to do in this respect can be handled through themes. For example, I'd like to set up a list of links, which I'd like to format something like this:

<code>
<dl class="links">
[repeating block]
<dt><a href="/[URL]">[Title]</a></dt>
<dd>[LinkDescription]</dd>
[/repeating block]
</dl>

This is somewhat oversimplified--there would need to be placeholders for the list lead-in and lead-out, that sort of thing.

If something like this actually can be done through themes, I'm all ears. Also, a "thank you" to the team for this excellent addition.

Comments

rkendall’s picture

rkendall commented

This _can_ be done with themes. Although it could be a little more straightforward.

For themeing flexinode fields I have put an example here (for phptemplate):
http://drupal.org/node/11811#comment-28887

Rob kindly posted this example for xtemplate (which I found helpful):
http://www.robshouse.net/theme_flexinode

Can this (non)issue be closed then?

Bèr Kessels’s picture

Bèr Kessels commented

IMO this is a non-issue too. This can be easily done in a themed function. Documenting thatin a manual or handbook page is more than enough IMO., And can you rhen also please close http://drupal.org/node/9700.
I did the customised dates on http://threesanna.com/ in a very simple function in about 10 minutes.

adamrice’s picture

adamrice commented
Version: » 4.6.x-1.x-dev

Bèr--

Thanks for the follow-up. I took a look at the handbook page. That describes a solution to a different problem:

1. As I understand it, what that page describes is a change in the presentation of a given flexinode field-type, wherever it is used.So if I have created two different content types that both use the timestamp field, I'm stuck with one rendering of the timestamp for both. I cannot customize it one way for one content type, another way for another.

2. It treats each field as "atomic"--that is, I don't see a way (except with additional theme-hacking) to, say, change a bunch of DIVs into LIs that are bracketed by a UL top and bottom. There's no way to use fields in a context that relates them to other fields, or to the start/end of the node.

3. I realize this stuff is childsplay for you, but for less experienced users, it's a bit intimidating to generate a couple of php files for each content type they want to tweak.

Dublin Drupaller’s picture

Dublin Drupaller commented

Hi Adam,

did you have any joy with your flexinode theming?

Dub

bermin’s picture

bermin commented

I am with Adam on this one. What is the solution to trying to combine/format two or more flexinode types in a single page? For example, one type being an image and the other type being a textfield that you want to wrap around the image. Pretty tough when you are dealing with two .tpl.php's.

Bèr Kessels’s picture

Bèr Kessels commented
Component: Code » flexinode.module (core)
Status: Active » Closed (won't fix)

Closing this feature request. We will deal with improved theming once we have most of the other real issues done.

And in the mean time there is a flexinode-theme-module that does waht you want and more.