The current implementation of flexinode_content() makes it so that theme_flexinode_x methods are ignored. This patch splits the method into 3, allowing for the theming of the html that contains the flexinode and the individual flexinode types as well.

flexinode_content($node)

function theme_flexinode(&$node)

function theme_flexinode_content_type(&$node)

CommentFileSizeAuthor
flexinode.module_0.patch1.26 KBrobertdouglass

Comments

jjkiesch’s picture

jjkiesch commented
Category: task » support

this appears to be exactly what i was looking for. is there anymore documentation on the usage? maybe some examples as well?

Bèr Kessels’s picture

Bèr Kessels commented
Category: support » feature

jjkiesch, remember that if you change the issue or project information, you do so for the whole project.

factoryjoe’s picture

factoryjoe commented

I'm all about more themability, so I'm for this if someone else can verify the code or setup a sandbox for me to see this in action (I really feel like I'm somewhat handicapped by not speaking PHP patches as a primary language!).

Bèr Kessels’s picture

Bèr Kessels commented

I might misunderstand this issue, but theme_node allows themeing on node level, per node type, already. o need to add more theme functions, IMHO.

-1 from me.

Dublin Drupaller’s picture

Dublin Drupaller commented

has anybody found any decent documentation for non programmers on how to theme at the node level for flexinode?

Have created a node-flexinode-x.tpl.php file..but am unsure how to theme the content.

had a look at the node_theme tip..but I'm not sure how to use that...

Dub

magnestyuk’s picture

magnestyuk commented

this might be a solution:
http://drupal.org/node/26398

urbanlegend’s picture

urbanlegend commented
Version: master » 4.6.x-1.1
Component: Code » flexinode.module (core)
Issue summary: View changes
Status: Needs review » Closed (outdated)

Given that this issue has not been updated in 11 years or more, I am closing this ticket as outdated (no longer needed and/or relevant). However, if anyone feels this represents an issue that is still being encountered in the current version of Drupal, please reopen and/or provide additional comments.