Setting primary term to <none> broken
Oliver Coleman - March 28, 2008 - 01:36
| Project: | Primary Term |
| Version: | 5.x-1.2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
Setting the primary term for a node to isn't working, the primary term stays set at the previous setting after submitting.
#1
Let's try that again:
Setting the primary term for a node to
<none>isn't working, the primary term stays set at the previous setting after submitting.#2
I have the same problem, here is a patch that should resolve this bug :
in primary_term_nodeapi-update, I don't use _primary_term_get_tid because this function never return null even form value is empty.