Since no issues in the issue queue and i would assume this is a pretty widely used module (since it is very useful) i assume there is possibly some interaction with other parts of my code that are breaking this - although i have gone through quite a bit of debugging and i can not see any place in my code that could be doing this.

Basically, what i see is when i edit one of my newly created nodes i see the title field and the vocab selector fields disabled (good) and the vocab selector is tagged with its matching term (also good). But, when i try to submit the node, the term is lost and the form will not validate since it says that the vocab field is required. Plus, it is still disabled, so no longer possible to select.

Also, if i disable your form_alter code for the node forms then the field is no longer disabled and now submits correctly.

ill take a look at previous version to see if something changed; and also look through your form_alter code to see if obvious mistake; although for my specific case right now it isn't too big a deal if the vocab selector field is left enabled.

Peter Lindstrom
LiquidCMS - Content Management Solution Experts

Comments

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Status: Active » Postponed (maintainer needs more info)

What type of vocabulary are you using? You used the word 'tagged', do you mean you are using freetagging? Because if that's the case, I might have to revise the code for that scenario as I really haven't thought that use case.

liquidcms’s picture

liquidcms commented

nope, not free tagging.. and damn.. that was a quick reply.

i have fixed the issue...

in your form alter code you are missing this line in your "fake" vocab selector:

$form['taxonomy'][$vid . '_disabled']['#required'] = FALSE;

plus, fyi.. you have this line twice:

$form['taxonomy'][$vid . '_disabled']['#multiple'] = ($vocab->hierarchy == 2);

module seems to work great now.. and just what i needed.. :)

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented

I am fixing that and adding the required = FALSE thing, I am worried about loosing the term when you first submitted the node, do you have everything disabled again now? I mean, have you reverted any changes you did to my module except the two things you mentioned on your last posts and your problem disappear?

Thanks,
a.=

liquidcms’s picture

liquidcms commented

not sure what you are asking?? only real change i made was to add that one line.. and module works fine.

i did also remove the duplicate line; but it wouldn't have any affect either way.

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Status: Postponed (maintainer needs more info) » Fixed

I was just asking if you did anything else such as having the disabled vocabulary 'enabled' as you mention on your first post. Anyway, I have released a new version with this two things fixed, so if you can upgrade to that module and provide any feedback if needed that would be great.

Thanks,
a.=

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.