Hi guys,

I had a need to have the body (or teaser) without the footnotes and the footnotes separated when being displayed in a view. The result is that I can show the teaser, some other things (i.e. read more...) then the footnotes. You can see the result here:

http://snapwebsites.info/journal

It could be neat to have that integrated in the module directly. At this time, one can use the Mini project to incorporate that functionality.

Just wanted to let you know.

Thank you.
Alexis

Comments

hingo’s picture

Is there a patch?

Also, in your example website, I see the footnotes in teasers just like I'm used to.

Also, have you seen #209037: Exclude foot notes in teasers

AlexisWilke’s picture

hingo,

It's not a patch, it's a separate module. See mini/mini_node_footnotes_views*   and you can keep it as a separate module! I'd just have to rename it if you don't mind integrating it. Now, we could also have it directly in the footnotes views module if you don't mind. It would be more effective as you would not glue the two string together in the first place (if possible... I did not look closely.)

I can create a tarball if you want, but Drupal does a great job at that already... 8-)

The "read more..." link appears BEFORE the footnotes. It's not as obvious as before when I had all the links which I removed from that page, but without this extension the "read more..." would appear after the footnotes and thus it would "break" the intended look.

You can check out this other page which is from the Core Blog module. And the cut is created in node.tpl.php in that case, but the effect is the same.

http://snapwebsites.info/blog

Thank you.
Alexis

hingo’s picture

Status: Active » Needs review

I like it! I just moved the files from your Mini module and renamed them to footnotes_views*.

I've never used Views. Can you test the new 6.x-2.x-dev and let me know if it happens to work.

Is there some common naming style used for modules that support Views API? I named this "Footnotes with Views".

I liked the approach of keeping this fully outside of the original footnotes.module so I want to keep it that way, even if they are part of the same download. It makes the code easier to work with when a piece of functionality can be completely independent of the rest of the code. If we ever change the output of the main footnotes module, that would be the only case were the search string in strpos() would have to be updated to match. Other than that this is a very clean separation worth keeping.

Also, I've given you CVS maintainer status for Footnotes, so if something is wrong, just fix it yourself :-)

hingo’s picture

I think drupal.org will have sent you an email already, but just to be sure, pleas also see: #1003690: footnotes_views should take into account that the footnotes needn't be at the end.

hingo’s picture

Component: Footnotes » footnotes_views
Assigned: AlexisWilke » hingo
Priority: Minor » Normal
Status: Needs review » Fixed

Tested a little, this seems to work.

(As an independent issue, #1003690: footnotes_views should take into account that the footnotes needn't be at the end. does not work.)

AlexisWilke’s picture

hingo,

Ah! Sorry... still did not find the time to test this. Thank you again for implementing this here.

Alexis

Status: Fixed » Closed (fixed)
Issue tags: -views

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