Project:User Comment
Version:5.x-1.x-dev
Component:Code
Category:feature request
Priority:critical
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

hi. i saw a few threads from november and then nothing beyond users reconciling with patches...wondering if patches have been rolled into a new release and if a release is coming for drupal 6.

the new "content profile module" - a d6 successor to node profile - fits this perfectly well. allowign comments on user profiles is a great sort of 'comment wall/corkboard' effect BUT only if the profile holder can moderate or at least delete those particular comments...

Comments

#1

I do plan to upgrade this to drupal 6, but I'm in the middle of a few other projects right now, so it probably won't happen super soon. If you want to take a crack at upgrading and submit a patch or tarball, I'm happy to review.

#2

thanks. i unfortunately can't write code, so i'm helpless and at your mercy ;)

is there currently any other way to do this at a user level within drupal this way (like this module) - or is this a unique permissions feature?

honestly, i feel like this should be core: and in user permissions (checkboxes like 'allow user to create pages' 'allow user to delete comments on his own pages' - doesn't it?

#3

As far as I know, there's no other way to get this sort of functionality in drupal without using a custom module like this one. It does feel like it would be a nice addition to core, I totally encourage you to open up a feature request asking for it.

#4

bummer. i'm using the new contentprofile module - allowing users to comment on that content type creates the 'comment wall' or 'corkboard' effect for a user profile, really great stuff, but not possible if hte user is unable to delete ;)

#5

It would be nice to have a stable 5 release as well :)
Many thanks for a useful module!
Expat9

#6

hi all,

today, i contacted gwen to ask when she could upgrade this module for drupal 6 and she told she is busy very much with her current project and that she would be happy to accept patches. unfortunately i am not a coder and can not make such a patch myself. so i call everyone interested to gather enough bounty to anyone who could upgrade this module.

i personally am ready to put $30.

who else and what amount?

and who could make a patch and for what amount?

#7

I am keen on this and could chip in a little.

#8

Title:is this supported? port to d6? hello?» Drupal 6 port
Category:support request» feature request
Priority:normal» critical
Status:active» needs review

I need this module for the DrupalMU installation profile so I upgraded it to Drupal 6. Attached patch is for the 5.x-1-dev version.

AttachmentSize
usercomment.patch 14.56 KB

#9

Status:needs review» fixed

@wmostrey: Thanks for the patch. It's been applied and there will be a 6 version once the packaging script does its thing.

#10

Remember you need to go to http://drupal.org/node/151289/edit/releases and manually enable the release. Thanks!

temp

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

#11

Status:fixed» closed (fixed)

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

#12

Status:closed (fixed)» active

Even with your patch I can still reproduce the issue from the original version, which is described here:
http://drupal.org/node/343037

#13

Did you see #320797: The Drupal 6 port? The patch there works as desired. You will also want the patch from #337405: hook_link_alter call was incorrect.

#14

Thanks for those links, but it seems those patches are for D6.x and I'm using D5. Is there any patch available for D5?

#15

Sorry, I thought that you were looking to upgrade to D6. I don't know a thing about the D5 version. The best I can suggest is to take a look at my patch on the other issue and see what I fixed. Disregard the mail handling code. There were some permissions problems and such.

I'm willing to try and answer questions about the D6 code, but I have only limited knowledge myself.

#16

Status:active» fixed

I am no longer supporting 5.x, so marking this issue fixed again.

#17

Status:fixed» closed (fixed)

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

#18

How stable is the 6.x dev branch?

Thanks!

nobody click here