Title bulk generation/conversion executed only on settings form submit and therefore not executed by workflow enable [#1988654]

For anyone coming across #1146724: Replacing field values are not always initialized (which was already baked into the 7.x-1.0-alpha7 release) to automatically bulk initialize the ueber-slick-cool translation field field_title with node->title, note that yes it does work for entities. However, it did not work when I staged to a remote server via Features/Git/drush. Instead, it took manually deleting the field field_title, reenabling the module, and then clicking the "Replace Field" GUI form workflow that you go through when initially enabling the module in development.

Love this clever module. Works great!

-Bronius

Comments

Comment #1

texas-bronius CreditAttribution: texas-bronius commented 7 May 2013 at 03:33

Shoot. That "the patch" link above should be a #1146724: Replacing field values are not always initialized live issue queue link. Sorry :)

Comment #2

plach

he/him

Italian

Venezia

CreditAttribution: plach commented 13 May 2013 at 08:59

Version:

7.x-1.0-alpha7

» 7.x-1.x-dev

I am pretty sure this happens also on dev.

Comment #3

iStryker CreditAttribution: iStryker commented 15 December 2014 at 00:02

Issue summary:

View changes

I am having the same problem. I need a solution that is programmable and not through the GUI.

Recreate Setups
1. Enable the module (along with Entity Translation)
2. Go to your content type and click replace.
Everything works on current site
3. Create a feature of the content type and new field.
4. Include the module (along with Entity Translation) in a separate site controller feature (one that enables all require modules on the site)

5. On a separate site, copy the 2 features over.
6. Click Enable
All titles are empty on the 'find content' page. New field table is empty in database, while node table contain all original titles.

At the moment I can think of 2 solution.

#1. An update hook in the feature that would resync the titles

#2. A feature hook, that would detect/check if the included title_field in the feature has been replace and sync it on enable/update and/or revert.

Solution #1 would turn this issue into a support ticket, not a bug report.

Comment #4

sgurlt CreditAttribution: sgurlt commented 7 January 2015 at 13:16

I ran into the same issue, but after updating the module to the latest dev version, it seems to be gone.
Please retest with latest dev.

Comment #5

iStryker CreditAttribution: iStryker commented 9 January 2015 at 13:26

Version:	7.x-1.x-dev	» 7.x-1.0-alpha7
Priority:	Minor	» Major

@sg88 you are right. Its fixed in dev. Would like to know where. After reading all of the commit, nothing stands out.

Should we close this ticket? It would be nice to fix out with commit this then close the ticket

Comment #6

iStryker CreditAttribution: iStryker commented 9 January 2015 at 13:33

Status:

Active

» Closed (fixed)

Walking back in the commits #2286145: Prevent empty translations from being synced into the legacy field on Novemeber 22 fixed my problem. I did not extensive test on this commit, but it is the one that fixed my problem.

Comment #7

iStryker CreditAttribution: iStryker commented 18 February 2015 at 00:06

Version:	7.x-1.0-alpha7	» 7.x-1.x-dev
Status:	Closed (fixed)	» Active

Nope this is still an issue. On the 'Find Content' it is fixed from alpha7 and alpha7+12-dev, however when you edit a node, it does not have a title. There is no data in the field_data_title_field and field_revision_title_field.

Work arounds - running drush command drush ev "title_field_replacement_batch_set('node', 'uw_event', 'title'); drush_backend_batch_process();"

work around is like clicking the 'replace' button when you first change the title field from drupal core to fieldapi.