Conflict with Active Translation? [#624392]

Hi,

Active Translation is a module for multilingual websites. If a page is not available in one language, it will display the page in the default language, along with a notification message. This message should be displayed at the top of the node.

I have two websites using Active Translation, one with a subtheme based on Basic 6.x-2.0, the other one with a subtheme based on Basic 6.x-2.8.

On the one using Basic 2.0, the message is displayed at the top of the content. On the one using Basic 2.8, the message is displayed at the end of the content (not very useful for a notification...).

Here is the info I gathered by trying to fix this issue :
- the message is given a weight of -100 by active-translation.module
- it is rendered in $content, so it hasn't been themed in a .tpl.php file
- I can't see anything in node.tpl.php or template.php that could explain this behaviour
- both websites are using the same version of Active Translation
- both websites are running the latest Drupal version

Therefore I think it comes down to something that was updated between Basic 2.0 and Basic 2.8, but I can't find what.

Comments

Comment #1

Anonymous (not verified) CreditAttribution: Anonymous commented 5 November 2009 at 17:14

That sounds rather odd. I might need more information about this.

- Does it still happen on a clean install with Basic 2.9 ?
- Could you provide a snippet where the message appear ? Or maybe even a screenshot ?
- It sounds obvious but, did you check the block configuration ?

I really don't see why this is happening. If a message is displayed, it should be using the $messages variable of the theme, and this one is easily movable. If the module uses something different, it sounds like something the module should change. I never tired this module so I might be wrong.

Comment #2

mdupont

French

Switzerland

CreditAttribution: mdupont commented 5 November 2009 at 20:32

I'll try with a clean Drupal install and Basic 2.9 and I'll make screenshots of the issue.

I have checked the block configuration ; as I wrote above, the module doesn't use drupal_set_message() or create a block, it uses instead its own theme hook to add the message to $node->content.

Comment #3

mdupont

French

Switzerland

CreditAttribution: mdupont commented 6 November 2009 at 13:17

Status:

Active

» Closed (fixed)

I stand corrected. After trying Basic 2.9 then Basic 2.0 on a website with the issue, it doesn't make any difference. So I guess it comes from Active Translation (although I still do not understand why I have this issue on some websites and not on others). I opened an issue at #625228: Implement hook_content_extra_fields() so CCK can re-order our message and I'm closing this one. Sorry for the noise.
EDIT: Found, it was CCK messing with elements default order, details in Active Translation issue.