After casting my untrained eye over the new module requirements for Drupal 4.6 and the cvs editasnew module there didn't seem to be anything that needed changing for Drupal 4.6. A quick test confirmed that it seems to work OK on Drupal 4.6.

Could the current module be tagged for 4.6?

CommentFileSizeAuthor
#4 editasnew.patch1.48 KBmikeryan

Comments

javanaut’s picture

javanaut commented

That sounds fine to me. There are several modules that are already upward-compatible (just because they don't use any features that were changed). I haven't had time to test much of anything out on 4.6 yet, and that's what I've been waiting for before tagging it. I'll trust that you've had it working properly thus far?

styro’s picture

styro commented

I'll trust that you've had it working properly thus far?

I'd never used it before until now, but it works fine on a prototype 4.6 site we are playing with. While it seems to work properly, it hasn't exactly been extensively tested.

We're happy with grabbing it from CVS, but tagging it would presumably get it some more testing ;)

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

I'm using it right now under 4.6, it's a great convenience when entering several instances of an event (differing only in date/time).

A couple of improvements that could be made:

1. Don't copy the path alias - it'll just be a duplicate
2. Please do copy the categories

Thanks!

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
StatusFileSize
new editasnew.patch1.48 KB

I continue to use this module regularly under 4.6, I think it can safely be tagged for that release.

Attached is a patch to implement my two requests (don't copy the alias, do copy the taxonomy).

Thanks!

styro’s picture

styro commented
Status: Active » Closed (fixed)

Just closing this old issue - I don't think anyone cares about getting a 4.6 version anymore :)