continous loading on create node

6.x issue without activity for over 3 years, closing.

Please reopen if this is still an issue in 7.x.

I want to reopen this because i have the same exact problem as it comes to the annoying loading cursor on a node creation.

Everything works fine, i can select every single term based on its hierarchy. The only thing that happends is once i select the first parent term it starts giving me the loading cursor outside selectable/clickable elements on the page. So basicly it loads everything fine and i can select the next sub parenting term and so on but once i move my mouse out of any usable element the spinning cursor pops up again.

To be really honest, if this was for myself i could not care less since it does work in functionality, but since this part is to be seen by many many people using that part of the panel i want this fixed somehow.

So, any ideas?

@DiviNe187 I am fine with including a fix for this -- just need someone to submit a patch and I'll have a look.

Is this something i can do or? (it is not a local installation so do not have any access except for ftp/web)

Love to see it fixed, it is exactly what i am looking for to reduce the mess a tree gives.

By the way, do you know if it is possible in combination with this module to make sure people choose a endpoint child term if you know what i mean? (if you want me to open up a new question i am fine with that)

Like, i have this:
Smartphone
-Apple
--iPhone 4S
---Repair blabla
-Samsung
--Galaxy S3
---Repair blabla

I want them to be able to choose the Repair term only, not any parent terms above that, is this something i can do with this or any other module? So that when they would pick the term Apple or Galaxy S3 they would get a message stating they need to pick and end-point term.

I think under Level choice there is a setting called "force the user to choose a !item from a deepest level"

Thank you, it worked, however, when i was trying this out i found out the loading cursor is not the only problem. When i select a sub term and click back on a parent term the new sub terms do not display.

For example:

If i click:
Smartphone <--1
-Apple <-- 2
--iPhone 4
--iPhone 4S <-- 3
---Repair blabla <-- 4

If i would click untill i land on #4 and go back to any other sub term such as iPhone 4 or even Apple or Smartphone, the sublist does not come back.
When i enable the deepest level selection option, what happends is, when i open a node creation page and click on Smartphone, it automaticly pops Apple + iPhone 4, so when i want to navigate back to for example Apple to be able to select the iPhone 4S it does not return any sub terms anymore.

Weird thing is, the same thing happends in the configuration example, except for the spinning wheel that stays. If i disable the deepest level only option the example page works like a charm in terms of cursor not staying, i still cannot navigate back to a parent term without loosing the option to select another child under the Smartphone term.

I am currently having this issue when i try to create a node. After selecting the taxonomy menu in the hierachical select drop down, my mouse turns into the page loading sign and i cant save or do anything else.

How do i fix this.

Thanks

@docans: regardless of using beta3, beta4 or beta5?

I'm unable to replicate this and it is 2 years since it saw any activity.

Also, it's a minor UX issue. There's no way this should have been set to Critical. :)

If anyone still sees this on a more up to date version please reopen and update the description with comprehensive steps to replicate.