Closed (fixed)
Project:
Node clone
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
30 Nov 2007 at 18:22 UTC
Updated:
9 May 2014 at 01:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
pwolanin commentedThere is at least one pending patch regarding
$node->name- that needs to be tested and fixed first. Did you port from the 1.x or 2.x branch?Comment #2
pwolanin commentedthis one: http://drupal.org/node/166684
please test - especially as a non-admin user.
Comment #3
panchoOh, I already tested that patch and incorporated it into my 6.0 port (which has been ported from the 5.x-2.x branch). Both here and there it worked out well. Still, I might find some time tomorrow to test everything again, and more thoroughly.
Comment #4
pwolanin commentedI just committed these patches:
http://drupal.org/node/198013
http://drupal.org/node/166684
so you may need to re-roll your patch.
also, why this change:
I always thought
$infowas a very unhelpful variable name. what's being passed in is a type objectComment #5
pwolanin commentedComment #6
robloachCould the Drupal 6 port be finished, committed to HEAD and then be branched to DRUPAL-6--1 as soon as possible please? I want to update DrupalBin to Drupal 6. I could rework the patch from DRUPAL-5--2 if that's required.
Comment #7
pwolanin commentedok, I synched HEAD with the 5x-2 branch and then worked up the attached patch. The patch above didn't apply, but I cut, pasted and edited some useful parts of it.
Passes basic testing - I'll tag and release a 6.x beta off HEAD. Please test the committed code.
Comment #8
robloachSeems to be working perfectly, nicely done! It also seems to be already committed to HEAD. Should we branch to DRUPAL-6--1 and make the development release snapshots for both DRUPAL-5 and DRUPAL-6--1?
Comment #9
pwolanin commentedI tagged and made a 6.x beta release. No point in branching now.
http://drupal.org/node/221051
Comment #10
hass commentedThis beta is not yet displayed on the project home. Fix this by going inside the release > Edit > Save :-)
Comment #11
pwolanin commented@hass - thanks, I was wondering why it didn't show up.
Comment #12
hass commentedThis is a project module bug.
Comment #13
hass commentedI think this patch is committed, isn't it? so marking as fixed.
Comment #14
pwolanin commentedyes - patch is committed - but I was still hoping for feedback on whether it works...
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.