Closed (fixed)
Project:
Content Construction Kit (CCK)
Version:
5.x-1.x-dev
Component:
content_copy.module
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
28 Sep 2007 at 16:06 UTC
Updated:
31 Jul 2008 at 04:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
elgrad.info commentedSubscribing.
I have same problem with CCK & Advanced Profile.
Comment #2
brahms commentedSubscribing.
I also have the same problem with CCK & Advanced Profile. Setting the interface language to english makes the content import work.
Comment #3
elgrad.info commentedThank you.
It decided my issue.
Comment #4
smk-ka commentedTracked this down to two locations, in both cases t() is erroneously applied to the key of a select form field. This makes the if-conditions to always fail, and results in the content type never being created (to be precise, Drupal tries to create a content table
content_type_<created>, which is not a valid SQL table name. Not hard to image that subsequent operations go wrong, causing the whole import operation to fail.)Comment #5
yched commentedfile under the new 'content_copy.module' component
Comment #6
magico commentedno patch attached.
Comment #7
smk-ka commentedgrml...
Comment #8
brahms commented@smk-ka:
I have just tested the patch from comment#7 with Content Copy 5.x-1.7. It solves the issue for the 5.x-1.7 revision of the module and so I set the status to patch (reviewed and tested by the community). Please include the bugfix into the 5.x-1.x-dev version and the next 5.x-1.8 release of the module.
In release 6.x-2.0-rc3 and probably in 6.x-2.0-dev of the module there are also the 2 comparisons with t('<create>') instead of '<create>'. Please fix those too.
Thank you.
Comment #9
yched commentedCommitted to D5 and D6. Thanks !
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.