hugod

Hi @ngeorg,
Thank you for reporting the issue. We’ll look into it promptly.
In the meantime, could you provide us more context on how to reproduce the fatal error?

• This reply was modified 2 months, 1 week ago by hugod.

Hi @danielstrelec,

I don’t get how it is related. You’re mentioning ACF fields, which is not the same as custom post type settings from @rgires ticket.
Also, for Polylang Pro support, please contact our helpdesk at https://polylang.pro/support/.
Moreover, you have to know that Polylang Pro 3.7 brings a new ACF integration. You may want to ensure the migration ran well.

Hi,

Thanks for reaching us. You have to know that PLL_Admin_Links::get_data_from_new_media_translation_request() does exist, see https://github.com/polylang/polylang/blob/f850d7af3a4e5051ecbfcf03d1cd1a909861d37f/admin/admin-links.php#L274.
In order to fix your issue, please delete Polylang from your wp-content/plugins/ directory and add it back.

Regards.

• This reply was modified 1 year, 1 month ago by hugod.

Hi @emrevona,
You can use our public API to retrieve the main Polylang class instance:

$polylang_settings = PLL()->options;
if($polylang_settings[“force_lang”] == 3){
    // do something
}