Hello,

Could it be possible to remove the dependency on blog module? There's no need to use it if the website does'nt allow other users to have their own blog (which I assume is the majority of drupal installations). Instead it could be great to have an administrative screen asking who the author is and which content type is to be used to display the daily digest.

I don't know how to do this (my programming knowledge is really poor) but I think studying "feeds module" (it makes something like this, but for a general purpose) could bring some clues.

Regards

PS: I thought I had written on this (and I even got an answer) but since I can't find it in the pretty short issue queue or my own issues I decided to post it (again?)

Comments

jadestorm’s picture

jadestorm commented

Did you not get the email from the other one? =/ Anyway, you were commenting on an unrelated issue so I closed that issue and asked you to create a new one. =D Anyway, this theoretically shouldn't be hard to implement . . . I think. As for the blog part, I actually went with that because it was enabled by default on my drupal installs and it seemed to make the most sense. lol!

jadestorm’s picture

jadestorm commented
Assigned: Unassigned » jadestorm
c-c-m’s picture

c-c-m commented

Sorry for the inconvenience, jadestorm.
I'll be looking forward to see if you succeed on it.

Thanks

dayer4b’s picture

dayer4b commented
Title: Remove blog module dependendy » Remove blog module dependency

* fixed the typo in the title.

I'm commenting so that I get notified on this. I look forward to this dependency being removed.

tomotomo’s picture

tomotomo commented

I haven't explicitly removed the blog module dependency, but a recent commit to 6.x makes this work with any content type set with the variable dailytwitter_content_type (e.g. "page"). If you don't have blog, then you should just delete the line "dependencies[] = blog" in dailytwitter.info.

trentoncolley’s picture

trentoncolley commented
Status: Active » Fixed

Just remove line 3 of the dailytwitter.info file. Problem solved.

c-c-m’s picture

c-c-m commented
Status: Fixed » Active

I'm afraid that if I remove line 3 daily twitter doesn't request blog module but instead tries to publish nodes as blog content types. I am not a programmer at all, but I've seen that dailytwitter.module has several instances of "blog". Eg:

function _dailytwitter_add_tweets_to_blog($uid, $username) {
  $tweets = _dailytwitter_pull_yesterdays_posts($username);
  if ($tweets != "") {
    // Create a new node
    $start = strtotime("yesterday midnight");
    $startdate = strftime("%m/%d/%Y", $start);

    $node = new stdClass();
    $node->type = 'blog';
    node_object_prepare($node);

    $node->title = 'Daily Twitter Posts - ' . $startdate;
    $node->language = LANGUAGE_NONE;
    $node->uid = $uid;

    $node->body[$node->language][0]['value'] = $tweets;
    $node->body[$node->language][0]['summary'] = text_summary($tweets);
    $node->body[$node->language][0]['format'] = 1;

    node_save($node);
  }

I have to assume that I could replace all instances of "blog" by "story" and the problem would be solved, but I don't feel confident about it.

tomotomo’s picture

tomotomo commented

Yes, see that line "$node->type = 'blog';"? It will create a blog type node. You can change it there, or set the variable dailytwitter_content_type to a different type if you run the latest dev version.