Hi,

I came a across a tricky problem. Imagine you are managing a multilingual website with mysite.com (english) and mysite.fr (french). If you enable both locale and content translation and choose to change language by domain detection you'll have a problem while trying to translate a content if you are not logged in.

Here's an example :

1. On mysite.com, I log in and create a new content in english
2. Now, still from mysite.com, I want to edit my new content to add a translation with the translate tab
3. When I click translate, I have a page with my english content (source) and I can choose to add a new translation
4. When I click the "add a translation" link, if I'm logged in on mysite.fr I'll have my title and body pre-populated but if I'm not, I'll have to log in first, then I'll have a blank title and body instead !

I don't think this is a normal behavior. What do you think ?

Thank you.

CommentFileSizeAuthor
#5 40x_query-1069514-5.patch962 bytessemiaddict
#3 40x_query-1069514-3.patch1 KBplach

Comments

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Title: Content translation » Node translations not prepared for anonymous users
Category: task » support
Status: Active » Postponed (maintainer needs more info)

I don't think this is a normal behavior. What do you think ?

I was able to make anonymous users translate content and have the node edit form prefilled by giving them the following permissions: Translate content, View published content, View own unpublished content, Create new content, Edit own content, Delete own content.

What about you?

anavarre’s picture

anavarre
Primary language French
Location 🇪🇺
commented

Actually, I don't want an anonymous user to be able to translate anything. On the example I gave before, I was doing the translation workflow from the admin user with all permissions enabled.

plach’s picture

plach
he/him
Primary language Italian
Location Venezia
commented
Title: Node translations not prepared for anonymous users » URL parameters are not passed along when logging in from a 403 or 404 page
Version: 7.0 » 7.x-dev
Component: translation.module » base system
Category: support » bug
Status: Postponed (maintainer needs more info) » Needs review
Issue tags: -multilanguage, -content translation +Quick fix
StatusFileSize
new 40x_query-1069514-3.patch1 KB

I'm sorry the OP was perfectly clear, but somehow I managed to misunderstand it ;)

This is a more generic bug: simply URL parameters are not passed along when logging in from a 403 or 404 page.

Steps to reproduce:

  1. log off
  2. visit /admin&p=test
  3. use the User Login block to log in as a site administrator

Expected result: you are redirected to /admin&p=test.
Actual result: you are redirected to /admin.

The attached patch should fix the issue, probably we need tests here.

Status: Needs review » Needs work

The last submitted patch, 40x_query-1069514-3.patch, failed testing.

semiaddict’s picture

semiaddict commented
Status: Needs work » Needs review
StatusFileSize
new 40x_query-1069514-5.patch962 bytes

I know this is a very old issue, but I am experiencing the same problem in 7.19.
Attached is a new patch, hoping it will pass the tests !

Status: Needs review » Needs work
Issue tags: -Quick fix

The last submitted patch, 40x_query-1069514-5.patch, failed testing.

Issue tags: +Quick fix

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.

Status: Needs work » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.