Auto-populate node title
stormer - September 3, 2007 - 10:27
| Project: | Field Thief |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Strictly speaking this probably isn't the place to post this request but I'm hoping it's ok. I'm using auto nodetitle with great success on my site but am wondering whether someone might be able to share a bit of code to enable me to auto fill the title field. I've got a taxonomy field which the user selects from and it's this selection which I want to auto fill the title field with. Any help would be very much appreciated.
many thanks
Ole

#1
Sorry to bump this but I'm desperate for a solution and am running out of time. It's possible I explained myself badly originally:
Basically I have a taxonomy field in the content type from which the user has to make a selection. It is is this selection that I need to pass to the node's title ie. taxonomy field selection = node title. I imagine this would be really straightforward but I have absolutely 0 knowledge of PHP and none of the other support requests seems to cover my requirements. Please can someone help me out here.
many thanks,
Ole
#2
I'm afraid that I haven't used Automatic Nodetitles, but since I'm changing the issue info anyway, I'm going to offer some advice:
On posting issues effectively:
Neither "help with PHP" nor "Desperate now" are descriptive issue titles. Developers skim the issue queue for items within our areas of interest and expertise. It's far easier to skip the vague ones than spend the time to examine them only to learn that 9/10 times they are not related to anything we work on.
Asking that a piece of software do something new is a feature request, not a support request. Asking for code or a change to code is not support, it's coding.
Feature requests are NEVER posted against a release of a piece of software. Once something becomes a stable release, it only gets bugfixes, security fixes, etc. Feature requests always go against HEAD or the latest dev version, as appropriate.
The "priority" field is not there to evaluate how important this issue is to you personally. It is there to indicate how critical the issue is the the project as a whole. If the issue doesn't pose a security threat or make the software almost or completely unusable, it is not critical.
On respecting the time and talents of Drupal developers:
It seems like you didn't intend it, but your posts send a very bad vibe to developers:
"Strictly speaking this probably isn't the place to post this request but I'm hoping it's ok." says to a developer that you know you are posting in the wrong place, but you don't care to make the effort to do it correctly. This is not the way to impress someone that you want help from.
Marking something as critical when it isn't says to a developer, "I don't care how many other things are on your to-do list that are more pressing and effect more users. I want this, I want it now, and what other people want is simply not as important as what I want."
"I imagine this would be really straightforward but I have absolutely 0 knowledge of PHP..." says to a developer, "I have no idea how you do what you do, but I don't value it. Do it for me, but don't expect any appreciation in return." Unless you can demonstrate enough knowledge to make this judgement, you are just devaluing our work.
You bumped your issue less than 14 hours after posting it. For someone who wants a volunteer to help them with something, you are very impatient. If we responded to everyone who wanted something done at the last minute with no compensation, we'd starve to death right after having our cars reposessed and our homes foreclosed on.
On getting the code you need:
First of all, be respectful. No one likes to be treated disrespectfully, and those of us who are good at what we do simply don't bother with rude people.
If you are respectful of the developers, if you are willing to do your homework (include all needed info, watch the issue and contribute information, advocate your desired feature/fix, test possible solutions that are offered, etc), if you are appreciative, and if you are willing to wait until we get around to it, you will likely get some help for free. We don't mind helping, we just don't want to be treated like your lap dog.
If you can't afford to wait until "when we get around to it", you are left with two options: do it yourself or pay someone to do it.
If you choose the do-it-yourself route, read the documentation, make liberal use of the Drupal API reference, and ask (polite) questions of the volunteers in the Drupal forums and IRC channels.
If you wish to hire someone to do the work for you, expect to pay a premium for work under a tight deadline. One way to find Drupal consultants is by posting to the paid Drupal services forum and/or groups.drupal.org. The more clear you are about your requirements, timeline, and budget, the better the responses you will get. (Don't forget to mention how you would like to be contacted!)
I know that it can be frustrating to need a solution and not be sure how to get it or how long it will take. I've taken the time to write this lengthy response because I hope that it will be helpful to you. I hope that you will take my advice to heart and use it to get the most from your participation in the Drupal community.
Susan
#3
It's doesn't seem to be related to Automatic nodetitles.
Try this module, although I'm not sure how it deals with Taxonomy. (But you can have your taxonomy as CCK field, and then it will work)
http://drupal.org/project/fieldthief
#4
Thanks for the lead, I'll have a look at that. In the meantime I've also come across this: http://drupal.org/node/137669