Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The message are displayed after updating a content type. The changed setting is the Publishing options -> Multilingual support -> Enabled, with field translation.
Screenshot
I'm not sure if this is only a problem of Commerce Coupon.
Comment | File | Size | Author |
---|
Comments
Comment #1
quiptime CreditAttribution: quiptime commentedSee
http://drupalcode.org/project/entity_translation.git/blob/refs/tags/7.x-...
The function entity_translation_menu_alter(), line 168 and the following, produces the message.
Comment #2
quiptime CreditAttribution: quiptime commentedFor a solution, please take a look at
http://drupal.org/node/1587108#comment-6180310
Comment #3
pcambraThere's no effort/testing in use entity translation with this module, so I'm not surprised you get some warnings there.
Not sure of what "base path" property is exactly but coupons should't have a uri normally.
Comment #4
plach@pcambra:
Entity translation relies on a
'base path'
entity info key to provide the translation UI. It tries to provide a sane default but for non-default values it needs the module defining the entity to explicitly provide that info. See entity_translation.api.php.See also #1114410: Replace hook_translation_info() with hook_entity_info(). The entity info is not changing but the hook in itself will go away.
Comment #5
pcambraThanks for the comments plach, let's mark this as feature request and implement the same integration than for commerce products.