Whether there will be a version for D7?

CommentFileSizeAuthor
#5 comment_edited.zip2.23 KBOleksa-1

Comments

snufkin’s picture

Its planned, but I wont have time in the near future. It would help if people would chip in, or would contribute patches though.

NPC’s picture

Subscribing, I like the idea of the module, so would like to use it on my future D7 sites.

playfulwolf’s picture

yep, like the idea also.
did not press Follow with hope to get reaction from dev's

snufkin’s picture

the developer reacted in #1, unless someone helps me, I don't think i'll have time for an update in the foreseeable future.

Oleksa-1’s picture

StatusFileSize
new2.23 KB

Until 7 version will be released I offer temporary decision

robmalon’s picture

Thanks for getting the ball rolling on this Oleksa. I was poking around the code as I might add some of my own modifications. Anyways, I was trying to understand your logic of why you have "changed" and timestamp" db columns. Both have a description of "The timestamp of the last change on the comment". And the only difference in insertion is "changed" being 1 second later than what is being put in the "timestamp" column.

snufkin’s picture

Thanks for the help, I'm happy to commit it to the repository as soon I can review the code. Could you please roll a patch against 6.x-1.x-dev?

Oleksa-1’s picture

@robmalon@snufkin really you can use only "timestamp" instead of "changed" and timestamp" in this case you will need to do LEFT JOIN 'comments' to compare data in function ok_comment_edited_comment_view . I use "+1" to exlude LEFT JOIN i understand that it is not correct way.

Also you can use user_load to get 'authname' insted to keep it in table. But I wanted to make module very quick thats why I used that 'stranged' logic;) and this code is not good for making patch. But it is easy to make correct logic in it.