Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Gday mate,
First I quote a post that I sent to Drupal (kick booty) developers
Well, coming from a management background using open source only for web serving (Apache) and mail (SENDMAIL) and top notch high throughput hardware (Sun), this is a breath of fresh air. Your complete modular application design is really cool. I can re-install the app and restore DB milestones in seconds.
One thing that is a bit of a worry though. One of the main modules our site will be using is the TAC. How am I always sure that my vocab/terms will be cared for as other modules are introduced? We installed on our local system the Category module that completely blew away any hopes of controlling our content and how our users will be accessing them.
Our plan so far? We have over 20 roles. 6 different vocab. Up to 100 terms per vocab. It could be a potential admin nightmare if modules are introduced without proper attention to the TAC
Barring that...this app is shit hot.
Pat
We are completely reliant on your module. Your module is exactly what is needed for a fully fledged moderator based blogging/social networking site.
I did, however, through extensive testing, find some lack of information in your docs. I would love to help. I think I could be a users mind in a developers world. If you are keen, please let me know how I can get active in your group to help with the docs.
I does rite weal gud :)
All the best
Patrick Van Rinsvelt
Comments
Comment #1
keve commentedHi,
I know this module is quite complicated escpecially for beginners.
But because of all my works, I rather try to develope the code, and i never have time for the documentation.
I guess this is not the only module with this problem.
Thanks for your offer. Of course i would gladly accept any help. :)
Best regards,
Keve
Comment #2
Patrick Van Rinsvelt commentedKeve,
I need to know what doco you want me to start working on. My guess is the README.TXT
so that you can have a look and edit. We can then look at updating the Drupal site accordingly.
Powerful little module you are developing and we are quickly learning the dependencies on
other parts of the Drupal core and other modules.
Your thoughts?
All the best,
Pat
Comment #3
keve commentedYes, we should begin with README.txt.
Maybe we should divide it to 'General info' and 'Technical info'.
In General: it should be clearer: what this module is for, and about its power. :)
We should add reference to the include Help page inside module.
I think. (/help/taxonomy_access).
What are your experiences about the install.txt?
Comment #4
Patrick Van Rinsvelt commentedFirst - experience with the INSTALL.txt is very good. Perhaps a couple of minor tweaks here.
Second - agreed that this is where I will start. Also agreed, for the most part, on the structure of the document. More might arise as I work on it. As I stated before, it is EXTREMELY powerful. Well coded to as I have had no issues with DP 5.0. The CMS I am putting together with your module, menus per role, and other bits and bobs, has created a great workflow.
I'll be sending you a link to our dev site so you can have a look if you wish
BTW, can you add me to your project list to make it official?
http://drupal.org/project/developers/10126
Thanks mate. Hope to have something to you in the next week or 2
P
Comment #5
keve commentedThanks for your feedback and help.
Regarding http://drupal.org/project/developers/10126, this is rendered automatically by cvs commits to the module.
But we will find a way to show your name somewhere. :)
Comment #6
Patrick Van Rinsvelt commentedKeve,
Sorry mate,
Have not been able to get to this as I am working with some menu per roles module issues
that just won't go awat. I'll get to it though.
Our launch is in 2 weeks and I am scared....
P
Comment #7
keve commentedDont worry. Good luck for your site.
You can do this anytime you like. :)
Comment #8
cpugeniusmv commented