I have two fields and I can't update their values, I did an update on Oct the 18th to the latest version and I guess something got broken. Can you confirm this behavior?

CommentFileSizeAuthor
#4 term_fields.patch1.81 KBb-prod

Comments

lelizondo’s picture

After 3 days trying to figure it out, I know what is the cause.

Steps to reproduce.
1. Create a vocabulary with some terms.
2. Create a field.
3. Add some data to the field you've just created and save the term.
4. Go back and edit the term. Change the data in the field and save.
5. The change will be reflected.
6. Add another field, this time make it a FILE field.
7. Edit the same term field you've edited on 4.
8. You'll notice here there's no file field.
9. Try saving the term after making a change on the term field and then edit the term again.
10. You'll see the change hasn't been reflected.

The problem it's caused when adding file fields to the term. Don't know what happened since this was working.

lelizondo’s picture

I've just restored a backup and it's working. I also want to add that I'm using Taxonomy Image, I don't think it's a compatibility problem. Right now, with the old version everything it's working.

Version using:
// $Id: term_fields.module,v 1.7 2009/06/11 06:10:27 archard Exp $
// $Id: term_fields.admin.inc,v 1.4 2009/06/11 06:10:27 archard Exp $

b-prod’s picture

Thanks for your well-detailed report.

I will investigate soon on what happen.

b-prod’s picture

StatusFileSize
new1.81 KB

Some code were missing and I really don't know why, because I never changed anything about file support.

I have created a patch. Could you please apply it and verify if it corrects your problem. If so, I will create a new release for the module.

lelizondo’s picture

Status: Active » Reviewed & tested by the community

It works. Since I'm the only one who found this problem I'll change the status.

Thanks.

b-prod’s picture

Status: Reviewed & tested by the community » Fixed

Thanks for testing! Patch has been ported.

Status: Fixed » Closed (fixed)

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