Hi, I really like this module now! One thing strange happens.
I checked the buttons:

-  Multiple values
- Display parent terms as selectable form items
- Add used terms as node tags?

- I add a node and tag terms on it.
- Than I press submit and can see the terms tagged to the node.
- Then I go to edit... and see my terms not checked anymore.
- Then I check them again, and from now on I see my terms nicely checked every time.

But the first time the terms are not ok saved I think..
Thanks for getting into this!

Greetings, Martijn

CommentFileSizeAuthor
#4 settings_vocab.jpg60.71 KBsummit
#4 settings__vocab_ssu.jpg73.69 KBsummit

Comments

rconstantine’s picture

rconstantine commented

That's puzzling. I'll have to check it out.

summit’s picture

summit commented

Hi Ryan,

The tabels are filled correctly Node_term and cck_ssu tables are filled correctly. Could it be the selecton process?
The terms are not checked when after first time making a new node, the nodes are edited...I have to submit them again..
Could you please get into this? Could it be the function _cck_taxonomy_ssu_branch?

EDIT: When I submit the node without checking terms, and edit the node again, and then check the terms, the terms are saved ok!
But the first time no term is checked when I edit a submitted node.

Thanks a lot in advance!

Greetings,
Martijn

rconstantine’s picture

rconstantine commented

I should have time to look at this next week. I'd like to clear the issue queue on this module, so stay tuned.

summit’s picture

summit commented
StatusFileSize
new settings__vocab_ssu.jpg73.69 KB
new settings_vocab.jpg60.71 KB

Hi Ryan, Thanks!
If you need me to test something please let me know.
I attached pictures to show the settings I made. The first time node submitting. It is only the first time submit with a new node that this behaviour occurs. The second time you go into the node, the checks keep staying there.
I think second time the check goes through other functions in the module, right?

EDIT: Especially the advertisement module (ad.module) gives this behaviour.

greetings,
Martijn

rconstantine’s picture

rconstantine commented

Ah, I may see a problem. I thought I had a note about this in the README, but maybe I don't.

Behavior is unknown for vocabs with multiple hierarchy. You should use single hierarchy.

summit’s picture

summit commented

Hi Ryan,

I changed my vocabularies to single hierarchy, but the behaviour still stays...
With selecting the ad.module contenttype ad_text. The node table, the node_revisions and term_node show the right terms selected also after the first time. But the GUI of the node-edit screen doesn't show the terms as selected the first time of edit.
And when you then push submit, no terms are shown selected.
Again after selecting the terms for the second time, they are shown correct when editing the node.

EDIT: Hi Ryan, May be this is related and is it not in your module: http://drupal.org/node/216862#comment-722840 I don't know yet.

Thanks for going into this!
Greetings,
Martijn

rconstantine’s picture

rconstantine commented

After reading the entire post you linked to, I'd say you figured it out. If the taxonomy is truly empty, then that would be the source of your difficulties indeed. Let me know how that plays out for you.

rconstantine’s picture

rconstantine commented
Category: bug » support
Status: Active » Fixed

OK. I tested this using the exact same settings as you did above. I could not duplicate the problem. I would suggest using the OpenAds module instead.

summit’s picture

summit commented

Hi Ryan, Thanks for testing. I think it is a ad (advertisement) module issue that taxonomy is not saved.
I have made an issue on the ad.module issuelog. If that is taken care off and I still have the issue, I will report back off course.
Again thanks for testing. You didn,t test with the ad.module, right?

Greetings,
Martijn

rconstantine’s picture

rconstantine commented

Nope. I didn't test with the ad module. Cheers.

Anonymous’s picture

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

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