Closed (fixed)
Project:
Title
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
4 May 2011 at 12:48 UTC
Updated:
28 Dec 2016 at 14:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
joostvdl commentedBTW. In the node table, the title is still saved. But the new fields are not prepopulated with the original title.
Comment #2
martin jinoch commentedSame problem here. Replacing Title for content-type works only if module Comment is enabled (as stated in http://drupal.org/node/1138646#comment-4429750 ) and after replacing Title all existing nodes of that content-type have blank Title.
using Title module version 7.x-1.x-dev 2011-May-09
Comment #3
dropcube commentedI confirm the issue, after replacing the title in a content type, nodes are showed with a blank title in any views and in /admin/content
I am using the latest -dev versions of entity, entity_translations and title.
Comment #4
plachThe attached patch should fix the issue.
Comment #5
martin jinoch commentedI've tried the patch and it now works just fine. Thanks
Comment #6
Scott J commentedYes! Now this module is usable.
Comment #7
plachThe previous patch was failing tests badly (tests are reliable if run locally) and didn't work with taxonomy. The attached patch is all green.
Comment #8
das-peter commentedLatest patch worked in my manual tests like a charm :) Thanks plach!
Comment #9
plachCommitted #7 to HEAD.
Changing to needs work since it seems we have still some problem with content created in language which has been uninstalled afterwards. We are missing tests too.
Comment #10
plachComment #11
renat commentedHi!
Latest -dev version converts node titles to fields very well for me, but the problem with taxonomy terms still exists. When I convert its "Names", they are still shown on the term page, but on "Edit" page "Name" field is empty.
Comment #12
Jerome F commentedSubscribe - I come from this duplicate issue http://drupal.org/node/1183524
When a term is created with the taxonomy term reference field's Autocomplete term widget (tagging), the title module's term name field is not completed, it's left empty, but the taxonomy term is saved.
Comment #13
ptaff commentedSubscribing; same problem as #11.
Comment #14
internetdevels commentedPatch which fix this issue you can find here
Comment #15
13rac1 commentedMy project has existing taxonomy terms with descriptions. The site is all in English, but Spanish has been recently added. I can reproduce this issue with the current(9/15/12) versions of all related modules.
Steps to reproduce:
If I import a database backup, and enable translations for Taxonomy Terms the descriptions are imported into the new fields correctly.
Comment #16
ar-jan commentedGiven #9 I thought this should work, but this doesn't work with node title fields for me:
- Install Drupal 7.17
- Create an article node
- Install and enable title 1.0-alpha4
- Edit content type Article and click the replace link for the title (message: "title replaced with a field instance.")
- Visit node/1 or the content overview, node 1 has no title in field_title.
Comment #17
dddave commentedWasn't working for me neither. Had to disable the module and got my titles back. Found this in the watchdog:
PDOException: SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'fid' cannot be null: INSERT INTO {file_usage} (fid, module, type, id, count) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4); Array ( [:db_insert_placeholder_0] => [:db_insert_placeholder_1] => media [:db_insert_placeholder_2] => node [:db_insert_placeholder_3] => 23 [:db_insert_placeholder_4] => 1 ) in file_usage_add() (Zeile 661 von /is/htdocs/XXXXXXXXXXXXXX/www/drupal/includes/file.inc).Comment #18
muschpusch commented@dddave: #2007066: Media module incompatibility
Comment #19
dddave commentedUh, thanks for the heads-up @muschpusch
Comment #20
tondeuse commentedI have gone through the same process here : launching a feature on a production site with content already present in various content types. The feature contained updates and declared the title as a title field for each of my content types. The node titles are gone altogether after the revert. A manual way to restore them is to follow the processed outlined below :
Operation #2 invokes the internal method of the title module responsible for the migration of the title data from the node table to the title field table in the database. Operation #3 makes sure to restore the display & input settings for the tiltle field as you have designed them for each of your content types, as outlined in the code of your feature. Hope this helps some of you.
Comment #21
iztok commented@tondeuse
I tried that but my titles are empty even after removing the field.
Comment #22
wizonesolutionsI'm encountering this on a fairly fresh Drupal 7.27 site using Content Translation (not Entity Translation). I'm using Title just to be able to move around the title field in custom view modes.
When I click replace, everything seems to go alright, but the initialization of the field values doesn't actually work. Titles render blank. When I delete the field, the titles come back (so it's not deleting the originals or anything).
I can also go in and set a title manually, and obviously things work alright then.
I'm not seeing any errors in the logs to go off.
I decided to put in some breakpoints and step through what is happening.
Everything looks good up through
title_field_text_sync_set(). I even see$entity->title_field['en'][0]['value']get set to the legacy title property.Something happens between then and the final result being delivered to
title_field_replace_init(). It becomes an empty array. So clearly something is altering it. I probably don't have time to provide a patch but want to try to contribute a root cause analysis at least :)Comment #23
wizonesolutionsIt's fixed in -dev. Can we get an alpha8?
Comment #24
pcorbett commentedUsing 7x-1.x-dev. This works except that some title showed as blank for me when viewing on /admin/content. Clearing site caches fixed this for me. My guess is specifically, cache_page needed to be cleared. Hope this helps someone!
Comment #26
deivamagalhaes commentedIs this already committed to alpha8?
Comment #27
polYes