Bug #103795
closedCannot localize page in backend
0%
Description
In typo3 V12, when we try to localize a page, it seems there is no default action selected (translate / copy) in the pop-up shown, which leads to a JavaScript error ‘Invalid action “null” 2 called.’ with an infinit loading pop-up.
Files
Updated by Georg Ringer 7 months ago
- Status changed from New to Needs Feedback
can you please check the ajax response in the console for errors?
Updated by Abderrazak Tigiti 7 months ago
Abderrazak Tigiti wrote:
In typo3 V12, when we try to localize a page, it seems there is no default action selected (translate / copy) in the pop-up shown, which leads to a JavaScript error ‘Invalid action “null” 2 called.’ with an infinit loading pop-up.
Georg Ringer wrote in #note-1:
can you please check the ajax response in the console for errors?
Sure, in the console i had an "400 bad request" error says : `Invalid action "null" called.`
Updated by Georg Ringer 7 months ago
can you please also check the response of the ajax request itself, not only the console? switch to the network tab and select "fetch/xhr".
thanks
Updated by Abderrazak Tigiti 7 months ago · Edited
- File invalidAction.png invalidAction.png added
Updated by Abderrazak Tigiti 7 months ago
Georg Ringer wrote in #note-3:
can you please also check the response of the ajax request itself, not only the console? switch to the network tab and select "fetch/xhr".
thanks
Yeah, i have this message : `Invalid action "null" called.
You can check my add picture attached to see the message.
Updated by Alex Kellner 6 months ago · Edited
I can confirm this bug in TYPO3 12.4.15 if you don't choose "translate" or "copy" in the translation wizard but just click on "next" button.
The AJAX result from TYPO3:
Invalid action "null" called.
I guess clicking on next without choosing a method shouldn't be possible.
Updated by Georg Ringer 6 months ago
- Status changed from Needs Feedback to Closed
closed as duplicate of #101415
Updated by Georg Ringer 6 months ago
- Is duplicate of Bug #101415: Cannot localize page in backend added