tag_editor 1.0 milestone

+1 to that

A definite requirement. I'll patch it up soon.

Yes, would be cool to see the option in taxonomy vocabulary edit form instead of creating another dedicated menu entry. There are enought modules that create menu entry to add one new when it's possible to skip it.

Any changes on this?

Also interested. Any news on progress?

Thanks

stalled for now. not sure when next time i'll work on it.

Would sponsorship improve the likelihood of development?

I would quite like this feature on my site!

+1 for this new feature. I would be happy to contribute testing.

I'm glad you volunteered for testing. So much, that you inspired me to rewrite the whole thing. Let's see if it works as good on other OSes and browsers. Tested on Mac OS X Safari 4 and Firefox 3.5.

Attached complete module. It also brings new features like navigating through tags in tag editor, deleting selected/highlighted tag, enhanced autocomplete support, and minor user experience stuff. And of course, multiple vocabulary support.

The settings to enable tag editor lie in vocabulary's edit form.

Upgrade is missing, so is hook_uninstall to delete tag_editor_% variables. Not sure if I want to take up the pain to write it. It should be pretty simple, Onopoc, if you want to help with it. :)

Great. Thanks Gurpartap. I'll try to do some testing this week. I'll post result here.

I'll update the README.txt file after the testing. http://drupal.org/node/531010

I tested #9. Here is the good new first. It works with Firefox 3 and Internet Explorer 7 on Windows XP. I tested navigating through tags in tag editor, deleting selected/highlighted tag, and multiple vocabulary support.

As for the bad news it works fine with Firefox and Internet Explorer but with the browser Opera version 9.62 funny stuff is happening. The first selected suggestion get enter twice. Then the following suggestions get all mixed-up. To clarify watch video at http://www.youtube.com/watch?v=cYwGBqaRwoo

The following isn’t a bug but a suggestion to improve usability. The spinning blue circle isn't showing. Is it normal? Expected result is after typing something into the tag editor field the spinning blue circle should be display until suggestions are return.

To improve usability I suggest adding a spinning blue circle outside the field. At a fix location to the top right. Find screenshot to clarify.

And I suggest moving the grey circle to a fix location at the top right side. Inside the field. Find screenshot to clarify.

Tested with:
-Drupal 6.13
-Windows XP
-Firefox 3
-Internet Explorer 7
-Opera 9.62

I have noticed the following bugs:
1. Other autoselect fields seem to be affected, input from non-tag_editor fields gets intercepted (zip)
2. no "select" on comma, unlike in the CVS version
3. both the zipped module as well as the CVS version might wrap themselves multiple times in Drupal.behaviors.tag_editor, so I added a check on the parent id (CVS) or parent class (zip) to avoid multiple wraps.

Too weird.

I'm using the zip version on two websites already without any noticeable problems.

Which browser are you using?

1. autoselect field? What is it? :P
2. Tagging by comma works for me on safari.
3. Need to verify this.

I was testing with Firefox 3.5.5, IE8 and Opera 10. In FF and pressing "Enter" to add terms everything worked great. With IE8 and Opera 10 I could reproduce the problems stated by Oopoc.

re 1:
"autoselect" - I do not know, where I came across this word :) I was referring to the regular autocomplete fileds, eg. the tag input field, when tag_editor is not enabled.

re 3:
Occured when using this module together with Hierarchical Select. All other functionality was not affected, just the input field looked strange.

re2:
I had to remove the module from my main site, but I will set it up on a test site to dig into it and post a link.

Just to narrow it down: in the tag field below this form on this page, there is an autocomplete "Issue tags" field. Can you use arrows and comma to select a tag? I cannot, have to press "Enter", but it worked with the CVS version of your module which is nice.

http://drupal.org/node/1025568
support one more fields
fixed opera web bowser bug