integration with vote up down

The documentation tries to cover this in great detail, if you walk through section 2.4.1 - 2.4.9, I think you'll find how to build from the ground up. (You probably don't need to use 2.4.10, the forms feature.)

I agree that having a ground-up tutorial would be good, as well. I would prefer to write one against a 'core' Drupal content type, if one exists that the current release doesn't address.

Ok I understand... I guess with a tutorial for a normal node type i could learn from it and apply it to the type I need,,, I was just in a hurry to use this with vote up down :-)

thanks

I'm not sure how you would use this with Vote-Up-Down, since we don't use node_view() to generate the MySite content.

This is because not all MySite content is node content.

It also goes against design a little, since MySite is not meant to be a replacement for normal node views, just a personal shortcut page.

Hi,

I want to use it to add an easy way add functionnality that could permit to see storylinks that are added by specific users, exactly like for the user"s blog

Thanks

I get it now. I had to look at the storylink code.

This post is a note to clarify part of what MySite does.

MySite does not let you collect all nodes of type {x}. Simply being a node type isn't enough (IMO). Those nodes must be organized by some other control schema. In the case of blogs, it's $user->uid; storylink, the same way.

That's why there aren't includes for 'page' and 'story' -- generally, I think that Taxonomy covers those node types. I was originally thinking that taxonomy will cover Storylinks (and it will), but the organization along $user->uid makes sense as well.

The use case is "Show me all links added by {user name}."

Changing title to reflect true content.

Yes exactly, show me all story links posted by "username" and in conjunction with the content recomandation engine, people will know which username enter there, so it's really useful for a digg-like site.

Thanks for your time

What does this part mean?

> in conjunction with the content recomandation engine

CRE content recommandation engine is a module for drupal that automatically pushes content to users according to their voting patterns.

It also recommends users (for example if you vote 2 times on a story by a certain user he will appear on the list of recommended users.. Also it suggests users that have the same voting pattern as you, so you can discover new quality content more easily.

When the CRE suggests a user, a person could go to his page and directly add that person in it's list for example. That's what I was trying to say lol, sorry english is not first language, so... ;)

Ah. That's a separate feature :-)

Hi,

Actually I was not thinking of integrating the two modules directly, but it's great idea! Imagine if you could have users pushed by cre's results into the mypage user selection section!! It would be great! I'll do a proper feature request for that I guess!

But returning to the subject of this post, are you willing to build an example out of storylink node type it would be really helpful as it still seems quite complicated for me to do it!

Thanks

I think doing a tutorial is a good idea.

But since storylinks is contrib and book is core, I'll probably do the book.module as a how-to.

http://drupal.org/node/91588

I undersand the logic behind what you say, but I still think doing it for storylink.inc is a better idea, especially since you seem to have trouble getting use cases for the blog one.

Don't waste your time on the blog one if you think it's useless and so the tutorial on one content type that you'll know someone will use right away!

;)

cya, patchak

Here is the storylink.inc that I've built, I hope everything's fine with, I guess you couls have a quick look to see it it's rightly done?

btw, if you can create a po file easily for this file i'd appreciate it, I have trouble with the extractor.php

thanks

This looks right. Does it work for you?

A few minor changes, noted in the latest version of the README.

• Remove everything after the $Id tag on line 2.
• Line 20: Either use 'Storylink Posts' or 'storylink posts'. Don't mix case.
• Line 22: Default translation string should be in English (sorry).
• The comments on line 44 can be removed, it doesn't apply.
• The check_plain() on line 69 has been removed. Just use $title.
• The user access checking in the storylink_block has been moved. This simplifies your code, actually. You can move the storylink acccess check into the first IF and remove the second IF. See the README example code.
• You should write a mysite_type_storylink_block_node() function. This will show the block link when you are looking at a storylink node page. See the README.
• The $implode on line 197 has been removed.

This is good stuff.

Translation instructions http://drupal.org/project/drupal-pot.

Once you have extractor.php, put it in the mysite folder, then run from the command line:

This should generate a storylinks.po or general.po file inside the mysite directory.

Hi,

I'll try tonight... I,m not sure i have access to a command line on my server... but I guess I,ll figure it out...
thanks for the comments on the .inc file, I'll post an updated version soon

thanks

This Site is for trial.

humm brought back a title that's more related to the issue ;)

This has been added to the tarball.