Hi all,
I am attempting to use the Taxonomy_Access module with a new 4.5 install.
I run the mysql file to update the database and copy the module to the module folder and enable.
I can go to the users section and click the Category Permission and bring up a list of roles to edit.
The links to edit those roles is bringing up a 404 error buy the way....but I got around that by manually pieceing the correct link together. From there I happily apply changes to a "User" role for each individual category.
Then I log in as a user from that role and egads! I can still create content in categories that I am not supposed to be able to access!
I have ready about this on the forums and it seems that there is a patch that I can apply to the original module file?
Well I read up on how to patch and when I try to run....
patch < taxonomy_patch I get..."Can't find file to patch at input line 1"
Does someone have a patched version of the Taxonomy_Access module?
Can someone tell me if I am on the right track to make the Taxonomy_Access module overright the basic roles permissions?
Can some one tell me where babies come from?
Jim
Comments
Read the README
The file taxonomy.patch comes with the module. In order for this module to work, you must apply taxonomy.patch to taxonomy.module. Instructions are in the readme, where it says:
"taxonomy.patch is a patch for 4.5.0 of taxonomy.module that makes sure users don't see or update to categories if they don't have the proper access."
Thanks for the tip but...
I have tried patching the two files with no luck. I get an error message just about any way I go about it. The error is listed in my top post. Does some one just happen to have the patched version of the module they can email me?
Or am I doing somthing wrong when I run....
patch < taxonomy.patch
Do you need shell access?
To run the patch do you need shell level access? I don't have that, can I still install the module?
Do it locally
If you don't have access to the shell, just do everything locally and then upload the patched module to the server.
You can also try the overhauled version
I recently made many significant changes to the module. Though it's not the "official" version yet, you may want to use it. See http://drupal.org/node/12892
Also, the entire module is there. No patching required.
Patching IS required
I think the original poster was having trouble with patching of the core taxonomy.module that is a prerequisite of taxonomy_access.module.
I assume this patch is still required for your new taxonomy_access.module to operate? There is nothing written to the contrary.
--
Brian.
Yes, you are right
Yes. I misunderstood. I thought he was patching the access module.
By the way...
My module still works pretty well without the patch as far as I know. However, without the patch installed, instead of getting an "Access denied" message, you see the category title with no nodes.
How do we patch?
How do us non- shell access people patch files? Anyone have a simple detailed answer for the techno-novices out there? While I'm at it anyone have a simple explanation for what the heck database prefixes are and how to multi-site; sorry, a whole new topic I know.
Read the manual
Best advice I can give you is to read the manual. You'd be eating up a lot of people's time if you asked everybody something you didn't know.
As far as patching goes, what computer are you running at home?
the manual
read the manual on db and didn't really get it. People like me need more examples than explanations because we don't understand all the terminology. I'm using windows xp as far as patching goes. Thanks
You don't have the vocabulary
You don't have the vocabulary yet. Check out http://tortoisesvn.tigris.org/ for a nice Win32 tool. You are asking for an explantion you are not ready for yet. When you move beyond the basic modules, you are now moving into development.
You will need to spend some time learning a whole new vocabulary and language. Teaching development is beyond the scope of the Drupal developers.
Note: Beyond the theory, I don't know how to patch a file. I do know what the process is though. :)
http://en.wikipedia.org/wiki/Software_patch
Here is a link that has the manual index
http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/index.html
The 'overview'
http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/ch04s17.html
How to apply a patch
http://tortoisesvn.tigris.org/docs/TortoiseSVN_en/ch04s17.html#tsvn-DUG-...
Note that there is a lot missing here. What I knew that you didn't was that Tortoisesvn existed. Now you know what I know, go forth and learn. :)
Now that you have a nice tool, you need to get familier with CVS. Here you go:
https://www.cvshome.org/docs/
Now you are where I am. Welcome to the learning circle, pull up a document and start playing.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
But isn't the point of Drupal
To make it user friendly, so that any knucklehead like me can use even the advanced features. It seems like the attitutde should always be about finding ways to make things simple simple simple, for the average user, so that everyone doesn't have to become a developer to get drupal working to its fullest potential. I know this is a longstanding issue between the tech world and the others (see "Nick Burns: Your company computer guy" on SNL for examples), but the great systems are the ones that can be both flexible and user friendly.
Thanks for the links, and I will go and learn, but many people won't and will just give up on Drupal, or whatever CMS in favor of some crap they pay a bunch of money for.
I know about the stereotyping
I know about the stereotyping. I don't watch SNL.
The developers are making great strides towards making Drupal easier to use. However, Drupal is flexible. That flexibility has a price in that you need to be willing to invest some time up front in learning it and getting it ready.
That said, they need more contributers and developers to work on the areas. You do not have to be a developer to contribute either. If you figured something out that you feel is not documented, then write it up and submit it to the documentation for inclusion. I can't teach you software development or php. However, I can lead you to some information that should help you get there, which I did.
You will notice that Drupal has a roadmap of development and that some of the things on it may be things you desire. If you can't develop, then you can certainly test what is being developed and submit the results.
Just watching the development traffic list I have learned a lot about development.
Check out the development roadmap for directions.
http://drupal.org/node/12202
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
In an ideal world, yes
In the future, backyard mechanics will have an army of engineers at their disposal to build robots that will modify their cars anyway they like in no time flat.
And, in the future, every open source software user will have an army of programmers and document writers to smooth the way so every custom software modification is painless, thought-free, and easy.
But until the future arrives, I'm afraid you are stuck with the prospect of rolling up your sleeves and getting a little dirty with the rest of us lowly grunts. If enough people do that, someday the future will arrive.
Your second option is to use an exceptionally good, albeit imperfect, piece of software and wait, pray, ask, or pay for the changes you need to be made to the software.
One Idea
this may be considered sacrilege in the programmer world, but why not include a patched copy of files in modules that require patching? You could include the patch for those that want to understant the changes, and the full file for us boneheads. And believe me I am a bonehead. I spent all day with tortoisesvn trying to figure out how to patch one file on my local computer. I tried merge and all kinds of things, but couldn't figure out how to take taxonomy.module and put the patch in it. Quit laughing. Seriously, what's wrong with including the patched versions- if anyone wants to post them I'm sure more people then just me will be happy.
One simple reason
What happens if you want to install more than one patch? It becomes impossible.
Under your proposal, you'd to have every combination of the module with all of the various patches that everyone has written. Of course, this would be a maintenance headache.
On Linux, patching is quite simple. One command:
patch file1.module file2.patch
Maybe you can find a command line patch tool for Windows that makes it this easy, too. I'm sure it's out there.
Help with patch on Windows
Check out this page: http://drupal.org/node/324. Scroll down to where it says to "patch".
Oh, and a second reason: What happens when the module gets upgraded? You will have to wait until someone patches a new version for you before you can upgrade.
these patches should be in core
Well these patches should be in the core. I mean everybody likes more control over content permissions.
Anyone have anything working on blocks/menu permissions? I was surprised this wasn't in the 4.5 menu.
That's for Dries to decide
Dries has the ultimate say over what modules get into the core. They must meet his quality control standards before they are accepted. These are new modules and are not quite ready for prime time.
description of patching in Drupal book is inadequate
I just added to the explanation of diff and patch that was at:
http://drupal.org/node/323
My explanation provides a more step by step guide to doing a patch if you have shell access on your web server (unix).
If you have Windows you should be able to have a similar set of step, about 8 or 9 steps, that will do what you are looking to do. However I didn't try downloading a windows based tool to do this so someone will have to write that.
NYSYS -- the attitude that it is too difficult is not helpful, because there are a lot of things about Drupal that could easily be made more accessible to people who are not able to read between the lines. If I find it difficult at times to get adjusted with a masters in computer science than I think it is going to be way to complex for many potential users.
Organizers' Collaborative -- Free Software for Activist Groups
http://organizenow.net and http://organizersdb.org
I'm all for it
I'm all for making things as easy as possible. That takes time, however. If people expect solutions and answers to be served on a silver platter with software with that is still maturing and evolving, then their expectations are too high. That's just not how it works.
If a user wants feature X, but feature X has not been fully developed, they are either A) going to have to learn how to install feature X manually or B) wait until it has been fully developed to take advantage of the feature, or C) pitch in either financially or with the talent that they have to make feature X ready for prime time sooner.
I'm doing C. I encourage others to do the same.
By the way...
Who is this? I contributed to OC a few years back and went to a conference you guys held at Yale. I've been meaning to get involved again but just haven't been able to find the time.
I was trying to patch the wrong file
I was also having a lot of problems trying to patch the taxonomy_access module, until I realised that it's not the taxonomy_access module that needs patching, but the taxonomy.module in the modules directory that needs patching. Just in case anyone else is being as stupid as I was.
Also, as I use windows, I had to find a way to patch on my windows xp machine. I found this tool which worked:
http://hp.vector.co.jp/authors/VA010446/toolbox1/archives/patc254w.zip
Remember to add the directory where you exract the patch tool to, to your path variable.
thanks to this node: http://drupal.org/node/323
Charles
www.parkroad.co.za
Charles
Drupal development, Cape Town, South Africa