I would like to put the storm menu in a block for reuse in a custom panel?
Any ideas or suggestions where to look?

CommentFileSizeAuthor
#4 organization.PNG93.59 KBqriz
#4 project.PNG81.01 KBqriz
Capture.PNG116.28 KBqriz

Comments

qriz’s picture

qriz commented
Assigned: qriz » Unassigned
Magnity’s picture

Magnity commented

@qriz,

Take a look at the code in theme_storm_link (storm.theme.inc) and a function like theme_stormorganizaton_view (stormorganization.theme.inc).

You should be able to use that code to recreate the links, and you'll need to know the nid and node type of the node that you are linking from.

Magnity’s picture

Magnity commented
Status: Active » Postponed (maintainer needs more info)

Wondering whether you've managed to solve this?

qriz’s picture

qriz commented
StatusFileSize
new project.PNG81.01 KB
new organization.PNG93.59 KB

I cleared all the (for this site) unneeded code from the stormorganizations body, so that just the menu and taxonomie images are left and set the floating to the left. Then I created a new panel for type stormorganizations and reused the body as a block (marked in yellow). I also moved most of the menu directly to the type stormproject, since that's how the work flows in that company. It might not be the most sophisticated way to handle this but at least all functions are still working after messing with the code. I'm still working on it as you can see in the snapshots.
And like I said before this module is awesome .... thank you guys so much for sharing it!

Magnity’s picture

Magnity commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Great. Looks like this support request can be closed.

If any of the code turns out to be reusable, please do share it here in case others want to do a similar thing!

qriz’s picture

qriz commented

Sure ;-)

Branjawn’s picture

Branjawn commented

@qriz, can you share exactly what you did to achieve this in a step-by-step tutorial?

qriz’s picture

qriz commented

It's NOT recommended to do what I did because all changes will be overwritten by the next update!!!

What i did was: uncommenting pretty much every entry beginning on line 43 in storm/stormorganizationstormorganization.theme.inc
and line 48
storm/stormproject/stormproject.theme.inc
what includes any fields (since I had build mine with CCK way before i learned about storm)

Then i had just the menu in the body of each node and could reuse it through panels but like I said, the fact that updates overwriting all changes, is making that a bad approach!