[Risolto] Urgent: Issues with Advanced Translation Editor (ATE) forcing & workflow blockage for custom page te...

Context:
I am experiencing critical workflow issues with your Advanced Translation Editor (ATE) in the latest WPML versions, specifically concerning custom page templates and ACF custom fields. Despite preferring and configuring my site for the classic WordPress editor for translations, the ATE's aggressive enforcement is causing significant blockage.

My Desired Workflow / Need:
I need to manage translations directly within the standard WordPress editor for my pages and Custom Post Types. My primary goal is a clean, direct interface for content management in different languages, without any warning notices or blocking pop-ups that interrupt the user experience. This approach is essential because I heavily rely on ACF fields with complex conditional logic, which needs to function correctly and visibly across all language versions of the editor.

Current Problems Observed:
Forcing of ATE despite settings:

I've configured my site to use the "Classic Translation Editor" globally, as the option to choose by Post Type (e.g., Pages, my custom CPT 'prodotto') is no longer available in recent WPML versions.
However, when I click the "pencil" icon to edit a translation from the original post (e.g., a page assigned to page-templates/page-prodotti.php), it still opens the Advanced Translation Editor (ATE).

ATE Interface Issues:
When the ATE opens, it fails to correctly represent my ACF field groups with conditional logic. Specifically, fields that should be hidden based on conditional rules (e.g., fields within the "Hero section (grafica)" or "Hero section (gialla)" groups based on the "Tipo di Hero" radio button) are all displayed. This makes the ATE interface confusing and unusable for my content creators.

Persistent and Blocking Warning in Standard Editor:
If I bypass the pencil icon and directly open a translated post/page for editing in the standard WordPress editor (e.g., wp-admin/post.php?post=XXX&action=edit&lang=en), I am immediately presented with a highly disruptive and non-functional warning pop-up: "Attenzione: Le modifiche che stai per fare andranno perse. Stai per modificare questa traduzione usando l'editor standard di WordPress. Qualsiasi modifica che fai andrà persa la prossima volta che mandi questa pagina per la traduzione." (translates to: "Warning: Changes you are about to make will be lost. You are about to edit this translation using the standard WordPress editor. Any changes you make will be lost next time you send this page for translation.")
This alert blocks the entire editor interface.
The provided options are:
"Torna indietro" (Go back) - Does nothing.
"Modifica nell'Editor di Traduzione Avanzato" (Edit in Advanced Translation Editor) - Does nothing (the button is unresponsive).
"Modifica comunque (sconsigliato)" (Edit anyway (not recommended)) - This is the only functional option, but it comes with a strong warning that is highly off-putting to content managers.

ACF Field Translation Preferences:
I have experimented with ACF field translation preferences in WPML > Settings > Custom Field Translation.
If I set ACF field groups (like hero_section_grafica or hero_section_gialla) to "Campi diversi tra le lingue" (Translate independently), the warning persists.
If I set them to "Copia" (Copy), the situation remains unchanged; the ATE still opens via the pencil icon, and the warning still appears in the standard editor.

Summary of the Core Problem:
The current WPML workflow is blocking my ability to use the standard WordPress editor for managing translations, which is critical due to ACF's conditional logic not being supported in the ATE. The persistent, blocking, and partially unresponsive warning makes editing translated content extremely difficult and frustrating for content managers.

My Request:
I need a solution that allows me to:

Manage translations directly within the standard WordPress editor.
Avoid the "Attenzione: Le modifiche che stai per fare andranno perse" warning pop-up entirely.
Ensure that my ACF conditional logic functions correctly and visually in the standard editor for all languages.