A client of ours requested a more "usable" UI for subscribing to taxonomy terms. The following module provides a block with the following (see screen capture: http://screencast.com/t/YThkM2U2):

autocomplete free tagging term selector

- autocomplete allows users to select terms from a defined vocab to be added to their subscription list
- if the term that is typed does not already exist; it will be added (ajax) to the vocab and also added to the user's subscription list

users current subscribed terms

- a list of the users existing subscribed terms
- small icon to remove (ajax) the term from their subscription list

current nodes terms

- if the block is on a page view of a node it will list the terms used on that node
- small icon beside each term to add (ajax) the term to the user's subscription list

extending this to add author and node subscription support would be pretty simple. Also had wanted to include a section of top tags with similar ajax driven selectors

the module requires jquery_update.

Hope someone finds it useful.

This work funded by the The Association of Faculties of Medicine of Canada (AFMC)

CommentFileSizeAuthor
chec_notifications_ui.zip24.91 KBliquidcms

Comments

liquidcms’s picture

liquidcms commented
Title: new ajax driven fee tagging UI » new ajax driven free tagging UI
Status: Active » Needs review
vm’s picture

vm commented
Title: new ajax driven free tagging UI » new ajax driven fee tagging UI
Status: Needs review » Active

Very nice!

liquidcms’s picture

liquidcms commented
Title: new ajax driven fee tagging UI » new ajax driven free tagging UI
Status: Active » Needs review

why did you change my title and status??

vm’s picture

vm commented

Incorrect accusation. Inspect the time of the posts. They are the same. I didn't intentionally change anything.

It's a known issue with issue posts that if we post at same time (which we did), drops downs in my comment screen retain the drop downs set from previous setting. When I submitted my comment it retained your original settings (inspect them) and didn't pull from your comment #1 settings because my comment in #2 had no idea that you changed the drop downs on its way to the database. ie: comment #1 wasn't physically on my screen yet when I submitted my comment.

sly5’s picture

sly5 commented

This is delightfully promising. Why isn't there a separate project page for the add-on?

vm’s picture

vm commented

I believe liquidcms's intention is to get it added to the notifications module as a contrib and ship with the main modules rather than a separate project.

liquidcms’s picture

liquidcms commented

likely not worth of a separate project - if it gets added to contrib for this module thats cool - could likely use a little clean up for things like i mentioned above.. include "subscribe to this post", etc. basically just figured i'd post here so people could try it out and use it if they like it.

my client thinks it is a huge improvement over what is available now - but it really is geared just towards subscribing to terms.