Comments

Anonymous’s picture

There is a #D7CX pledge, so presumably the answer is yes. The maintainers of this module are also core maintainers, and I assume they are working on getting D7 core out now instead.

I'd like to see the improvements I've implemented get into the D7 version, and will provide patches/help/testing/whatever as needed for that to happen.

JohnnyX’s picture

Will a dev version available soon or no port started yet?

scsmith’s picture

Subscribe

jarodms’s picture

Subscribe - using this in drupal_wiki so I am interested in its progress. thanks!

webankit’s picture

Looking forward fr it +1

bart.hanssens’s picture

Is someone already working on this port ? If not, I'd like to give it a try during the (shameless plug) DrupalGov Days (April 9).
I'm not that familiar with Drupal development, but it seems a rather easy - yet useful - module to get started...

davidzz’s picture

To bart.hanssens - that'ld be much appreciated!

kanani’s picture

StatusFileSize
new11.07 KB

I started on a port to D7, but it still needs a lot of work. Biggest thing left to do is actually get the comments moved from the "view" tab to the "talk" tab. After that is finished, it will need general style/formatting cleanup.

Bart (or anyone else) ping me when your ready to start so we can coordinate efforts.

kanani’s picture

StatusFileSize
new11.03 KB

This one should work in D7.

2nd Iteration. There's probably still a lot of code that can be cleaned up but appears to be working on D7. After I've verified the test cases are working I'll figure out how to submit the whole module as a patch for D7 (never done that before)

kanani’s picture

Status: Active » Needs review
StatusFileSize
new3.18 KB

Patch against head.

Status: Needs review » Needs work

The last submitted patch, 959518-drupal7port.patch, failed testing.

kanani’s picture

Status: Needs work » Needs review
StatusFileSize
new18.58 KB

rerolled against master

Status: Needs review » Needs work

The last submitted patch, 959518-drupal7port.patch, failed testing.

kanani’s picture

Version: 6.x-1.x-dev » 6.x-1.6
Status: Needs work » Active
StatusFileSize
new18.58 KB
kanani’s picture

Status: Active » Patch (to be ported)
StatusFileSize
new18.58 KB
kanani’s picture

Status: Patch (to be ported) » Needs review
StatusFileSize
new18.58 KB
kanani’s picture

Sorry for the triple post. I was trying to get it to recognize the patch and initiate the test.

All three patches are the same.

webankit’s picture

#16: 959518-drupal7port_0.patch queued for re-testing.

JohnnyX’s picture

Will we get a (dev) release soon?

kanani’s picture

JohnnyX,

My patch needs to be reviewed before it can be committed (and possibly turned into the d7-dev branch).

If you grab the patch, and test it against your d7 install, then provide feedback that might help move the process along.

-D

Anonymous’s picture

kanani, thank you very much indeed for working on this.

I'm currently trying to apply the patch, and will test when I have.

So far, I can't get the patch to apply at all. I'm not used to using the patch command, so probably I'm doing something totally stupid and will eventually figure it out. However, if you could post detailed instructions on how to apply, that could speed things up.

What I've done is put the 6.x-1.x-dev version in sites/all/themes/talk, put your patch in that folder, and do patch -p1 < 959518-drupal7port_0_2.patch . I get:

Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file README.txt.rej
patching file talk.info
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file talk.info.rej
patching file talk.module
Hunk #1 FAILED at 6.
Hunk #2 FAILED at 44.
Hunk #3 FAILED at 199.
Hunk #4 FAILED at 236.
4 out of 4 hunks FAILED -- saving rejects to file talk.module.rej
patching file talkpage.tpl.php

Anonymous’s picture

On the theory that maybe 'patch' is the wrong tool to use, I've just tried using git.

git apply --check < 959518-drupal7port_0_2.patch
error: patch failed: README.txt:1
error: README.txt: patch does not apply
error: patch failed: talk.info:1
error: talk.info: patch does not apply
error: patch failed: talk.module:6
error: talk.module: patch does not apply
error: patch failed: talkpage.tpl.php:1
error: talkpage.tpl.php: patch does not apply

What starting point does your patch apply against?

Thanks!

kanani’s picture

Patch was build using git.

For the long version See "Applying Patches" here http://drupal.org/node/1054616#applying-patches

For the short version you need to clone talk from git.

git clone http://git.drupal.org/project/talk.git

then download the patch into the talk folder

wget http://drupal.org/files/issues/959518-drupal7port_0_2.patch

then run the git command for applying the patch

git apply 959518-drupal7port_0_2.patch

you might get some errors about additional whitespace, but the patch should apply

Macintosh-2:talk davidhazel$ git apply 9.patch 
9.patch:28: trailing whitespace.
5. If you'd like to change the text used in a variety of places go to 
9.patch:412: trailing whitespace.
 * 
9.patch:42: new blank line at EOF.
+
9.patch:379: new blank line at EOF.
+
warning: 4 lines add whitespace errors.
webankit’s picture

i agree it is stable and should me made dev

kanani’s picture

Status: Needs review » Reviewed & tested by the community

per #24 changing status to reviewed and tested by community

greggles’s picture

Status: Reviewed & tested by the community » Needs work

In general, it seems like this patch might be against the wrong branch and incorporate a mix of changes made in Drupal 6 and other stuff.

+; Information added by drupal.org packaging script on 2011-02-25
+version = "7.x-1.x-dev"
+core = "7.x"
+project = "talk"
+datestamp = "1298620330"
+
+

That all should be stripped from the patch.

-      $output = '<p>'. t('The talk module gives you the option to display comments on a seperate tab. The option is per content type and can be set in the workflow options of a content type.') .'</p>';
+      $output = '<p>' . t('The talk module gives you the option to display comments on a separate tab. The option is per content type and can be set in the workflow options of a content type. You can control the text that shows in the tab, title, and link to the "talk" page.  You may use tokens in the patterns you set such as [title-raw], [node_comment_count], or [unread_comment_count].') . '</p>';
 

In the future it's best not to make changes like this as part of a port. You should focus the port on just the parts related to making it work on the new version of Drupal.

+  return ( $access = 

Why are you assigning $access this value? Also you have an extra space between "( $"

+  drupal_set_title(check_plain(talk_title($node, 'page')));

In Drupal 7 drupal_set_title already does a check_plain, so this will double encode characters in node titles.

I stopped reviewing at that line as I'm out of time for now.

kanani’s picture

Thanks, my primary focus was on getting a D7 port working. I'll go back and do some work to cleanup / remove extraneous code.

chapatt’s picture

Thank you so much for your work on this kanani. I'm trying to migrate to D7, and I really like this feature for wikis.

kanani’s picture

Happy to help chapatt. Did it work ok for you? Any issues?

BenK’s picture

Subscribing

cwgordon7’s picture

Status: Needs work » Fixed

I've completed the port to Drupal 7. Please report any issues as new issues in the queue, not here. Thanks!

acolyte26’s picture

Hi, Where is the link to download the dev version of drupal 7. I would like to try it.

Status: Fixed » Closed (fixed)

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

rfay’s picture

Congratulations on this!

Probably time to remove the #D7CX pledge from the project page :-)