Postponed
Project:
Quick Edit
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
1 Feb 2013 at 08:47 UTC
Updated:
19 Aug 2014 at 20:53 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nod_I totally expected this one to come up. So close. I was going to look at it this week-end :)
Comment #2
kingfisher64 commentedI'm just delighted to hear that this is being addressed for d7.
Will be very handy to have it work with the title mod.
Good stuff nod_ :)
Comment #3
nuezHi nod_
Thought I´d give you a hand. I´m sure you could figure out a cleaner solution, but here´s what I did:
The problem is that what the TITLE module calles 'legacy fields' should be updated as well.
Let´s say the original language of a entity is spanish, but the entity could be translated to english as well.
If you save the $entity->title_field['en'] values nothing happens, but when you save the $entity->title_field['es'] values, the $entity->title value gets saved as well.
I looked into the title_field_attach_submit function to see what it does, and took some essentials from it to add to the 'edit' module. See patch.
I´ve noticed that the edit module executes the field_attach_submit function, so the title hook should be taken into account...
Comment #4
nuezSome trailing whitespace fixes
Comment #5
wim leersWow. Talk about massive edge cases for valid use cases :)
However, I don't understand yet why we essentially need to duplicate part of the Title module's code here (i.e. of
title_field_attach_submit()). Edit callsfield_attach_submit(), which should calltitle_field_attach_submit(), which means that … in theory, it all should be working just fine without these hacks?Also, this is not a bug, it's a feature request, and possibly one of major priority.
Comment #6
wim leersFrom #2168725: [META] Add support for in-place editing entity types other than Node:
Comment #7
wim leers