I've tried searching the archive, but to no avail. How are the taxonomy synonyms expected to work? My first thought was that they're a sort of autocorrection mechanism (think of tags with umlauts). To my surprise, there are only two places in the core where synonyms are used at all: in the term edit form, and in the {term_data} updating code. This means synonyms are not used at all. Did I miss something? If so, should I write my own module for tag autocorrection, or is there a solution available already?
I'm using the video module, which works really well, except I need to add more than one embedded video to a node. So that rather than have one embedded (youtube) video in a node, I could have say 5.
I'm unfortunately not an expert in the development of modules, so I was wondering if anyone had any tips on how to go about customising a module like video to do this.
I have a small module that validates users creating new accounts using the 'validate' op in the _user hook. However this hook also gets invoked when they try to change any aspect of their profile.
How do I tell the difference between these two contexts?
The best stab I have is that $account['status'] is set to 1 when someone is trying to change their profile, but it isn't in either of the cases that a non-user is trying to create an account or an admin person is creating one for them.
But where is the documentation? Is this the right test or is there a better one?
The primary use of this would be either 1) online meetings or 2) meetings for folks in the local office. I know there are several existing modules for event notifications, but in place of getting notifications a day in advance, I want to figure out how to allow users to be notified in X minutes. It could just be a pulldown menu with times in 5 minute increments.
Is there any existing method for getting notifications in increments in minutes instead of days?
how can you change the preview button text? short of using the locale.module or image replacement, i can't figure it out, without hacking up node, since a button's text is controlled by its #value.