• Resolved enonir

    (@enonir)


    Add Polylang support for Customizer v. 1.3.8
    Theme: Ashe v. 1.9.9.5.1
    Wordpress 5.7

    Changes in customizer made in one language are saved to other languages.
    For example – featured links, featured slider.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author richardevcom

    (@richardevcom)

    Hi @enonir thank you for your submission.
    Due to previous fix in 1.3.7 version can you verify that, when saving settings you have language added as parameter in your URL (for example. https://localhost/wordpress/wp-admin/customize.php?lang=en?lang=en)?

    While you verify, I’ll go ahead and test this on Ashe theme latest to see what else could cause this issue.

    • This reply was modified 3 years, 11 months ago by richardevcom.
    Thread Starter enonir

    (@enonir)

    I have in both languages,

    /wp-admin/customize.php?lang=pl
    /wp-admin/customize.php?lang=en

    Thread Starter enonir

    (@enonir)

    Update – Featured slider works as for now. Featured links won’t translate.

    Hi,
    I have the same problem.
    I change page for EN Footer, I save it. After that I change the language and save footer page for FR footer. The new FR footer override the ENG Footer.. and also all other langages.

    I also see the correct parameters when I change language:

    Es:
    /wp-admin/customize.php?lang=en
    /wp-admin/customize.php?lang=fr

    Polylang support for Customizer v. 1.3.8
    Wordpress 5.7

    Thanks
    Have a nice day

    Plugin Author richardevcom

    (@richardevcom)

    After some testing it seems that the issue is in the way Ashe theme options are being saved and parsed on update. To be more precise – while this plugin indeed creates and updates settings for both languages, Ashe theme options seem to still save under ashe_options record.

    For now I can try make workaround for set of array settings to be also parsed within the database for each language.

    Also thank you both @neroti and @enonir for submissions. For now I’ll put it as resolved (this means I’ve put this as top priority feature to add into the plugin for next update) and I’ll update you both here when the workaround update will be out.

    • This reply was modified 3 years, 11 months ago by richardevcom.
    • This reply was modified 3 years, 11 months ago by richardevcom.
Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Won’t work’ is closed to new replies.