Closed (fixed)
Project:
Taxonomy Term Permissions
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 Feb 2009 at 22:42 UTC
Updated:
27 Mar 2009 at 04:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
deviantintegral commentedThanks for reporting this. Can you try the following patch to see if this fixes it? It looks to be caused when the #weight (or any other # property) is specified for the vocabulary element.
Comment #2
deviantintegral commentedThe above only removed the error, at the cost of showing all terms!
Try this one instead.
Comment #3
deviantintegral commentedSetting proper status for this.
Comment #4
arlinsandbulte commentedConfirmed: Patch 2 fixes this error
(hurray! my first patch review!)
Comment #5
deviantintegral commentedThanks for testing this. I've committed the fix.
Comment #6
arlinsandbulte commentedThis latest -dev release did not implement the fix.
md5_file hash: da6b53a25d3676241a03584982176baa
Last updated: March 13, 2009 - 00:23
Comment #7
deviantintegral commentedAre you sure? I just downloaded that tarball and it contains both patches; the CVS revision is 1.4, which is correct. The md5 sum matches for me as well.
Comment #8
arlinsandbulte commentedYes, I am sure. I downloaded the module from the project page.
I think it is unchanged from the 1/17/2009 release.
I can apply the patches to the latest -dev with no problems.
I did this a bunch of times... thinking I was grabbing the files from and old directory or something.
I am pretty sure I am doing everything right.
Comment #9
arlinsandbulte commentedHmmmm... something may be wrong on the drupal server...
The project page shows a file size of 9.61 KB.
The file I download from there is 9.27 KB (9,495 bytes).
Also, even after updating, Drupal reports page still shows out of date term_permissions module.
Comment #10
deviantintegral commentedSounds like you might be hitting a web node which isn't updating properly.
Try again in 12 hours, and if you're still getting the old file, open up an issue in the Drupal.org infrastructure queue.
Comment #11
arlinsandbulte commentedCleared all private data in FF3 and now it downloads the right one!!!!
Sorry for the confusion.
All is well.
Comment #12
deviantintegral commentedNo worries - glad you got it working!