To be done for 6.x-1.0 release [#294164]

Comment #1

heine commented 17 August 2008 at 22:41

A few bugs / compatability issues have been resolved:

#295657: JS bug after preview comment
#295645: Error after delete node

I've not yet received any bugs regarding the upgrade process from earlier versions of comment upload.

I did forget to include one other 'thing' that needs to happen before a 6.x-1.0 release. Doh!

The new list:

Views 2 integration (already working on)
Test the upgrade path
Test the module dev release

Log in or register to post comments

Comment #2

gábor hojtsy

he/him

Hungarian

Hungary

commented 28 October 2008 at 16:32

Looks like people reported several upgrade problems so far. #326668: No *old* comment uploads shown after 5.12 -> 6.6 upgrade which is about files disappearing altogether in the upgrade my understanding. #297845: Files attached to comments after upgrade are missing which is about files being listed but non-existent after upgrade. These might be the same bug differently worded (and I misunderstood the difference).

Log in or register to post comments

Comment #3

vladimir.dolgopolov commented 29 October 2008 at 09:13

I've provided a patch for #326668: No *old* comment uploads shown after 5.12 -> 6.6 upgrade.
The issue is due to using drupal_write_record() instead of update_sql() in comment_upload.install.
Not sure it is the same as #297845: Files attached to comments after upgrade are missing so {comment_upload} is not empty.

Log in or register to post comments

Comment #4

gábor hojtsy

he/him

Hungarian

Hungary

commented 11 January 2009 at 19:02

Issue tags:

+drupal.org upgrade

Log in or register to post comments

Comment #5

Rosamunda commented 21 January 2009 at 02:49

subscribing

Log in or register to post comments

Comment #6

gábor hojtsy

he/him

Hungarian

Hungary

commented 9 February 2009 at 10:21

Issue tags:

-drupal.org upgrade

It was tested a lot in Cambridge by Derek and Austin for the drupal.org upgrade. Worked with JS and without JS. Maybe need more testing, but removing the upgrade tag, since we found it fine.