Project:Taxonomy Access Control
Version:7.x-1.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:closed (fixed)

Issue Summary

I'm just wondering if you're planning for a D7 version of TAC, and if so, what sort of a timeline it's on.

Comments

#1

Status:active» postponed

#2

Marked #820400: Drupal 7 version as duplicate of this issue.

There's no D7 branch at present. I've postponed this issue since I don't have time this summer to work on a D7 port of the module. I'd like to see a D7 version, but I'm not going to be maintaining any D7 sites during the next fiscal year. I don't think keve has plans to work on a port either.

If someone else creates a port I can help with its development this fall, but it's unlikely it will make D7 release.

#3

#4

subscribing

#5

This is a critical part of some Drupal systems I manage, so I'll definitely be keeping an eye on this. Without looking at the underlying code or comparing functions, at a basic level it seems sensible to pursue a TAC/TAC_Lite merge.

#6

Subscribe

#7

Status:postponed» active

subscribe

#8

subscribe

#9

subscribe
#3 interesting, Would love a more lightweight version and reducing duplicate functionability

#10

subscribe

#11

subscribe

#12

subscribe

It would be nice to have it in D7. Already using it in D6 and will have to wait for something similar before moving to D7.

#13

subscribing

#14

subscribe

#15

subscribe

#16

subscribe

#17

Hello !
#623660-3: TAC: D7 port#3 seems to me a great idea !
Do you already have a porting plan, or decided what would be in the liteweight version of TAC_Lite/TAC and what what would maybe come as a complementary module to add the other features TAC and TAC_Lite currently offers?
I don't know much of these modules, but I have some time to code (with let's say a guiding help from someone who know where this module combinaison is going ...)...

#18

subscribe

#19

@ #17: I haven't started work on this yet, but I'm hoping to do some planning two weeks from now at DrupalCon. I'm still interested in making TAC and TAC_Lite one project, but TAC_Lite opened a partial port to D7 just yesterday.

Some more information for those who are curious. TAC by itself is going to be less than straightforward to port, for three reasons:

  1. Database abstraction layer changes: DBTNG has a big impact on TAC, because we use a BIT_OR aggregate that is not exactly your run-of-the-mill SQL. Historically even older postgres has required special support within the module.
  2. Taxonomy changes: The taxonomy system has been entirely redone in D7 and there are lots of new hooks.
  3. Core access control changes: There are lots of new hooks available and we may want to take advantage of some of these.

#20

subscribing

#21

subscribe

#22

Hi All,

I agree with xjm. I'm planning to create something similar to acl module, that can be a base for any taxonomy-based frontend. This will have all the features of both tac and tac_lite. In the longer term, I think it should be possible to merge the module with acl.

Please contact me, if you're interested in cooperation. The more the merrier!

Tomek

#23

@tmuras / anyone else who's interested: If you're going to be at DrupalCon, let me know if you're interested in talking about TAC in D7 or helping port it. (You can use my contact form to email me.)

#24

Title:D7 port?» TAC: D7 port

Following.

#25

Here's where I am in the D7 port process. I'll update this as I work through it. Update: the 7.x-1.x branch is now open and a -dev snapshot will be available soon. However, the branch is more or less nonfunctional at this point, so don't get your hopes up just yet. :) Please let me know if you want to help work on one of the tasks below.

  1. Run through coder for obvious API changes. Done
  2. Get V/U/D ops in hook_node_access_records() working properly for automatically-generated term access data. Done
  3. #1097782: Admin forms in D7 Done
  4. Research DBTNG API and migrate queries. Done
  5. #1097770: Update schema for D7
  6. #1097776: Update hook_menu() for D7
  7. #1097798: D7: implement create and list ops and provide API
  8. #1097804: TAC Fields D7 port
  9. #1097806: Provide Views 7.x-3.x filters for each permission
  10. #1097816: Update INSTALL.txt, UPDATE.txt, and README.txt

#26

Version:master» 7.x-1.x-dev

#27

Status:active» needs work

#28

Category:support request» task

Hey, I'm interested in helping out a bit. (After too much time working on D7 core and with that finally released, I've recently started to remember again that contrib modules exist and have been trying to work on some of them, so you caught me at a good time at DrupalCon :)

