Module development and code questions

I have already searched all of drupal.org, as weel as Reyeros site, and google, trying to find a patch so taxonomy_menu works with i18n (or the other way around).

The problem is: when changing languages from i18n block, while displying a taxonomy_menu page for a term in one language, does not bring the taxonomy_menu page for the translated term.

Instead, the same taxonomy_menu page is called, but because its terms ID are for the prior language and not the language just selected, no content is displayed and a not-found message is displayed.

When the normal taxonomy/term pages are used, the i18n block processes the taxonomy/term/xx url and the link in the block is for the translated taxonomy/term/yy page. It seems that the block is aware of taxonomy/term/xx->yy, but this processing in the block does not occur for taxonomy_menu.

I noticed that taxonomy_menu uses a different syntax than taxonomy/term (/aa/bb/cc instead of just cc) and because of this complexity I could not make any progress in my attempt to patch i18n block. (If the syntax was similar, this could be done with an extra "if .... /taxonomy/term/id else ..../taxonomy_menu/id")

I have tried a workaround with alt urls. For example:
These are the two taxonomy_menu pages that needed to be switched through i18n block:
pt/taxonomy_menu/5/28 (term in Portuguese)
en/taxonomy_menu/5/25 (same term but in English)

Is it possible to extend taxonomy term edit/create form, like _nodeapi does? Is there any _termapi hook available? Or do I need to hardcode what I need?

I am not sure anyone played around with the lightbox.js

http://www.huddletogether.com/projects/lightbox/

now
the js source (to be downloaded and put into drupal/scripts or /files
http://www.huddletogether.com/projects/lightbox/lightbox.js

this is the .js include to go to the page.tpl.php
script type="text/javascript" src="lightbox.js

I just started working with webform for drupal, and it works fine.

But there is one small problem,

I have a form, where people can register products for repairs. For example:

Product1
- Model name
- serial

Product2
- Model name
- serial

Product 1/2 are labels.
Model name / Serial are textfields.

The Problem is, the name of de textfield is used as id of the textfield. So if i fill in this form. Product 2 model name will overwrite product 1 model name because they have the same id.

Updated TinyMCE Module v4.6.0j (1.21.2.11j 2006/02/24 01:55:27)

Long time listener, first time caller... what I'm trying to say is, I've never contributed to a Drupal module before, and I'm not even sure if I'm doing this in the right place.

I've been trying to get the most updated version of TinyMCE installed and configured on my Drupal setup. Currently, I'm running CivicSpace 0.8.3, which I believe synchs with Drupal 4.6.5. As many of you know, the TinyMCE module 4.7.0 has been taken down from the modules area, and only 4.6.0 is available right now (but I hear is still available in the CVS). I guess TinyMCE 4.7.0 is meant to work with Drupal 4.7.0b, and since I won't be moving to Drupal 4.7.0 until CivicSpace certifies their distribution of it, I'm at 4.6.5, probably for a while.

TinyMCE 4.6.0 works fine with CivicSpace 0.8.3/4.6.5, but the documentation on the implementation of the included plugins is aimed at developers using TinyMCE within a custom installation, not with the Drupal module. Because it's not intended for those of us running Drupal, the context of the TinyMCE plugin instructions doesn't apply to how the plugin inits need to be syntaxed within our module.

So I played around with the TinyMCE 4.6.0 module for a while until I figured out the syntax, and I added in the plugins I was most interested in using. They have been added to the "Advanced" theme. Since it took me so long to figure out how to add all of this, I thought I'd provide everyone else with a copy of the tinymce.module that I modified, in case you want to use it until the next version is stabilized.

I am new to Drupal and I am developing my first module.. It all seems to work OK, other than I get a Login and Register Tab mixed with my module tabs.. I am using a CSS based template.

I have created the permissions and access control elements and they seem to work OK, however, I don't seem to be able to get rid of these unwanted tabs.

Any idea..?