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.
As we look at the code, das-peter and I think this should be 'base path', not 'path'. True?
function hook_translation_info($types = NULL) {
'translation' => array(
'translation' => array(
'class' => 'TranslationCustomEntityHandler',
- 'path' => 'custom_entity/%custom_entity',
+ 'base path' => 'custom_entity/%custom_entity',
Comment | File | Size | Author |
---|---|---|---|
translation.base_path_api.patch | 1.05 KB | rfay |
Comments
Comment #1
rfaytagging
Comment #2
plachYesss!
Comment #3
sunbtw,
base path
sounds a bit odd and ambiguous, as it literally can mean the base path of everything and nothing. Shouldn't it beentity path
?Comment #4
das-peter CreditAttribution: das-peter commentedsubscribe
Comment #5
sunmmm,
base path
, resp.$this->basePath
is used all over the place (and this partially duplicates Entity API module, I think :-/... ), so let's simply fix the docs for now.Thanks for reporting, reviewing, and testing! Committed to HEAD.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #6
plach@sun:
Yes, I'm seriously considering to drop the translation handler class in favor of an entity wrapper: since we still are in deep dev stage I think we can lightheartedly take this path if we want to.