I can volunteer to work on items #4, #5, and #6; they seem like the best places to jump in. I hope to get to this in the next several days.

Since there is now a 7.x-1.x branch, does it make sense to close this issue and open up smaller ones for the actual tasks that need to be done?

#29

Thanks David! I opened the following issues:

#1097770: Update schema for D7
#1097776: Update hook_menu() for D7
#1097782: Admin forms in D7
#1097798: D7: implement create and list ops and provide API

I'll leave this issue open for now so I can reference it on the project page.

#31

subscribe

#32

subscribing

#33

subscribing

#34

subscribe

#35

subscribe

#36

subscribe

#37

subscribe

#38

As part of my employer's drupal efforts, I have written a Drupal 7 version of TAC from scratch. If anybody else would like to try it out, its available from svn at http://gforge.unl.edu/svn/wdn_thm_drupal/branches/drupal-7.x/staging/sit... (username anonymous, no password)

#39

@ spam38 - your link, after logging in, gives me an error message - "no mime type"

#40

Hmmm. If the port works, that's awesome, but I'm a bit concerned about it being written from scratch. It would be missing seven years of bugfixes, if that makes sense.

In any case, quite interested to see the code, if a working archive can be posted. I've had to put my Drupal development on hold for a few weeks because of other requirements at work, but I will take a look at it whenever I get back to working on the port.

By the way, if anyone else wants to help with the existing port, there is a D7 branch in git and there are several specific issues open (as above).

#41

Subscribing.
Edit: FYI: 7.x-1.x-dev: http://drupal.org/node/1089904
(not showing on the module front page, but on the "all releases" page)

#42

Subscribing

#43

Subscribing

#44

subs

#45

subscribing

#46

subscribing

#47

subscribe

#48

subscribe

#49

subscribing

#50

Subscribing.

#51

Re: #41 -- That is because it is not functional yet. :) I unfortunately had to drop work on this due to other circumstances.

#52

subscribe

#53

Just to let everyone know, the Austrian BIFIE is sponsoring development of the 7.x-dev branch. A functional development version should be available by July 11.

#54

subscribe

#55

me too

#56

Happy to test and provide feedback when the dev version becomes available.

#57

I have added the issue tag d7 release for issues that need to be resolved prior to a D7 release. The next major task is to get the create and list ops working (#1097798: D7: implement create and list ops and provide API). After that, the dev branch should be functional enough for people to begin testing.

#58

subscribe

#59

Status:needs work» fixed

Drupal 7 Port Complete

The Drupal 7 port is complete, and the development build is available for testing:
http://drupal.org/node/1089904

Notes and Known Issues:

  1. All the module's basic functionality is present. View, Update, Delete, Create, and List grants are functional; and access is updated in response to node and taxonomy changes.
  2. The module's internal API has been refactored significantly, improving perfomance, permitting better interoperability, and reducing the risk of future regressions.
  3. The create and list grants have been entirely re-designed in the backend, in part because of API changes and in part because of many previous and outstanding bugs in 6.x-1.x and earlier branches:

Recommendations

  1. Do not deploy the dev build in production without significant testing.
  2. Use the Devel module during testing for accurate feedback on node access behaviors. For more information on using devel, see the module documentation. (There may be minor inconsistencies with Drupal 7 in the instructions.)
  3. If you are using a field widget other than those provided by core, Multiselect, or Hierarchical Select, or if you are using some type of taxonomy field other than core's term reference field, test to see if the field behaves as expected when the user does not have create grants. If it doesn't, please open a feature request to support this widget.

What is needed for a 7.x-1.0 release

  1. Help test! I do not have any production Drupal 7 sites, so I need as much help testing the module as possible.
  2. Issues tagged d7 release need to be resolved before we create a release version.
  3. Please, please report any bugs you find!

If the 7.x-1.x-dev build of module works for you, feel free to leave a comment below! However, if you encounter a bug or have a feature request, please do not re-open this issue. Instead, check the open 7.x issues or create a new issue if yours is not yet listed.

#60

Status:fixed» closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.